Can't upload MIOS

Testing/Troubleshooting
1

So, I flashed/burned the pic and for the last couple of days I can’t find a way to solve my problem.

I am receiving Upload request but PIC won’t accept data/send back checksum. I don’t have the scope

to check stability of power imput and I have read most of MIOS upload problems(and tired some of the

solutions). I also erased the pic, check it for empty space and flashed once more.

[table]

[tr][td]

Loader:

[/td][td]bootloader_v1_2_pic18f452.hex[/td][/tr]

[tr][td]

MIOS:

[/td][td]mios_v1_9_pic18f452.hex[/td][/tr]

[tr][td]

MIOS Studio:

[/td][td]MIOSStudio_beta4_4.jar[/td][/tr]

[tr][td]

Connection:

[/td][td]J11 <-custom built cable-> Gameport [sB Live!, kX driver v3537][/td][/tr]

[tr][td]

PSU:

[/td][td]C128D Power unit, connected to outputs +12 & 0[/td][/tr]

[tr][td]

J2 Voltage:

[/td][td]~5.11V[/td][/tr]

[tr][td]

LCD 4x20 CMC420L01:

(www.cct.com.my)

[/td][td]Backlit, 1st & 3rd line FILLED WITH BLOCKS, 2nd & 4th EMPTY[/td][/tr]

[tr][td]

Cable loopack test:

[/td][td]Passed[/td][/tr]

[tr][td]

PCB loopack test:

[/td][td]Passed (removed pic, pins 25 & 26 shorted)[/td][/tr]

[tr][td]

LED on pin 26 test:

[/td][td]Passed (with pic in)[/td][/tr]

[/table]

2

New MIOS 7_2 Report:

Starting upload of mios_v1_9_pic18f452.hex
Hex file contains code in MIOS range, forcing reboot!
Received Upload Request
Sending block 00000400-000004FF
Error: Received unexpected Upload Request
Sending block 00000500-000005FF
Error: Received unexpected Upload Request
Sending block 00000500-000005FF
Error: Received unexpected Upload Request
Aborting after 3 errors
3

What is the output of the MIDI In window?

Best Regards, Thorsten.

4

Upload request after upload request…

...
timestamp 61266000 us: Sysex message: F0 00 00 7E 40 00 01 F7
timestamp 63158000 us: Sysex message: F0 00 00 7E 40 00 01 F7
timestamp 65051000 us: Sysex message: F0 00 00 7E 40 00 01 F7
timestamp 66943000 us: Sysex message: F0 00 00 7E 40 00 01 F7
timestamp 68835000 us: Sysex message: F0 00 00 7E 40 00 01 F7
timestamp 70728000 us: Sysex message: F0 00 00 7E 40 00 01 F7
timestamp 72620000 us: Sysex message: F0 00 00 7E 40 00 01 F7
timestamp 74512000 us: Sysex message: F0 00 00 7E 40 00 01 F7
timestamp 76405000 us: Sysex message: F0 00 00 7E 40 00 01 F7
timestamp 78297000 us: Sysex message: F0 00 00 7E 40 00 01 F7
timestamp 80189000 us: Sysex message: F0 00 00 7E 40 00 01 F7
timestamp 82082000 us: Sysex message: F0 00 00 7E 40 00 01 F7
timestamp 83974000 us: Sysex message: F0 00 00 7E 40 00 01 F7
timestamp 85866000 us: Sysex message: F0 00 00 7E 40 00 01 F7
timestamp 87759000 us: Sysex message: F0 00 00 7E 40 00 01 F7
timestamp 89651000 us: Sysex message: F0 00 00 7E 40 00 01 F7
...

A little idea TK, is it possible for you to put some different message on startup that would signify powerup[the idea is to easily detect reset]? Pseudo

<startup>
<upload request>
<upload request>
<upload request>
...

Since I’ve read at lest 3 posts with Psu problems and rebooting. What do you say?

5

The upload request already notifies a reset. If multiple requests are sent, then due to a watchdog timer reset - this reset happens on a timeout (e.g. no SysEx code received, or MIOS not uploaded). It doesn’t make much sense to add more variations here, it wouldn’t give you any useful information, it would only increase the complexity.

So far I know, the “Received unexpected Upload Request” message can only happen in two cases:

  1. the core doesn’t receive a SysEx block with command 02 (Write), therefore a watchdog reset will happen

  2. you are sending the code with a different device ID number - your core has device ID 00 (therefore I asked for the MIDI In dump, it shows me the number), is the same number selected in the upload window?

I don’t know other cases for such a behaviour

Best Regards, Thorsten.

6

Well, that’s why I came here for ansvers, I too don’t get it.

[i didn’t know it reboots if doesn’t get a upload start, sorry]

How about this, the logic voltage levels are offset and therefore

pic doesnt “get it”?

I’ve forgot to menition that there is nothing in the OCoupler position

and that instead of R6 (1k2) was put … CRAP!! 100R

Let me get back to you.

7

You have replaced the 1.2k by a 100 Ohm resistor? This cannot work, and this is propably the reason for the failure… if the MIDIbox is directly connected to a gameport, you can also left out 1.2k, or (better) you can replace it by a 10k or higher in order to avoid that the MIDIbox will receive random (and invalid) MIDI events when it is not connected to your PC

Best Regards, Thorsten.

8

Done it! Connected 80k & 37k in paralel then all that to one more 80k to achieve a resistance of 105k, MIOS UPLOADED

So simple…and I’m testing for problems tru the whole last week.