toneburst Posted October 8, 2006 Report Share Posted October 8, 2006 I'm having major problems uploading MIOS to the core PIC for my MIDIBox SID.I get the follwing when I try to upload:Starting upload of update_without_installed_mios.hexHex file contains code in MIOS range, forcing reboot!Received error code 0C: MIDI IN Frame ErrorThis was an expected error - please ignore!Received Upload RequestSending block 00000000-000000FFReceived error code 0C: MIDI IN Frame ErrorSending block 00000400-000004FFError: Received unexpected Upload RequestSending block 00000400-000004FFReceived error code 0B: MIDI IN Overrun ErrorSending block 00000400-000004FFError: Received unexpected Upload RequestSending block 00000400-000004FFReceived error code 0B: MIDI IN Overrun ErrorSending block 00000400-000004FFError: Received unexpected Upload RequestSending block 00000400-000004FFReceived error code 0B: MIDI IN Overrun ErrorSending block 00000400-000004FFError: Received unexpected Upload RequestSending block 00000400-000004FFReceived error code 0B: MIDI IN Overrun ErrorSending block 00000400-000004FFError: Received unexpected Upload RequestSending block 00000400-000004FFReceived error code 0B: MIDI IN Overrun ErrorSending block 00000400-000004FFError: Received unexpected Upload RequestSending block 00000400-000004FFReceived error code 0B: MIDI IN Overrun ErrorSending block 00000400-000004FFError: Received unexpected Upload RequestSending block 00000400-000004FFReceived SysEx message of less than 8 bytesReceived error code 0B: MIDI IN Overrun ErrorSending block 00000400-000004FFError: Received unexpected Upload RequestAborting after 16 errorsI'm definately getting a MIDI in signal between pins 26 and 31 of the main PIC chip, and between pin 31 of the PIC and pin 6 of the Optocoupler. I can't try the MIDI-OX loopback tests, since I'm on a Mac, but I'm pretty sure the PIC is receiving something from the Core's MIDI-In port now.What else can I try?Incidentally, MIOS Studio doesn't seem to work on my PPC-based Mac G5 (MacOS 10.4.8). It runs OK, but the GUI doesn't redraw correctly, and I can't route my MIDI in and out ports to MIOS. Oddly, it works fine on my Intel MacBook Pro.Alexhttp://www.toneburst.net Quote Link to comment Share on other sites More sharing options...
TK. Posted October 8, 2006 Report Share Posted October 8, 2006 I remember that I read about a similar issue short time ago somewhere else in the forum?Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
toneburst Posted October 8, 2006 Author Report Share Posted October 8, 2006 Hmmm... that'll be me too... I double-posted, I'm afraid.Alexhttp://www.toneburst.net Quote Link to comment Share on other sites More sharing options...
moogah Posted October 8, 2006 Report Share Posted October 8, 2006 Perhaps this has already been resolved..Hex file contains code in MIOS range, forcing reboot!Can you specify your entire upload setup?What kind of PIC are you using?Where did you get it?Was it preloaded with MIOS? (I believe both Mike and Smash sell preloaded PIC's only)What program are you using to upload?Can you specify "update_without_installed_mios.hex" I don't recall a file with that name. Quote Link to comment Share on other sites More sharing options...
toneburst Posted October 8, 2006 Author Report Share Posted October 8, 2006 Hi moogah!thank for getting back to me!Not quite sure what you mean about this already being resolved. I may be missing something obvious though....My Setup is:• SmashTV PIC with Bootstrap v.1.2 preloaded• Using MIOS Studio to upload running on an Apple MacBook Pro under MacOS 10.4.8 using NI Kore and M-Audio MIDISport 2x2 USB MIDI interfaces (tried both with similar results).• I got the HEX file from the MIOS downloads page, it's the very first file in the list. maybe it's completely the wrong one....Ah...... I may have answered my own question here. Is it completely the wrong file?Alexhttp://www.toneburst.net Quote Link to comment Share on other sites More sharing options...
smashtv Posted October 8, 2006 Report Share Posted October 8, 2006 Is it completely the wrong file?Hi Alex....Sorry your having troubles......"update_without_installed_mios.hex" is the wrong file, you should be sending "mios_v1_9c_pic18f452.hex"BestSmash Quote Link to comment Share on other sites More sharing options...
smashtv Posted October 9, 2006 Report Share Posted October 9, 2006 I moved the other thread about this same issue (now known as "Toneburst MIOS Upload Issues Thread 2") here in hopes we can end this crossposting madness. ::)BestSmash Quote Link to comment Share on other sites More sharing options...
toneburst Posted October 9, 2006 Author Report Share Posted October 9, 2006 Doh!!I'll give that other file a go as soon as I get a chance.Incidentally SmashTV, do you remember that red neg. LCD you got for me? I finally got around to hooking it up at the weekend, and it turns out it IS pink, as a couple of people suggested, and the background is definitely not black, as the pic on the Crystalfontz site indicates. I'm not too disappointed though- it actually looks quite nice! I'm considering getting a white neg. one and putting some sort of coloured gel over it. That way, I can have any colour I like.Alexhttp://www.toneburst.netPSsorry about the cross-posting Quote Link to comment Share on other sites More sharing options...
toneburst Posted October 9, 2006 Author Report Share Posted October 9, 2006 OK, well I tried the correct file, but sadly it didn't work.Different set of errors this time though. Not sure what that means though.Looks like the MIDI in still isn't working.I'm off to work now.Alexhttp://www.toneburst.netStarting upload of mios_v1_9c_pic18f452.hexHex file contains code in MIOS range, forcing reboot!Received error code 0C: MIDI IN Frame ErrorThis was an expected error - please ignore!Received Upload RequestReceived error code 0B: MIDI IN Overrun ErrorSending block 00000400-000004FFError: Received unexpected Upload RequestSending block 00000500-000005FFReceived error code 0B: MIDI IN Overrun ErrorError: Received unexpected Upload RequestSending block 00000500-000005FFReceived error code 0B: MIDI IN Overrun ErrorSending block 00000500-000005FFError: Received unexpected Upload RequestReceived error code 0B: MIDI IN Overrun ErrorSending block 00000500-000005FFError: Received unexpected Upload RequestReceived error code 0B: MIDI IN Overrun ErrorSending block 00000500-000005FFError: Received unexpected Upload RequestSending block 00000500-000005FFReceived error code 0B: MIDI IN Overrun ErrorSending block 00000500-000005FFError: Received unexpected Upload RequestReceived error code 0B: MIDI IN Overrun ErrorSending block 00000500-000005FFError: Received unexpected Upload RequestSending block 00000500-000005FFReceived error code 0B: MIDI IN Overrun ErrorError: Received unexpected Upload RequestReceived error code 0B: MIDI IN Overrun ErrorError: Received unexpected Upload RequestReceived error code 0B: MIDI IN Overrun ErrorError: Received unexpected Upload RequestSending block 00000500-000005FFReceived error code 0B: MIDI IN Overrun ErrorSending block 00000500-000005FFError: Received unexpected Upload RequestReceived error code 0C: MIDI IN Frame ErrorReceived SysEx message of less than 8 bytesReceived error code 0B: MIDI IN Overrun ErrorError: Received unexpected Upload RequestSending block 00000500-000005FFReceived error code 0B: MIDI IN Overrun ErrorSending block 00000500-000005FFError: Received unexpected Upload RequestSending block 00000500-000005FFReceived error code 0B: MIDI IN Overrun ErrorSending block 00000500-000005FFError: Received unexpected Upload RequestAborting after 16 errors Quote Link to comment Share on other sites More sharing options...
toneburst Posted October 9, 2006 Author Report Share Posted October 9, 2006 I think I was getting MIDI feedback there, for some reason....Alexhttp://www.toneburst.net Quote Link to comment Share on other sites More sharing options...
TK. Posted October 9, 2006 Report Share Posted October 9, 2006 So, it is working now?Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
toneburst Posted October 9, 2006 Author Report Share Posted October 9, 2006 Ill run another test tomorrow Thorsten,I've been distracted by non MIDIBox-related projects this evening (I'm working on a little music commission that I've been putting off for too long).Thanks once for all your help on this (and of course, for the whole MIDIBox thing :-) ).Alexhttp://www.toneburst.net Quote Link to comment Share on other sites More sharing options...
toneburst Posted October 10, 2006 Author Report Share Posted October 10, 2006 Thanks once for all your help on this (and of course, for the whole MIDIBox thing :-) ).That should have been "Thanks once again..." of course. I need a proof-reader here :[Alexhttp://www.toneburst.net Quote Link to comment Share on other sites More sharing options...
Mr modnaR Posted October 10, 2006 Report Share Posted October 10, 2006 music commission sounds interesting, what is it? tv ad? Quote Link to comment Share on other sites More sharing options...
toneburst Posted October 10, 2006 Author Report Share Posted October 10, 2006 Believe it or not, it's music for an exercise class. The problem is, it's for people using rowing-machines, which means it has to be really slow- ie 60 to 120bpm. And it keeps changing tempo too. Quite tricky keeping things interesting for 30+ minutes, especially at a really slow tempo. And it can't be too rhythmically interesting because it'll put them off their stroke. Hmmm...Alexhttp://www.toneburst.net Quote Link to comment Share on other sites More sharing options...
toneburst Posted October 10, 2006 Author Report Share Posted October 10, 2006 So, it is working now?Best Regards, Thorsten.Nope :-(I've tried 2 different MIDI interfaces, under XP and MacOS X. I seem to get different error messages every time. This is my last attempt:Starting upload of mios_v1_9c_pic18f452.hexHex file contains code in MIOS range, forcing reboot!Received Upload RequestReceived SysEx message of less than 8 bytesSending block 00000400-000004FFReceived error code 0C: MIDI IN Frame ErrorThis was an expected error - please ignore!Received error code 0C: MIDI IN Frame ErrorReceived SysEx message of less than 8 bytesSending block 00000500-000005FFError: Received unexpected Upload RequestSending block 00000500-000005FFError: Received unexpected Upload RequestSending block 00000500-000005FFReceived SysEx message of less than 8 bytesReceived unexpected MIOS SysEx message = 40000140000E0C01F7 expected = 00007E4000Received unexpected MIOS SysEx message = 40000140000E0C01F7 expected = 00007E4000Received SysEx message of less than 8 bytesReceived unexpected MIOS SysEx message = 40000140000E0C01F7 expected = 00007E4000Received SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived unexpected MIOS SysEx message = 40000140000E0C01F7 expected = 00007E4000Received SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived unexpected MIOS SysEx message = 40000140000E0C01F7 expected = 00007E4000Received SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived unexpected MIOS SysEx message = 40000140000E0C01F7 expected = 00007E4000Received SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived unexpected MIOS SysEx message = 40000140000E0C01F7 expected = 00007E4000Received SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived unexpected MIOS SysEx message = 40000140000E0C01F7 expected = 00007E4000Received SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived unexpected MIOS SysEx message = 40000140000E0C01F7 expected = 00007E4000Received SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived unexpected MIOS SysEx message = 40000140000E0C01F7 expected = 00007E4000Received SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived unexpected MIOS SysEx message = 40000140000E0C01F7 expected = 00007E4000Received SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived unexpected MIOS SysEx message = 40000140000E0C01F7 expected = 00007E4000Received SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived error code 0C: MIDI IN Frame ErrorReceived error code 0C: MIDI IN Frame ErrorSending block 00000500-000005FFReceived error code 0C: MIDI IN Frame ErrorReceived error code 0C: MIDI IN Frame ErrorSending block 00000500-000005FFReceived error code 0C: MIDI IN Frame ErrorSending block 00000500-000005FFReceived SysEx message of less than 8 bytesReceived error code 0C: MIDI IN Frame ErrorReceived error code 0C: MIDI IN Frame ErrorSending block 00000500-000005FFReceived error code 0C: MIDI IN Frame ErrorSending block 00000500-000005FFReceived SysEx message of less than 8 bytesReceived error code 0C: MIDI IN Frame ErrorReceived error code 0C: MIDI IN Frame ErrorSending block 00000500-000005FFReceived SysEx message of less than 8 bytesError: Received unexpected Upload RequestSending block 00000500-000005FFError: Received unexpected Upload RequestReceived SysEx message of less than 8 bytesSending block 00000500-000005FFReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived SysEx message of less than 8 bytesReceived error code 0C: MIDI IN Frame ErrorSending block 00000500-000005FFReceived error code 0C: MIDI IN Frame ErrorSending block 00000500-000005FFReceived error code 0C: MIDI IN Frame ErrorSending block 00000500-000005FFReceived error code 0C: MIDI IN Frame ErrorSending block 00000500-000005FFReceived error code 0C: MIDI IN Frame ErrorAborting after 16 errorsI tried doing the PC test 2 from the MIDI problems page, but can't work out how to do it. Is it likely to be a problem with the MIDI interface though (given I've tried 2 different ones)?Any help very gratefully accepted.Alexhttp://www.toneburst.net Quote Link to comment Share on other sites More sharing options...
Mr modnaR Posted October 10, 2006 Report Share Posted October 10, 2006 wow! crazy-ass-electro-rowing-mutha-funkers. ;D Quote Link to comment Share on other sites More sharing options...
toneburst Posted October 10, 2006 Author Report Share Posted October 10, 2006 With error-messages, yeah....:-(Alexhttp://www.toneburst.net Quote Link to comment Share on other sites More sharing options...
toneburst Posted October 10, 2006 Author Report Share Posted October 10, 2006 OK, I think I've really f*cked it now....After MIDI-Ox crashed completely (can't believe how flakey MIDI is under Windoze), I still can't upload MIOS after the Nth attempt (same selection of error messages), but now the LCD shows a row of bars, but this time with a line across them.Any clues anyone, I'm completely lost and this is starting to take over my life!!Alexhttp://www.toneburst.net Quote Link to comment Share on other sites More sharing options...
carsten_the_dane Posted October 10, 2006 Report Share Posted October 10, 2006 Hey Toneburst. As you have probably seen, i have been flooding the forum with questions lately. So my advice will probably not be worth much. BUT, i have had problems with midi in the last couple of days, and i have also had problems with misbehaving LCD. So here goes:Have you tried: mbsid_interconnection_test_b.zip and lcd_interconnection_test_v1.zipMany of my problems with midi has come from stupid short cuts, not just on the core module. Also from other modules, and those pins you put on the SIL headers touching each other (mine are not in any kind of plastic wrapping, yet). So check also for shorts on other modules.I think that the fact that you keep getting unexpected upload request could indicate that MIOS was restarting all the time, perhaps because of some problem with power.Again, i dont really know what im doing. So i might be far offcheers/carsten Quote Link to comment Share on other sites More sharing options...
toneburst Posted October 10, 2006 Author Report Share Posted October 10, 2006 Hi Carsten,thanks for taking pity on me...I can't try either of the tests you mention because I can't upload anything (including MIOS itself) to my Core module. I just tried the LCD test one, and got the same 'unexpected upload request' error I've was getting before. Interestingly, my LCD has now started working again (in as much as it now shows a row of blocks, but now without the line through them). I did unplug and the replug its ribbon cable, so I guess that's probably got something to do with it.I was definitely getting some of the crimp pins connected to the SIL headers touching each other, when I first plugged in the Core. I but heatshrink around them, but have since removed them altogether, so the Core is now not connected to anything except the LCD.I don't know how to test the PSU really, except to use my multimeter to test the voltage across the 5V pins. It seems to be a rock-steady 5.19V, and doesn't seem to vary at all when I try to upload MIOS. Then again, it's a cheapo meter, so I don't know how much use it is in this case.I'm dubious about going through the MIDI debug tests again, because my soldering isn't that great, and the more I mess around soldering things to the PIC pins, the more likely I am to fry something... My solder-joints all look ok to me, so short of desldering and resoldering everything (and almost certainly trashing the baord in the process) I really don't know what else to try.This is very frustrating. Because I don't really know what I'm doing, when things go wrong I'm completely lost.Alexhttp://www.toneburst.net Quote Link to comment Share on other sites More sharing options...
carsten_the_dane Posted October 10, 2006 Report Share Posted October 10, 2006 This was one of the things i had problems with, that also caused strange midi messages. Wirering the mid inputs. The image is showing the core and the 2 midi - the midi inputs are laying on the ground to the right of the core, with the female connections down towards the ground. Then you just drag the wires over. Like shown ( :-\) kinda.Are you using a USB audio device.?/carstenPS: you could install linux ubuntu. Wouldnt that make it possible to do that loop test (or whatever its called) that you cant do on mac. Quote Link to comment Share on other sites More sharing options...
toneburst Posted October 10, 2006 Author Report Share Posted October 10, 2006 Ah, OK,I might give that a try. I'm actually using the pcb-mounted MIDI sockets that came with the SmashTV kit. I might have a couple of chassis-mount 5-pin DIN sockets kicking around somewhere.One thing I did try though- I removed the optocoupler and tried the upload again. Obviously it wasn't going to work, but I wanted to see if I'd get the same error-message.I did, soo..... it could be the optocoupler, methinks. My logic here may be faulty though...I have Windows XP installed on my MacBook Pro (they're Intel-based now anyway, so they can run XP natively), so I can use MIDI-Ox. It's just I can't work out how to carry out the test.Yep, I have a USB MIDI interface. Or rather, 2 USB MIDI interfaces. I also have one on my m-audio 1010 which is connected to a PCI slot on my G5. The only problem is I can't get MIOS studio to work on that computer. I may try to install the perl script mentioned here http://www.ucapps.de/howto_tools_hex2syx.html and try uploading a syx version of the MIOS OS from the desktop Mac. Now though, it's time for bed, I think.Think I'll put in another order for a replacement optopcoupler tomorrow, as I need to get some other bits and bobs (crimp-pin housings and other things) anyway.Thanks very much for the suggestions Carsten :-) .Alexhttp://www.toneburst.net Quote Link to comment Share on other sites More sharing options...
moogah Posted October 10, 2006 Report Share Posted October 10, 2006 Hmm. Those error messages are frustrating, but I'm no surprised by them. First I would take the time to not get frustrated by this, clear you head and work on some other things for awhile and then come back to this.. and start right from the beginning. I would want to know, 110% sure that the core is assembled correctly and the MIDI connections are correct. I've almost never had an issue with a bad IC myself, but if you have another optocoupler to swap with, go ahead. In MIOS studio are you using the "wait for upload request" option? It is possible you are just having trouble starting the upload in time. I use the wait feature and it's worked well for me. The strangeness with the LCD's isn't encouraging, but it wouldn't lead me to believe that you've caused any serious problems with the PIC. I've got 6 PIC's which I've really put through all sorts of hell. All of them still work. Also, there were more than a couple times where I had successfully uploaded MIOS and thought something had gone wrong because the LCD was all messed up. Each time it was a combination of not having enough juice going to the LCD (check that the output of the regulator is nice and stable with the LCD connected) and/or having the brightness/contrast setting in a bad position. I've found there to be a pretty narrow range of brightness/contrast that presents a readable screen. In your case this is something to think about next, I don't think you've gotten MIOS onto the PIC yet. Quote Link to comment Share on other sites More sharing options...
toneburst Posted October 11, 2006 Author Report Share Posted October 11, 2006 Hi moogah,thanks for the kind words.I think you're right about taking a break from this for a while. Good advice.I've tried using the 'wait for upload request' option in MIOS Studio.It's good to know the PICs are so tough.I've check the output of the regulator (the 'Optimised PSU' I made) with the Core board and LCD connected. As far as I can tell with my basic multimeter, it's producing a rock-steady 5.19V, even when I try and do an upload.The LCD looks fine in terms of readability- it's just that I can see a line of solid blocks across the top row of the display, and sometimes there's a clearly-visible line across the lit blocks; ie the 3rd row of 'pixels' from the top are no-longer lit. Sometimes the screen comes on like this, sometimes it doesn't, but the line appears later. I'm pretty sure I haven't managed to get MIOS onto the PIC also. I've been getting MIDI errors from the beginning.I'm getting a new Core/Sid set from Mike's MIDIShop, so maybe I'll just give up on this one and start again, as you suggest, from the very beginning. I'll go through all the MIDI debugging tests on the current board while I wait for the new ones to arrive though, and see if I can come up with something this time.Thanks again,Alexhttp://www.toneburst.net Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.