Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by borfo

  1. On 4/16/2019 at 10:30 AM, ilmenator said:

    For the FM a PIC18F452 is the standard option - I can provide that as well, still have some of those around I think. To the US shipping will be 7€ including tracking. It's cheaper (4,70€) if you don't want tracking, but I'm not sure I would recommend that...

    Looks like shipping from here to the states with a tracking number might be about $14CDN - without a tracking # would be about $7.  (seems expensive for such a tiny parcel - not sure if I could squeeze PICs into lettermail though...)Jaytee, buying from Ilmenator seems like the right move...


      Within Canada would be a lot cheaper, if any Canadians need PICs. 

  2. Have you looked at http://www.ucapps.de/ yet, or just the forums?  There are several midibox synths.  The Midibox SID is a commodore SID synth; there's an FM synth.  Midibox CV V2 isn't a synth, but it's also interesting: http://www.ucapps.de/midibox_cv_v2.html.  If you look around the wiki http://wiki.midibox.org/ and old forum threads, you can find a bunch of examples of people making custom synths and MIDI controllers with features that didn't previously exist in MIOS.

    You are not restricted to the API in MIOS - take a look at the app.c files in some of the projects (eg: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fsrc%2Fapp.c) - there are a bunch of hooks in that file that you can use to launch custom stuff.


    • Like 1
  3. I'm thinking about modifying MBNG slightly to control a headless/knobless audio mixer I'm building (the plan was always to make it a MIDI-controlled device, controlled from external software or hardware I want to build a UI for, but I thought why not use the NG itself if possible...)  The NG would serve as the control interface for the mixer (as well as doing other stuff, controlling synths, whatever you'd normally do with it).  The mixer controls would send MIDI (OSC could work too, but instead of leaving the device via an out port, I'd like to send to one of the NG's own in ports.  That way I could use the

    APP_MIDI_NotifyPackage(mios32_midi_port_t port, mios32_midi_package_t midi_package) 

    hook in app.c to monitor for incoming MIDI control signals meant for the mixer (including MIDI sent from the NG itself, as well as any external mixer control signals that I might send in from other devices.)  If a mixer control message is found, the NG would send a control signal to the mixer hardware via I2C.

    Can the NG send MIDI to itself in a way that would be caught by the APP_MIDI_NotifyPackage hook?


    I suppose I could physically connect an NG out port to one of its own in ports, but it'd be cleaner to do it internally...


    Also, is it possible to access values of Midibox NG control elements (like, the current value of an encoder for example) from within app.c?


  4. Yeah, but better to pay shipping than to pay full price I guess.

    Hm...  The laptop PSU option is interesting...  I have a Surface Pro power supply here that puts out 12v and has a USB charging port.  Do you just wire your laptop power supply directly into the 5v and 12v rails?  Or do you run it through linear voltage regulators?  Are laptop power supplies internally regulated?  What PSU are you using?

  5. Could I use separate power supplies (a 9vac PSU and a 5vdc PSU) plugged into the same mains power source?  Would that work, or would I have to worry about the possibility that they'd have different ground references (and potentially unexpected voltage differentials) despite being plugged into the same mains power source/ground? 


    ...I've got one C64 psu with working 9vAC and broken 5vDC, and another with working 5vDC and broken 9vAC...  

  6. Argh.  Looks like that's it right there.  I just read directly from the PSU pins and I'm only getting 4v (not sure why I didn't read straight from the PSU before, I guess because the SID board was already wired up and I read 4.6v on the 5v rail there).  Frustrating - this is the second one I've bought.  I guess they're all pretty old and deteriorating at this point...


    I guess I'll work on another power solution.  Thanks a lot for the help, Noise Generator.

  7. Thanks everyone - I was thinking it might be restarting over and over again as well.  The MIDI circuit seems fine (I've tested it in a variety of ways, and I do get communication back and forth from the core including confirmation in MIOS Studio that the bootloader is running).

    Power is coming from a C64 PSU, so the 5v rail is regulated within the PSU.  Unfortunate if it's not working properly, since this is the second one I've bought (AC on the first one was broken), and they're not cheap.

    I suppose building a minimal core on a breadboard is probably the sensible next step, and then if it is the PSU I guess I'll power it some other way, since the C64 PSUs seem a bit unreliable.

  8. Thanks - I tried the linux 1.2 version of pk2cmd, and it really seems to be working ok to flash the bootloader to the PIC...  I'm inclined to think it's probably some kind of problem with my MB-6582 core board.  Can anyone confirm that those "f0 00 00 7e 40 00 01 f7" upload request messages coming 120 times per second from the bootloader-flashed PIC is way faster than they should be sent?  ...and if so, does anyone have any idea what might be wrong with my core board to make that happen?  Any ideas what I should be looking at?  All the voltages on the PIC seem right - just below 5v.

  9. 2 hours ago, fcebreros said:

    the PICKit2 works, I have used a chinese version I got for under 20$  and had no problem. I couldn't find an easy way to change the ID's (but there is a way)
    but had no problem changing the ID's afterwards with the MIOS tool.

    What Operating System and software did you use to flash the PICs?  I'm having some trouble with mine - I posted in the SID forum about it.

  10. I'm trying to program four PIC18f4685's for my MB-6582 from scratch, and I'm having problems...  I seem to have at least sort of successfully flashed the bootloader using a Pickit 2 and MPLAB X, but I can't flash MIOS to the SID over MIDI in MIOS Studio.  I can query the core, and it says the bootloader is running, but whenever I try to flash any .HEX, MIOS Studio times out and says "no response from the core after 16 attempts.

    The Core is sending out these messages (which I guess is the upload request) about 120 times a second all the time the SID is powered on...  From other forum posts, it seems this is way too fast - should these messages be sent that often, or is there something wrong with the clock speed on the PIC or something?  Anyone have any thoughts?  Voltages seem fine on the PIC...

    [25442.111] f0 00 00 7e 40 00 01 f7
    [25442.120] f0 00 00 7e 40 00 01 f7
    [25442.128] f0 00 00 7e 40 00 01 f7
    [25442.136] f0 00 00 7e 40 00 01 f7
    [25442.145] f0 00 00 7e 40 00 01 f7
    [25442.153] f0 00 00 7e 40 00 01 f7


    I've never used MPLAB or flashed a PIC before, so it is possible I didn't flash the PICs correctly...  (although MPLAB said the flashes were successful) Is it possible that flashing the bootloader in an incorrect way in MPLAB could somehow make the PIC's clock go way too fast?

    Or, is it possible that the circuit I used to connect the PIC physically to the PICKIT 2 could have been incorrect in a way that could make the clock speed go way too fast?  (there is a pcb with the PICKIT that fits smaller PICS and connects to the PICKIT - I just connected the appropriate pins on that pcb to the pins on my PIC18F4685s via breadboard leads.)

    ...even thought MIOS Studio reports that the bootloader is running when it queries the core?


    Is there a complete HEX of the MB-6582 PICs that I could try flashing in MPLAB so I don't have to install MIOS via MIDI?


    Any help or pointers would be much appreciated. 

  11. Hi - I think I've tested it on a raspberry pi...  It should work anyway.


    ...Are you sure you're installing Mido into Python3, not just into Python 2?  Try "pip3 install mido" and rt-midi...  If that doesn't work you You might also try installing as your user rather than sudoing it.  You could also try installing python3-mido and rt-midi from your package installer (if they're there) instead of through pip.


  12. You could try the python BLM implementation - if you do, let me know if it works for you: 

    edit:  Oops - didn't notice that you were already aware of the python BLM thing.  because the virtual BLM and pyBLM use totally different codebases, I thought the issue you're having under the virtual BLM software with conflicting device names might not occur with pyBLM.  Might be worth giving pyBLM a shot now rather than trying to work out the issue in virtual BLM if you're planning on using pyBLM anyway. 


    ...pyBLM should work in windows too, I think, provided the dependencies will install.

  13. Thanks everyone - I'm not sure they're fried, but they're certainly corrupted, and the bootloaders on all of them are no good.  I think I overvolted the board while I was impatiently trying out some ill-considered power supply ideas after my commodore 64 psu arrived DOA.  I tried flashing one with an arduino PIC programmer circuit I found on the internet, and the burn failed.  

    I've found someone local to borrow a Pickit 2 from and I'll try reflashing my existing PICs...  If that doesn't work I just bought four compatible PICs for cheap on eBay, so I should finally be able to get this thing working one way or another.

  • Create New...