hi great news with your deivce, congrats, looks and sounds pretty convincing.
And thanks for all those information, I kind of already have read over that, and I did not mean the J11 jumpers but the J11 Core jumpter, i dont really get those as one can short the tx rx from the PICS.
Anyway, did oyu mean this hex? setup_mb6582.hex ?
I will try now to flash the MIOS again and then upfinally recognize it with my MIOS on the mb6582 board, will also probe around witht he scope if it wont work, but i am pretty sure MIDI is working just fine until the PICs.
Since my hardwareloop is recognized and I get the sysex message out:
[300922.170] f0 00 00 7e 40 00 01 f7 every second or so
edit1:
short update, I did get another badge of fresh PICs yesterday via the nice microchip sampling service, cause I thought, maybe i messed up with some configurator bytes? is that even possible with the pickit programmer and the diamex???
I am only very very familiar with code composer and the Texas Instruments controllers, Atmel I had before because of the great work of Oliver at mutable instruments.
What puzzles me a bit is the complicated way Atmel works with its fuse and other settings, with the Texas controllers you just flash a hex file and everything else you dont have to care, or someone else already took care of in the code, Atmel you have a working hex files but the code wont work because someone forgot to tell you about those fuse settings… seems kind of unnecessary ot me.
So because of that expirience I wondered or still wonder, is it the same with the PIC, can I possibly mess up a perfect hex file with wrong config bit settings, I read :
https://www.eevblog.com/forum/microcontrollers/pic18f4685-config-bits/
and there it at least says so.
So enough of my rant back to business:
I did flash a couple of those PICs I got, btw i also got some PIC18LF devices, are those the same, what does the L stand for, at least i could flash them also.
Now after yesterdays struggle I think something might have changed in my connections ( I am programming on a prototyping solderless board right now, so open connections and too much parasitic capacitance could actually be a thing), because now the hex code seemed to work fine and I can now also verify the program ( I assume the pic program checks if the actual code on the PIC matches the imported hex file from my PC )
Then I connected the PIC back into the core module, startet Mios.exe and a couple of times the same as yetserday no MIOS detected and so on.
I also flashed the troubleshoot PIC code on one device, strangly no echo occured, BUT the one pin on J14 I think toggled when I did send a random code over the MIOS, so flashing probably works I thought.
Well after some more fiddling, the first time the upload of the mios hex file did work, it stated MIOS8 detected, that was on device id 0, then i switched on dev 1, it did not detect anything, then back to dev 0, again no mios detected, hmmm.
But anyway I assume MIOS studio got some issues for itself, and i cannot blame it its hard to program communication stuff on pc and midi then having to rely on some external cheap chinese midi gear like i got and so on.
anyway after restart it detected MIOS8 again and so on, then i had to leave home for work, but the hopes are high to produce a sound until the end of the week.
And just a headsup, i inserted a pic wrong way around one time ( with 10 pics and on and off troubleshooting and all quick and on a messy workbench, this is 100% sure to happen to anyone
) just wanted to say i “think” it is still working, at least i could reflash and verify it.
thats all for now.