MB-6582 - MIDI IN Overrun Error

[weedoo]

Hi!

I’m done soldering all the base pcb. I tried connecting with midi to the computer. I see the request message when I power on the device. I don’t get the message each 2 seconds, only on power on. Is this normal ?

I tried uploading the mb6582 setup file via mios studio, it only start sending when I press start and power on the device. There is no way to send anything if the device is already running.

I get these errors:

Sending block #293 00F00000-00F000FF

Received Checksum: 30 - OK

Sending block #294 00F00100-00F001FF

Received error code 0B: MIDI IN Overrun Error

Sending block #294 00F00100-00F001FF

Error: Received unexpected Upload Request

Sending block #1 00003000-000030FF

Received error code 0B: MIDI IN Overrun Error

Sending block #1 00003000-000030FF

Error: Received unexpected Upload Request

Sending block #1 00003000-000030FF

Received error code 0B: MIDI IN Overrun Error

Sending block #1 00003000-000030FF

Error: Received unexpected Upload Request

Sending block #1 00003000-000030FF

Received error code 0B: MIDI IN Overrun Error

Sending block #1 00003000-000030FF

Error: Received unexpected Upload Request

Sending block #1 00003000-000030FF

Received error code 0B: MIDI IN Overrun Error

Sending block #1 00003000-000030FF

Error: Received unexpected Upload Request

Sending block #1 00003000-000030FF

Received error code 0B: MIDI IN Overrun Error

Sending block #1 00003000-000030FF

Error: Received unexpected Upload Request

Sending block #1 00003000-000030FF

Received error code 0B: MIDI IN Overrun Error

Error: Received unexpected Upload Request

Received error code 0B: MIDI IN Overrun Error

Error: Received unexpected Upload Request

Received error code 0B: MIDI IN Overrun Error

Error: Received unexpected Upload Request

Received error code 0B: MIDI IN Overrun Error

Error: Received unexpected Upload Request

Received error code 0B: MIDI IN Overrun Error

Error: Received unexpected Upload Request

Received error code 0B: MIDI IN Overrun Error

Error: Received unexpected Upload Request

Received error code 0B: MIDI IN Overrun Error

Error: Received unexpected Upload Request

Sending block #1 00003000-000030FF

Received error code 0B: MIDI IN Overrun Error

Sending block #1 00003000-000030FF

Error: Received unexpected Upload Request

Sending block #1 00003000-000030FF

Received error code 0B: MIDI IN Overrun Error

Aborting after 16 errors

Any ideas ?

[fussylizard]

I only get one request for an upload on mine, so I think that’s fine.

In MIOS Studio, I normally check the box for “Wait for upload request before starting upload” and use Smart Mode.  Then I turn off the MB, and when I turn it on the upload starts automatically.  (Make sure your device ID is set correctly, and set J11 to allow the target core to send MIDI out.)

Did you try the manual mode in the MIOS Hex File Upload screen?  You can set a delay to whatever you want and see if that fixes the issue.

Do you get these errors for every block or just at the end?  If so, try uploading a smaller file for testing since the MB-6582 app takes forever to upload.  Try the SID Testtone app instead, nice and small.

[nuke]

mmm…not exactly the same,but…when i had midi issues like “midi timeout” once the app was already in, i had a faulty optocouplers…sometimes working, sometimes not…maybe try to change the 6n13x if you got one spare…

[nILS]

Also, check if your MIDI interface is blacklisted and use the search function of the forum to look for “overrun error”.

[weedoo]

Hi,

It’s getting better, but still, I would need some help Any idea anyone ?

[nuke]

cables checked?..sometimes it´s that easy…midi interface?..(…got a different one to check?)…optocoupler broken? (as i mentioned before…i had issues too before i changed the 6n138s…

…what exactly did u do that made it work “better”?

[fussylizard]

Does it happen on all blocks of the upload, or only at the very end?  I notice when uploading the MB-6582 app that the last few blocks are very slow.

Does it happen on all apps (e.g. SID testtone app?) or just on the MB-SID app?

Does it still happen if you set a higher delay, say 1000ms between blocks?

[weedoo]

Hi,

This error only happens at the end. I don’t know how many block there is, but they’re all ok until 294. My midi interface if brand new, I use cakewalk um-1g by roland. I will try 1000ms and see if it works better. I will check with the sid testtone too. I’ll get back to you when test is done.

Thanks!

[lylehaze]

I have some experience with the UM-1 interfaces.

Since we might be dealing with a driver problem, remember there are TWO

different drivers you can use. The interface has an “Advanced Driver”

switch on the side. When it is ON, you’ll use the drivers supplied with the

interface, when it is OFF, you will use the standard OS drivers for class-

compatible interfaces.

Please note that the interface identifies itself as soon as it’s connected, so

if you want to change the switch setting, you should probably unplug the

USB cable first.

I had the pleasure of writing the “class compatible” drivers for another OS.

Once the drivers are right, the UM-1 will work correctly with the "Advanced

Driver" switch off.

Have Fun,

LyleHaze

[fussylizard]

Hi,

This error only happens at the end. I don’t know how many block there is, but they’re all ok until 294. My midi interface if brand new, I use cakewalk um-1g by roland. I will try 1000ms and see if it works better. I will check with the sid testtone too. I’ll get back to you when test is done.

Thanks!

Hmmm. For whatever reason those last few blocks are very slow. 1000 ms may not be enough, but try it. 2000 ms should be plenty based on my experience bit YMMV.

[weedoo]

OK I tried using advanced driver to off but this doesn’t seem to work, in fact, I can’t get the mb6582 request at all when I boot the device.  I tried using 700ms, 1000ms, trying 2000ms right now. Hope this works.

[weedoo]

I tried 2000ms with and without advanced driver and I still get the same error. What is strange, the 1k testtone was uploaded without problem.

[T.K]

It seems that your MIDI interface sends some additional MIDI bytes while the EEPROM is programmed. Since interrupts have to be disabled during this time, it could cause a MIDI buffer overrun.

I never saw such a strange interface behaviour before, but it’s the only explanation I have for such an error message.

Possible workaround: you could split the .hex file into multiple pieces and download them separately. Each file contains an EEPROM block.

I guess that these files would work fine for the latest MBSID release (this is quick copy&paste, I haven’t tried this…)

eeprom_1.hex

:0200000400F00A
:100000004C656164205061746368202020202020AA
:10001000000000000000000000008000FF000080E1
:1000200000FF00008000FF00008000FF0000800053
:10003000FF00008000FF50008000FF00008000FFF4
:1000400000800080008000800080008000800080B0
:1000500000007F00100002000000100002000000FD
:10006000000400F00008000040800200001F0500AE
:10007000001400F00008000040800200001F05008E
:10008000001400F00008000040800200001F05007E
:10009000000400F00008000040800200001F05007E
:1000A000001400F00008000040800200001F05005E
:1000B000001400F00008000040800200001F05004E
:1000C00001800000000180000000018000000001AC
:1000D000800000000180000000018000000000009E
:1000E00000C00030FF0000FF304020000080808012
:1000F00000400050FF0000FF501030000080808062
:00000001FF
[/code]


eeprom_2.hex
[code]  
:0200000400F00A  
10010000010003C000000000020003C00000000066  
:10011000030003C000000000040003C00000000052  
:10012000050003C000000000060003C0000000003E  
:10013000070003C000000000080003C0000000002A  
:10014000FF000F3F0300000000000000000000005F  
:10015000000000000000000000000000000000009F  
:10016000F00000000000000000000000CB00001FB5  
:1001700080CB00203FA0CB00405FC0CB00607FE081  
:10018000404040404040404040404040404040406F  
:10019000404040404040404040404040404040405F  
:1001A000404040404040404040404040404040404F  
:1001B000404040404040404040404040404040403F  
:1001C000404040404040404040404040404040402F  
:1001D000404040404040404040404040404040401F  
:1001E000404040404040404040404040404040400F  
:1001F00040404040404040404040404040404040FF  
:00000001FF  

eeprom_3.hex

:0200000400F00A
:1002000000000200027800000000006000000060B2
:1002100000007F400000000010007F400000000050
:1002200010007F400000000010007F400000000030
:1002300010007F400000000010007F400000000020
:100240000000000002780000000000600000006074
:1002500001007F400000000010007F40000000000F
:1002600010007F400000000010007F4000000000F0
:1002700010007F400000000010007F4000000000E0
:100280000000000002780000000000600000006034
:1002900002007F400000000010007F4000000000CE
:1002A00010007F400000000010007F4000000000B0
:1002B00010007F400000000010007F4000000000A0
:1002C00000000000027800000000006000000060F4
:1002D00003007F400000000010007F40000000008D
:1002E00010007F400000000010007F400000000070
:1002F00010007F400000000010007F400000000060
:00000001FF
[/code]



eeprom_4.hex
[code]  
:0200000400F00A  
:020300000100FA  
:00000001FF  

In MIOS Studio, please enable Smart mode again!

Best Regards, Thorsten.

[weedoo]

YEA ! Thanks to Cerebral Infect!!! (http://www.midibox.org/forum/index.php?topic=13703.0) I was able to upload SID R31 !!! For some reason, removing all banksticks, uploading WITHOUT “Wait for upload request” in Smart Mode worked !