Cerebral Infect Posted June 25, 2009 Report Share Posted June 25, 2009 Hi,I've pretty finished the Mainboard. I've tested the Sid with the testone program. I was able to upload the program to all four core. Now I am trying to upload the MB-6582 hex file and I have this following error :Sending block #1 00003000-000030FFError: Received unexpected Upload RequestReceived error code 0B: MIDI IN Overrun ErrorDoes anybody encountered something similar ?Does the bankstick chip being installed changes something ?Thanks ! Quote Link to comment Share on other sites More sharing options...
Wilba Posted June 25, 2009 Report Share Posted June 25, 2009 Occasionally I've had trouble uploading a new app to a PIC if the app that's already on there is a tight-looped test app. I don't remember if I got this specific problem.Try uploading it the same way you would upload MIOS, i.e. with "Wait for upload request" checked.First power off the MB-6582.Check "Wait for upload request".Press the start button to upload.Wait two seconds before powering on the MB-6582.The MB-6582 should then send out one upload request, which should trigger the upload of the application.If you get the same error, repeat a few times to confirm it happens every time.If that doesn't help, I'll think up some other things to try. Quote Link to comment Share on other sites More sharing options...
Cerebral Infect Posted June 25, 2009 Author Report Share Posted June 25, 2009 Hi Wilba,What you proposed was exactly what I was doing. So I used shorter midi cables, unplugged the power supply for a while. Repluged everything in. Powered On and I was able to send the hex to the core BUT At packet 293 (or 294) an error message appeared "Received error code 0B: MIDI IN Overrun Error" and the hex file process started again. When I pressed stop, the Midibox LCD showed that the unit was formatting the memory banks.So I`ve uploaded the Hex file to the other cores, all 3 with the same error messages at packet send 294. I've then uploaded the SID preset patches with no problems to bank A.The new problem is that when the SID unit starts, it start at midi channel 16. I can switch through the programs and bank using midi messafe from my midi controllers. But it doens`t respond to midi notes. I hear the 4-5 notes when the Midibox boots, but after, I cannot make sound.Is no making sound related to the "upload error at packet 293-294" or the unit is stuck a channel 16 and the core respond only to channel 1 to 4 ? Quote Link to comment Share on other sites More sharing options...
Wilba Posted June 26, 2009 Report Share Posted June 26, 2009 Any error during upload is going to leave the PIC without the full application, so you can't expect things to work properly until you get it fully uploaded without errors.I don't know why it would fail at a specific packet every time. That's just weird.I would say now, perhaps to try removing the banksticks, uploading MIOS again (1.9f only!), and then the MB-SID app. Do not install banksticks again until you have the MB-SID app uploaded without errors. You can make sure the app is receiving notes and playing sounds BEFORE you install banksticks and (perhaps) debug another issue. Quote Link to comment Share on other sites More sharing options...
Cerebral Infect Posted June 27, 2009 Author Report Share Posted June 27, 2009 Hi,I removed the bank stick. Uploaded the Mios 1.9 for PIC18F4685. No problems.Then I tried to Upload the MB6582 Hexfile and I have the same error message on all cores at #294. It is just like yesterday. What is supposebly suppose to happen at 294 ? It stops ? I`ll tried tonight with a different midi interface. Thanks in advanceSending block #294 00F00100-00F001FFReceived error code 0B: MIDI IN Overrun ErrorSending block #294 00F00100-00F001FFError: Received unexpected Upload RequestSending block #1 00003000-000030FFReceived error code 0B: MIDI IN Overrun ErrorSending block #1 00003000-000030FFError: Received unexpected Upload RequestSending block #1 00003000-000030FFReceived error code 0B: MIDI IN Overrun ErrorSending block #1 00003000-000030FFError: Received unexpected Upload RequestSending block #1 00003000-000030FFReceived error code 0B: MIDI IN Overrun ErrorSending block #1 00003000-000030FFError: Received unexpected Upload RequestSending block #1 00003000-000030FFReceived error code 0B: MIDI IN Overrun ErrorSending block #1 00003000-000030FFError: Received unexpected Upload RequestReceived error code 0B: MIDI IN Overrun ErrorSending block #1 00003000-000030FFError: Received unexpected Upload RequestSending block #1 00003000-000030FFReceived error code 0B: MIDI IN Overrun ErrorError: Received unexpected Upload RequestSending block #1 00003000-000030FFReceived error code 0B: MIDI IN Overrun ErrorSending block #1 00003000-000030FFError: Received unexpected Upload RequestSending block #1 00003000-000030FFReceived error code 0B: MIDI IN Overrun ErrorSending block #1 00003000-000030FFError: Received unexpected Upload RequestSending block #1 00003000-000030FFReceived error code 0B: MIDI IN Overrun ErrorAborting after 16 errors Quote Link to comment Share on other sites More sharing options...
Cerebral Infect Posted June 28, 2009 Author Report Share Posted June 28, 2009 Okay,I made some progress. I've removed the bankstick. Made bunch of uploads to the Core.I was able to upload MIOS with "Wait for upload..." in manual mode.Then I was able to upload the SID OS to the core in manual mode, but without the "Wait for upload..."Channel 1 to 4 are working. I can play notes with the MIOS midi keyboard.I then put the bankstick on the unit. It is when the unit doesn`t work anymore. It boots at channel 16, I can flip thourgh the presets, but does make any sounds when playing the keyboard. On any channel.So I think it goes down the banksticks. Any Ideas ? Quote Link to comment Share on other sites More sharing options...
Wilba Posted June 28, 2009 Report Share Posted June 28, 2009 What exactly do you mean by "manual mode"?If you mean "Don't use feedback from core" then you really should be using feedback from Core... this validates that each packet of the upload was received without errors, and if you can't validate that there is uncorrupted firmware on the PIC, any other problem might be caused by corrupted firmware on the PIC.This is probably not the case here, but you should make sure you can upload with feedback from the Core before anything else - any failure to get that working is a completely different bug (PC MIDI hardware/drivers, bad MIDI In/Out on the PCB, etc.)It is possible that some garbage data got stored on the bankstick, and so putting it in the PCB is making the MB-SID get confused.Try this:Take out all banksticks.Upload the latest version of MB-SID app (RC 31) using "Feedback from Core"Test if everything stills works as before.Put one bankstick in socket 8 (so it gets formatted as the Ensemble bankstick)... then put it in socket 1 (so it gets formatted as a Patch bankstick).Test if everything still works (scroll patches, play notes).Repeat for the other banksticks (put in socket 8, then in socket 2,3,4,5,6,7)Note: sockets numbers are arranged like so:1 2 3 45 6 7 8(In hindsight, I probably should have put numbers on them, but I didn't anticipate people needing to move them around after construction.)The GOOD NEWS is, you're getting sound out of all your SIDs, and I assume your control surface is also working! So there's a lot of possible things that could go wrong that DIDN'T. Congratulations! :) Quote Link to comment Share on other sites More sharing options...
Cerebral Infect Posted June 29, 2009 Author Report Share Posted June 29, 2009 Success !I was able to load Sid R31 OS to the core using the core feedback option on BUT with "Wait for upload request" off. Whenever I putting the "Wait for upload" on, there was always an error a Packet 294.I then reformated the bankstick with the ensemble socket. The problematic stick was the original "ensemble" bankstick. So I've put it in socket A, reformatted it and placed the other in and everything works. Loaded the patchs and tadam, I could play the patch.Thanks Wilba for the help. Thanks Thanks Thanks, I was trying stuff but not really logically.As for infos to the others. My midi controller is an Edirol PCR-M1 and once I understood the twist around uploading the midibox OS, everything went well. On the other Hand, the Novation Remote SL was not good at all. Lots of missed packet send. Anybody else had bad experience with the Novation Remote SL ? Quote Link to comment Share on other sites More sharing options...
Wilba Posted June 29, 2009 Report Share Posted June 29, 2009 It could be the driver playing up with the Java based MIOS Studio. I seem to be lucky, my Delta 1010LT works fine.Good to hear you got it all sorted.POIDH :) Quote Link to comment Share on other sites More sharing options...
Cerebral Infect Posted July 1, 2009 Author Report Share Posted July 1, 2009 Pic to proove it did happen !Have a good cold one too !100_1255.JPG100_1255.JPG Quote Link to comment Share on other sites More sharing options...
Wilba Posted July 1, 2009 Report Share Posted July 1, 2009 Oooh! Canadian beer! Thanks! Quote Link to comment Share on other sites More sharing options...
weedoo Posted July 6, 2009 Report Share Posted July 6, 2009 Thanks to Wilba and Cerebral Infect, I had the same issue ! -> http://www.midibox.org/forum/index.php/topic,13660.0.html 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.