I can't Upload the MIOS, HELP PLEASE!!

banneduser · August 24, 2004, 7:56pm

Hi, please help me,..I have already build the core and the JDB(on protoboard). I burn the PIC with the Bootstrap Loader and it seems to by OK, the IC-prog, says that was succesfuly verified.

The I’m trying to upload the MIOS, but nothing happend.

This is what i get from the MIOS-OX

I have succesfully received the F0 00 00 7E 40 00 01 F7 statement, in the input and then in the output

When it try to upload the MIOS I can see the code in the Output Monitor with some yellow "F0 00 00 7E 40 00 01 F7 " statements inbetween.

I tryied with the MIDI Troublesooting guide, this are my results.

Check the resistor values at the MIDI In Port: R11=220 Ohm (resistor code: red-red-brown), R6=1.2kOhm (brown-red-red), R5=5.6kOhm (Green-Blue-Red). Â Â [glow=red,2,300]PASSED OK[/glow]
solder two cables to the bottom side of the core module like shown in mbhp_core_midiin_debug.gif. The LED should lit (take the polarity of the LED into account, the short leg is the cathode and has to be connected via a resistor to Vss). So long as single MIDI events are received, you won’t notice a difference, but with a continuous SysEx stream the LED should begin to flicker.

The led never lit. I try to send the mios with the led in this position to send more midi events, but the let did not flick.

[glow=red,2,300]Not Passed[/glow]

if the LED doesn’t lit, connect the anode to the optocoupler (Pin IC2:6). If it still doesn’t lit, connect the anode with the +5V rail of the optocoupler (Pin IC2:8)

I conect the anode to the PIn IC2:6 and it doesn’t lit. [glow=red,2,300]Not Passed[/glow]

I conect the anode to the PIn IC2:8 and it does lit. [glow=red,2,300]Passed OK[/glow]

If this doesn’t help you to detect the error, continue with the next step - see mbhp_core_midiin_debug2.gif - in this configuration the LED should only lit when MIDI data is received. Than more MIDI events are received a time, than brigther the LED. If the LED doesn’t lit, check the polarity of the protection diode D1 before the optocoupler (again…). Also check the polarity of the MIDI cable (again…).

[glow=red,2,300]Passed OK[/glow]

A second standalone test for the optocoupler, this time the optocoupler isn’t plugged in the core module: mbhp_core_opto_test.gif

[glow=red,2,300]Passed OK[/glow]

6)final check to ensure that all 4 MIDI ports are working: put the PIC out of the socket and loopback the MIDI IO ports at the Rx/Tx pins like demonstrated in mbhp_core_extract_io_loopback.gif. Send any SysEx dump by using the “Send/Receive SysEx” function of MIDI-Ox. The number of sent bytes must match with the number of received bytes

[glow=red,2,300]Passed OK[/glow]

PLEASE HELP ME; Thanks

kapser · August 24, 2004, 11:46pm

Well I have the same problem. I passed check number 6. I get a response from the device every 2 seconds ( SYSX: F0 00 00 7E 40 00 01 F7 )

If I upload the mios_v1_7.syx with midiox ( i tried low level output buffer from 64 bytes ) and a delay of 1000 ms. I get a response on the input. Everytime this string ( F0 00 00 7E 40 00 01 F0 ) a lot of times ( seems like a reaction of the pic on the incoming data ).

After my “upload” is finished, I keep getting the 2 second message’s.

I’ve read every item on your site and tried different thing, but nothing seems to work.

goyousalukis · August 25, 2004, 9:04am

Ok, if you get the response every two seconds, that means you have just the bootloader. When you successfully send MIOS, you will get a bunch of replies like this (i just did it)

TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT Â  Â  Â  Â  Â  Â  Â  
 0000A31B Â  9 Â -- Â  Â  F0 Â Buffer: Â  Â 10 Bytes Â  System Exclusive Â  Â  Â 
 SYSX: F0 00 00 7E 40 00 0E 04 0E F7
 0000A646 Â  9 Â -- Â  Â  F0 Â Buffer: Â  Â 10 Bytes Â  System Exclusive Â  Â  Â 
 SYSX: F0 00 00 7E 40 00 0E 04 34 F7
 0000A971 Â  9 Â -- Â  Â  F0 Â Buffer: Â  Â 10 Bytes Â  System Exclusive Â  Â  Â 
 SYSX: F0 00 00 7E 40 00 0E 04 3A F7
 0000AC9E Â  9 Â -- Â  Â  F0 Â Buffer: Â  Â 10 Bytes Â  System Exclusive Â  Â  Â 
 SYSX: F0 00 00 7E 40 00 0E 04 3F F7
 0000AFC8 Â  9 Â -- Â  Â  F0 Â Buffer: Â  Â 10 Bytes Â  System Exclusive Â  Â  Â 
 SYSX: F0 00 00 7E 40 00 0E 04 5D F7
 0000B2F4 Â  9 Â -- Â  Â  F0 Â Buffer: Â  Â 10 Bytes Â  System Exclusive Â  Â  Â 
 SYSX: F0 00 00 7E 40 00 0E 04 20 F7
 0000B629 Â  9 Â -- Â  Â  F0 Â Buffer: Â  Â 10 Bytes Â  System Exclusive Â  Â  Â 
 SYSX: F0 00 00 7E 40 00 0E 04 42 F7
 0000B956 Â  9 Â -- Â  Â  F0 Â Buffer: Â  Â 10 Bytes Â  System Exclusive Â  Â  Â 
 SYSX: F0 00 00 7E 40 00 0E 04 28 F7
 0000BC7F Â  9 Â -- Â  Â  F0 Â Buffer: Â  Â 10 Bytes Â  System Exclusive Â  Â  Â 
 SYSX: F0 00 00 7E 40 00 0E 04 59 F7
 0000BFAA Â  9 Â -- Â  Â  F0 Â Buffer: Â  Â 10 Bytes Â  System Exclusive Â  Â  Â 
 SYSX: F0 00 00 7E 40 00 0E 04 0C F7
 0000C2D6 Â  9 Â -- Â  Â  F0 Â Buffer: Â  Â 10 Bytes Â  System Exclusive Â  Â  Â 
 SYSX: F0 00 00 7E 40 00 0E 04 7C F7
 0000C601 Â  9 Â -- Â  Â  F0 Â Buffer: Â  Â 10 Bytes Â  System Exclusive Â  Â  Â 
 SYSX: F0 00 00 7E 40 00 0E 04 10 F7
 0000CA54 Â  9 Â -- Â  Â  F0 Â Buffer: Â  Â  9 Bytes Â  System Exclusive Â  Â  Â 
 SYSX: F0 00 00 7E 40 00 0F 53 F7
 0000D2DA Â  9 Â -- Â  Â  F0 Â Buffer: Â  Â  8 Bytes Â  System Exclusive Â  Â  Â 
 SYSX: F0 00 00 7E 40 00 01 F7

You’ll notice that the byte before F7 changes. This is the checksum. If when you send the sysex file to the pic, you get no replies back, there is a problem with your midi input. I know this sounds dumb, but I did this on my first midibox attempt: Do you have the pins right on the midi in? Even if you are sure they are right, try reversing them just in case. Also, do you have the diode in the correct orientation? Double check that. Sorry if you have already tried these, but I am just throwing out some ideas.

Justin

*one more thing - in midiox, make sure you don’t have any ports mapped to eachother. Check this by clicking on the icon that looks like a roadsign with a 66 on it. There should be no lines between midi ports. If your midi-in port is mapped to your midi-out port, it will not work!

kapser · August 26, 2004, 4:29pm

Well, now I’ve connected Tx to Rx without the microprocessor. If I send a lot of bytes ( 1024/512/64) at the same time, I get other messages at the input ( like pitchbend ).

Now I send bytes with this configuration :

This are the first hex numbers I’ve send :

F0 00 00 7E 40 00 02 00 00 01 00 40 3B 62 3F 04 03 5E 13

But I receive this in the sysex scratch pad:

F0 00 00 7E 40 00 02 00 00 00 00 00 3B 62 3E 00 03 1C 02 70

It goes wrong after 9 numbers. I suppose that I should receive the same value’s as I’m sending.

raphael · August 26, 2004, 10:46pm

Hi,

I suppose that I should receive the same value’s as I’m sending.

ThatÂ´s right.

So perhaps your midi interface is buggy. Are you using a onboard soundcard? I had several problems with some nVidia nForce onboard interfaces.

Now with the interfaces of my Marian Marc X Soundcard everything is OK.

So try another MIDI interface.

Raphael

kapser · August 26, 2004, 11:31pm

Well, I use a midiman midisport 2x2. Thought it was a pretty realiable device, but I could try another one of course.

kapser · August 27, 2004, 10:27pm

Well, I did ALL the debugging ( optocoupler test etc. ), but nothing seems wrong with the hardware.

If I receive sysex I get a feedback string everytime a string of 1024 bytes is send. Everytime this string :

SYSX: F0 00 00 7E 40 00 01 F0

What does this mean ??? Because it’s different then F7, but I couldn’t find it in the error codes table.

If the sysex “uploading” is done, I’ll get the 2 second message ( F0 00 00 7E 40 00 01 F7 ) Again.

kapser · August 30, 2004, 7:32pm

Well, I also tried to upload mios with another interface ( emagic unitor8 ) and did the last send/receive test. Again the bytes are changed

Is there a way to upload mios without midi ?

goyousalukis · August 31, 2004, 5:33am

Just to check, you are using the sysex configuration shown:

kapser · August 31, 2004, 9:45pm

Yep, and others to try if that might work.

banneduser · September 1, 2004, 11:02pm

I have exactly the same problem, except all my tests came out fine, LED lights in all cases, string is returned exactly the same, tried both midisport 2x2 and audiophile delta midi interface.

In other words, bump, me too.

T.K · September 2, 2004, 11:54pm

Hi Nacho,

When it try to upload the MIOS I can see the code in the Output Monitor with some yellow "F0 00 00 7E 40 00 01 F7 " statements inbetween.

this means that you forgot to disable the internal MIDI thru function of MIDI-ox which forwards incoming data to the output(s). This function disturbs the communication with the core and should therefore be deactivated:

once you did this, deselect all MIDI In/Out ports and select them again (easiest solution), or modify your port mapping directly (expert solution)

More details can be found at the Bootstrap Loader page:

http://www.ucapps.de/mios_bootstrap.html

Best Regards, Thorsten.

P.S.: a Java based uploading tool which replaces MIDI-ox and is easier to use (since it doesn’t provide so much options…) will be published in the next days

banneduser · September 4, 2004, 8:12am

Is the MBHP_USB - Port an example?

IÂ´m the next one.

But iÂ´v never seen the backlight.

Maybe an XP problem?

T.K · September 4, 2004, 1:04pm

No, there is no problem with XP.

Just follow the MIDI troubleshooting guide step by step — all issues from the past are documented there, all users were able to get the upload running based on this guide, and I don’t think that there is any new, unknown problem.

http://www.ucapps.de/howto_debug_midi.html

Best Regards, Thorsten.

banneduser · September 7, 2004, 7:34pm

Just to let you all know, my problem was with the optocoupler. Got myself a new optocoupler today, and the OS is now uploaded!

banneduser · September 10, 2004, 4:26am

6)final check to ensure that all 4 MIDI ports are working: put the PIC out of the socket and loopback the MIDI IO ports at the Rx/Tx pins like demonstrated in mbhp_core_extract_io_loopback.gif. Send any SysEx dump by using the “Send/Receive SysEx” function of MIDI-Ox. The number of sent bytes must match with the number of received bytes

[glow=red,2,300]Passed OK[/glow]

You are, right Thorsten, The test 6 its not passing, I have received more bytes that the sent bytes…

Some tips’???

kapser · September 14, 2004, 8:28pm

My problem is also fixed, it was a bad solder connection from one of the resistors to the optocoupler.