Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


yogi last won the day on August 28 2017

yogi had the most liked content!

About yogi

  • Birthday January 7

Profile Information

  • Gender
    Not Telling
  • Interests
    EEtech for the last 25yrs; spending my free time working on PIC uC projects, MidiBox projects, Atari2600 & 800s, Analog synthy stuff ( MFOS rules). First computer was a 'Super Elf' RCA Comac 1802 kit, First personal was Atari 800; ASM on 1802,6502, 8052 & PICs. When I grow up I want to be Bob Moog.

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

yogi's Achievements

MIDIbox Addict

MIDIbox Addict (2/4)



  1. Pretty much go by price; unless you plan to use the synth in the Arctic or the Sahara desert :) You should be fine with either and if you need to operate in industrial temp range something else would fail first, most likely. Yogi
  2. Just a little follow-up. Want to thank Smashtv for all he has done through the years, would have posted to his thread in the News forum but I've no access there. Placed an order for Seq v4 FP with Modular Addicts. They shipped the next day and arrived here 5 days later. Good job MA. Yogi
  3. Yep, one decoder per 4 boards. Yogi
  4. Hi, Yes, that setup file sets the options for mapping CS controls to firmware routines, within limits. So rearranging LEDs, buttons and encoders connections is a matter of changing this file and compiling. To add new features would require adding to the main source. If you look at this file closely, you'll see a section for the build options of MB6582 or sammichSID; these flags are for the re-arranged CS of these projects. They use SR IO matrices for all control elements. As opposed to the 1 to 1, SR I or O pin to a CS Element as you do with the standard build. Like all the synth projects, most everything can be controlled over midi with CC and SysEx messages without changing the code. The most min system would be a Core and a SID board, this is playable via midi. With a min CS (step B), synth prams can be changed through the menu layers. The Full (step C) CS allows less button pushing, having a dedicated controls or displays for most of the synth sections. The MB6852 or sammichSID just improve on the full CS by minimizing shift regs. Even though there is code for a specific control or LED the synth will work if it's not attached. From the MB6582 Wiki . So you could use the base board, without the bottom SRs, and a min CS connected to the first core's J8/9 and I think just the stock FW on the cores ( each with a different ID). If anyone can confirm? Yogi
  5. Having a spare STM32 is a good thing, lots of uses :) Glad it was only the cable, Yogi
  6. Congrats on your SID synth! The MB6582 is basically 4 cores and 8 SID boards copied to a single PCB. The cores are networked and the code for the cores is slightly different then the stock app. If you can poke around in the code, could change the FP options to your own needs and build the FP as you please. Don't know if you have any programming experience but it's not too hard and there is plenty of info on the wiki. There is a new MB board supplier They are carrying the main board for $24.99, http://modularaddict.com/manufacturer/midibox So using the main board saves you alot over modules. Without the interconnecting. There are a few threads here on the PSU and the MB6582 is flexible for setting up the power supplies. Good luck, Yogi
  7. I can't recall anything special I did, but I've reflashed via ST-link more then once. Can't recall if I held the reset or something. As I understand, the mini-USB is always enabled with the ST-LINK processor that is connected to the 'F407 (by JTAG?). Do you have the two 'ST-LINK' jumpers on CN3 header, they connect the ST-LINK to the core. Yogi
  8. Hey man..

    Reading Your comments in the MB TIA thread - i'm getting the same stuff in the Manager/MAX thing - greyed out and not working with any rev of MAX. Did you ever get this to work on a Windows system?

    1. Show previous comments  2 more
    2. mrspring


      Antichambre did some live support on this yesterday, and the issue was caused by an out of date MAX file, or a possibly corrupted one.. It's ALL GOOD now.. :)

    3. Antichambre


      MAX Manager was fine, I checked and I refreshed the box firmware on September last year. Maybe you downloaded it before and it was out of date. Best

    4. mrspring


      Correction - it was the Cart .hex that had the issue I think - whatever .hex i was using, it was not correct. The MB TIA would respond in part to MIOS Studio keyboard, but the notes played were not in any logical tuning, but the device would not connect with MAX. Antichambre passed me the cart .hex directly and that fixed everything.. Fairly sure i only ever downloaded files from places in the official thread and the PM one, so i guess they got corrupted, or were non working early editions with the same filename. As of now, it's working, and i'm exploring patches!

  9. Looks like a minor fix, not a problem for me :) Looking forward to the board. Yogi
  10. So after many months and a little testing I ran into a problem with the build, hex upload doesn't work right. But it seems to be a general Linux issue. The issue is already reported in this thread, And a work around Midi In/Out and File browser works fine; haven't tested any other tools. Still to test the Hex upload work around so time will tell. Yogi EDIT: Tested upload with work around, direct entry of file path works fine. Yea!
  11. Hi urtzurd, Well, for options A and B J73 should be bridged to route +5V from an external PSU; and for Option C J73 is can be used to route to/from the on board +5V regulator. So for all options the J73 footprint is used, just in very different ways depending on how you plan to supply power. I think that on the parts list, it is saying that the use of a header is mainly needed for option C, as A and B only needs a wire bridge. Of course one could use a header and a shunt for A and B, OR not use a header for C and solder jumper wire directly to the solder pads. There are so many options to supply the board that it can be confusing but with a little study of the schema and reading the forums it will make some sense. Yogi
  12. I can't say that Notepad++ is the best way to work on projects; and if you want to dive into a proper IDE, Eclipse would be my first choice. In Npp you can trace a var to a point, you just have to setup the search. Eclipse would help with organizing your project and auto completion is handy, so getting to know it can speed your coding but it's not going to tell you if your logic is wrong. For this you would need a simulator or ICE tool so you can step through code and see the effect on memory or registers. I think STM does have tools but never looked. I'm a "code; compile; crash; repeat" guy :) Yogi
  13. OK, so that kind of leaves the changes you made. mios32_config.h is where the boot string is defined, it gets displayed till the app changes the output to the LCD. Not familiar with NG and when it rewrites the LCD. What I usually do is make a copy of a project and place it in a new folder in my MIOS32 directory, alongside the trunk folder. This way I have the original code in 'trunk' and my changed code in the other folder. From then on, I run Make in the edit folder and this produces the new hex in this folder. From MIOS Studio I then upload this hex. I haven't worked on the NG scr but the process has worked well for what I have been working on. Check that MIOS Studio is pointing to your build. If that is correct then review the changes you made and try only the boot string for a start. The only other thing I can think of is on a few occasions I have made changes to a scr file and run Make, BUT forgot to save my scr changes back to disk. Of course Make built a hex but based on the old scr! So ' Edit, Save and then Make'. I'm using Notepad++ with the 'NppExe' plugin. Yogi
  14. Generally you would just need to upload the new hex to the core and it should display the changed text when it boots. I've never known what the release.sh is for, I assumed it was for IDE use. Have you uploaded the pre-compiled hex to make sure the defaults works? I'm not sure about NG, do you have an SD card attached? It may be hanging without a card, but I don't know for sure. Yogi
  • Create New...