With regard to the issue you highlighted about your screen showing all blank squares. So, really no need to ever move the jumper again once all PICs are programmed and have the correct device IDs. 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. This is required for programming with MIOS.Īll of the PICs will receive a copy of the incoming MIDI signal, but the only the correctly numbered PIC will respond.įor 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). With regard to the jumpers you referenced (J11), this controls which PIC will be enabled to talk back to your MIDI interface. You shouldn't have to do any additional programming with them at all. 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. 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 to hear that the PICs arrived across the ocean. I also had at least one bad PIC that accepted the bootloader from MPLAB, but wouldn't function at all in my MB-6582. Other issues I encountered included some mismatched capacitors on the crystal above my PIC, which made communication synch to MIOS impossible. Now I have an 'iConnectivity MIO XL', which is one of the MIDI interfaces on the MIDIBox Interface Whitelist ( ). 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. 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).Īlong 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. My own posts in these forums can certainly attest to that. This process can be very frustrating when you're trying to figure out where a particular problem is. I tried programming a chip with mplab ide 5.45 as i tried with mbhp burner but the ic socket broke (i am finding that the circular is much better than the flat so I am replacing) and the hex file downloaded from the pic has the same beginning and and end lines as the hex file but different inbetween, why am I so unsuccesful at getting mios studio to see the core, I built 2 cores and programmed chips with mplab ide and mbhp burner but mios always says no response from core, why am i so unsuccessful, is it my soldering, my midi lead or my chip programming? I hoped if i just follow instructions and schematics everything turn out just fine but not so, why?
0 kommentar(er)
