Jump to content

dwestbury

Members
  • Posts

    271
  • Joined

  • Last visited

  • Days Won

    25

Everything posted by dwestbury

  1. OMG! I'm so sorry for stirring such a painful memory. ...And equally sorry for your losses. I lost a house and everything I owned in a fire some years back, I'm obviously grateful for my health and well being. Good to see you in the forums, hopefully enjoying better times. Best to you. -Darrell
  2. Anything left? Oh and nice encoded MSG... ˇ T h a n k s f o r t h e M I D I b o x , T K !
  3. Some years later I'm finding this thread about KiCAD, at exactly the time I'm getting familiar with it. I see that the basics section is still up: http://wiki.midibox.org/doku.php?id=kicad and it provides a useful foundation. I also REALLY like the video series from Peter Dalmaris on Udemy: https://www.udemy.com/course/kicad-like-a-pro-2e/ The price on this course varies from time to time, but I managed to get it on a promotion for $9.99 USD, so keep an eye out for that. Switching back to the topic of a MIDIbox library... The suggestions from @Psykhaze make a lot of sense, based on projects I've worked on (e.g., MB-6582). Has anyone made such a library available?
  4. I can certainly help out with preprogrammed PICs. I also have left over inventory of all the other key ICs to make a MB6582 or sammichSID Send me a DM for details... -Darrell
  5. Yes, exactly. I had the headers in place as an interim step, while I waited for 7P circular DIN connectors to show up in the mail. The final Base PCB build looks like this:
  6. This video shows you how to use a C64 to configure your ARM2SIDs for full stereo, using Socket mode. If you want to fast-forward through the “discovery, trial and error”, skip to ~28:00 Once your ARM2SID configuration is saved to the internal flash memory, you can move them into your MIDIbox for Stereo pleasure... Cheers
  7. The PIC 18F4685 is an 8-Bit Microcontroller. The datasheet is here: https://ww1.microchip.com/downloads/en/DeviceDoc/39761c.pdf Generally speaking, you can program it in C / C++ using a supported IDE, but the firmware for MB6582 is actually programmed in Assembly language, for both performance and space efficiency on the limited chip memory. The MIOS-8 codebase is maintained on Github here: https://github.com/midibox/mios8 You download the MIDIbox SID v2 firmware here: http://www.ucapps.de/mios/midibox_sid_v2_044.zip Once downloaded, you can see the raw and uncompiled (but well commented) assembly code for MB-6582, here: .../midibox_sid_v2_044/setup_mb6582.asm (there are lots of .inc files to explore in the .../src folder as well)
  8. Some basic "sanity check" steps here... 1) Perform some voltage level tests for all the IC Sockets (This view assumes 8580 SIDS and Power Supply Option E) 2) Use an oscilloscope to ensure that your Oscillator frequency is reading ~10 Mhz, from both pins 13 and 14 on your PIC (highlighted by a yellow box below)
  9. I have to admit that I haven't experienced this particular issue, so I'm sure others will have some good suggestions here, but one other consideration that comes to mind is the timing crystal. In one of my builds I made the mistake of using the wrong capacitors, because I didn't check them properly before soldering. By outward appearances, they looked identical to the correct caps, but they had the wrong capacitance, which completely messed up the crystal oscillator timing being sent to the PIC. This took me quite a while to figure out...
  10. @Al99Great to hear that the PICs arrived across the ocean. I tested them extensively in my own MB-6582, including menu navigation, MIDI handling from my DAW, as well as successful handshaking with MIOS, etc. You shouldn't have to do any additional programming with them at all. Just plug-and-play. With regard to the jumpers you referenced (J11), this controls which PIC will be enabled to talk back to your MIDI interface. This is required for programming with MIOS. All of the PICs will receive a copy of the incoming MIDI signal, but the only the correctly numbered PIC will respond. For the most part, you should be able to leave J11 set to position 1 (right-hand-side), as this enables bi-directional communications with CORE 1 (using ID: 0). If a new MIOS or MB6582 firmware were to come out, you could simply program CORE1, then reboot your MB-6582, while holding the menu button to clone to the other PICs. So, really no need to ever move the jumper again once all PICs are programmed and have the correct device IDs. With regard to the issue you highlighted about your screen showing all blank squares. it could simply be a LCD brightness or backlighting issue. have you tried slowly turning the trimmer potentiometers in PI or P2_CORE1? Good luck! -Darrell
  11. dwestbury

    midiphy MatriX :)

    This looks like a brilliant piece of hardware. Is the Matrix a modern derivative of the BLM 16x16? Assume the key use case is sequencing and scene launching? I wouldn't think those lovely keys could be used for finger drumming or velocity sensitive performance, etc. Irrespective, it looks gorgeous!
  12. dwestbury

    Cables!!

    I love the C64 1571 cable management system ;-)
  13. If you really wanted to, you could tap the primary Arm2SID and route the cables yourself to get into 2nd / 3rd SID capabilities. There's some fairly useful documentation on the site: https://www.retrocomp.cz/produkt?id=20 However, IMHO having the second (dummy) Arm2SID is a much more convenient choice for managing 2*SID stereo audio.
  14. I guess I should also add that the Arm2SID is capable of emulating up to 3 SIDs and includes FM synthesis capabilities... These features won't matter much for a MIDIbox SID build, but hey, they're solid extra features for your C64 ;-)
  15. The recommendation to modify the board was based on speculation. This turned out not to be necessary in my testing... You can simply drop the Arm2SID set into the required sockets and jam away. The second (dummy) Arm2SID is basically only there to intercept the Chip Select signal and pass it along to the active Arm2SID, which performs it's double-duty, then passes the audio-out for the second SID back via the bridge cable. I'd imagine that the only real reason that someone might want to purchase an Arm2SID over two regular ArmSIDs is to save a little money. The Arm2SID set costs ~48 eur versus two separate ArmSIDs @ 28 eur each or 56 eur for the pair. So really only a modest savings of ~8 eur per pair, but when you multiply that by the four cores for a fully populated MB-6582, now you're up to a 32 eur build cost difference.
  16. The status text should show that Programming and Verification are complete.
  17. This process can be very frustrating when you're trying to figure out where a particular problem is. My own posts in these forums can certainly attest to that. I spent days and days struggling through various dead ends, until I finally found a process that ultimately worked well for me (e.g., the document linked above). Along the way, I realized that the MIDI interface I was trying to use (a Native Instruments Komplete Audio 6 Mk2) was not properly passing SysEx messages to my PICs via MIOS. This was one of my first issues. Unfortunately, I had completely destroyed my PIC and base PCB with all my removing and de-soldering and part replacements, while I worked that out. Now I have an 'iConnectivity MIO XL', which is one of the MIDI interfaces on the MIDIBox Interface Whitelist (http://wiki.midibox.org/doku.php?id=midi_interface_whitelist). Other issues I encountered included some mismatched capacitors on the crystal above my PIC, which made communication synch to MIOS impossible. I also had at least one bad PIC that accepted the bootloader from MPLAB, but wouldn't function at all in my MB-6582. In my case, taking some time away from the issue to clear my head was key, combined with some very useful feedback and patient input from the community in these forums.
×
×
  • Create New...