Pic not sending upload Request!

[Digispunk]

Hi There everyone,

after many months of reading and researching, i took the plunge and built a core and sid board, the first attempts were rubblish, too much bad soldering, so i started a second batch with some excelent help.

Now the Core and Sid boards are built, and they all check out with the electricity readings at the various points, these have been checked by a skilled electronics friend and he assures me they are all connecting and reading fine as per the guildlines.

I connected the core's midi ports to my computer to upload the Mios software into the Pic - (Bootstrap loader V1_1b from Smash Tv)  and the problem is i dont get any requests or sign of life from the pic, when i run Mios Studio and open the Midi monitors there is nothing.

The midi interface has been checked in/out signals sent / recieved with synthesisers - everything working

The core board has been checked - all correct readings with multimeter

My electronics friend asks me to check with you about the Octocoupler calibration - is this necessary to get the message through?

Could it be possible that my Pic is dead?

Do i need to upload a new bootstrap?

This project is a really cool thing and i want to thank Thorsten, Smash and the whole community for making it possible, and i look forward to getting the bleeps out of the SId.

 

[stryd_one]

You haven't followed the correct procedure. The bootloader cannot be loaded by MIDI, it has to be burned onto the PIC. After this, you can use MIDI via the bootloader to upload MIOS, and then you can upload your application. Please check the WIKI or this forum for instructions.

[Digispunk]

Hi Stryd,

thanks for the speedy reply,

maybe my writing syntax mis-represented what i meant,

so what i mean is -

I have a Pre-Burned Pic from Smash with the Bootstrap V 1_1b installed into the core

its not sending a request in Mios studio - i do have Mios configured correctly

please correct me if im mistaken - but if a Core has a Pre-Burned Pic with the Bootloader installed, it should send a request message when its connected to Mios Studio and its Power Switched on? right or wrong?

[stryd_one]

Sorry mate I missed that post somehow, I think the forum glitched...

That's all correct then... What does the LCD do? Are you sure that the MIDI Input on your PC and the cable are both OK (particularly with SysEx messages)?

[Digispunk]

The LCD was lighting up  - but there was no message or characters displayed,l

I have tested the midi connections (in and out) by attatching a synth to it and sending and recieving midi notes and midi cc's in and out of Ableton, i will also check the sysex send and receive for safety.

Can you confirm whether i dont or do need to calibrate the optocoupler for the MIDI on the core? - my electronics mate asked me to check this out with you.

[illogik]

Can you confirm whether i dont or do need to calibrate the optocoupler for the MIDI on the core? - my electronics mate asked me to check this out with you.

no; the only calibration that can be done at the core are LCD brightness/contrast

The LCD was lighting up  - but there was no message or characters displayed,l

and if you turn up the contrast, youll see a bar of black blocks, right?

please correct me if im mistaken - but if a Core has a Pre-Burned Pic with the Bootloader installed, it should send a request message when its connected to Mios Studio and its Power Switched on? right or wrong?

yes, but only if;

* you have your midi device routing properly set up in MIOSStudio

* and the midi part of your core works; do the MIDI-troubleshooting guide step by step to insure your core is working

good luck, marcel

[stryd_one]

edit: Beaten :)

[Digispunk]

thanks Illogik, and all who have contributed to the knowledge

* and the midi part of your core works; do the MIDI-troubleshooting guide step by step to insure your core is working - yes - just no request from the pic - at this point i am beginning to presume that it has not been burned properly or has been damaged in some way, i am going to try to locate another pic and retest - hopefully this will solve the problem

* you have your midi device routing properly set up in MIOSStudio - yes i have this done - i am competent with Midi including sysex

if there is no need to calibrate the optocouplers - will turning the (optocoupler) pots have any effect on the performance or the MIDI ports?

LCD - yes turning up the brightness makes the upper row of bocks turn black - i am using the 40x2 LCD from Voit.Nl

cheers - i am going to check all this out tomorrow and report back - hopefully with some good news! :)

[Digispunk]

well - im pleased to say that some progress has been made, but we aint all the way home yet,

the problem was the wires between the midi ports and the core board (i am using surface mounted midi sockets - so i had to use wires to extend the length),

- so once corrected - i bootup MIOS studio, get the hex file ready - \MIDIBOX\mios_update_v1_9\pic18f452\midi\update_without_installed_mios.hex

this was the one recomended to go for, since i have Smash Pic with the bootstrap already burned in the pic (v1.1b)

now upon switching on the core, MIOS gets the request signal and begins to load the software, everything seems to be going fine -

MIOS reports that 'Upload process complete' then instead of the checksum i get an endless string of sysex requests as pictured below

the software doesnt seem to be behaving as planned - any ideas? ???

my troubleshooting logic goes like this -

MIOS receives request signal from PIC/CORE = PIC functional / CORE functional / CORE MIDI OUT PORT functional / PC MIDI PORT functional

MIOS is sending the software, MIOS MIDI 'in' PORT monitor shows feedback from CORE (but no checksum) - IF MIDI conection from PC to CORE MIDI 'in' is physically disconected, then PIC sends new upload request and MIOS MIDI 'in' PORT monitor stops displaying the 'recieved data' = CORE MIDI IN PORT functional

so

PIC = Functional

CORE MIDI IN/OUT Functional

PC MIDI in/OUT Functional

Cables OK

MIOS OK

anything else im missing? hints?

[TK.]

Could you please try the latest release of MIOS Studio?

-> http://www.midibox.org/forum/index.php?topic=6810.0

Best Regards, Thorsten.

[Digispunk]

OK - so with the latest MIOS STUDIO running, i set up to load the hex file - no luck - i get these messages

with the core powered down, and MIOS awaiting request i get this message

'Hex file contains code in MIOS range, forcing reboot!'

when i switch the core power on, it begins to upload, but the core returns error message and after 3 attempts MIOS Stuido aborts the upload with this message

'Aborting after 3 errors'

i search the forum for references to these errors, but not found anything

i couldnt find anything on this in the threads regarding the latest release of MIOS studio,

??? ??? ??? ??? ???

[stryd_one]

I think you need bootstrap loader v1.2 for MIOS 1.9 no?

[Digispunk]

yes - thats what TK says in the readme.txt -

quote -

A) you got a preburned PIC18F452 from SmashTV or Mike with the old

  Bootloader v1.1b, and haven't installed MIOS yet.

In this case, upload

  -> pic18f452\midi\update_without_installed_mios.hex

via MIDI like described at the http://www.ucapps.de/mios_bootstrap.html page.

This .hex file contains MIOS V1.9 and the update program. The updater will:

  - do a CRC check in order to ensure that the whole binary has been uploaded

  - replace Bootloader V1.1b by Bootloader V1.2

- end -

i thought that all i had to do was upload this one hex file to get mios installed,

then next i would have to upload the application (eg. midibox64)

maybe im missing something, do i need to have any banksticks attatched? i dont have one made yet

[illogik]

i think it's in the readme file;

if you upload "update_without_installed_mios.hex" and you allready have bootstrap v1.2 it will abort after 3 times. try the "mios_v1_9_pic18f452.hex, this is for a pic running with bootstrap 1.2

cheers

[Digispunk]

my PIC was from Smash, and it has Bootstrap 1.1b burned in,

- thats why i opted for the hex - -> pic18f452\midi\update_without_installed_mios.hex

either way, i thried the hex you proposed, and i got exactly the same error message

'Error: Received unexpected Upload Request

Aborting after 3 errors'

should i be looking for hardware malfunctions? or is this purely a software thing?

your help is truly appreciated!

[illogik]

999 out of 1000 times it's a hardware (construction!) error but you could be number 1000 of course  ;D

i have no concrete ideas for you at the moment..

[TK.]

You are using the right .hex file, never select another one (some of the .hex files could destroy the bootloader).

I think you should try to find out, why the PIC sends garbled SysEx responses. A message begins with F0, and ends with F7. So far I can see in your snapshots, there are multiple F0 within one message.

Currently I only know two reasons for such failures:

  - the PIC is reset during a MIDI transaction. This can happen on a bad PSU, bad or open solderings, short circuits

  - the PIC receives bad data frames. This can for example happen, if the MIDI interface cannot handle SysEx properly (ensure that you are using the MIDIsport Uno v4.2.0 driver), or if another MIDI hard/software sends MIDI data at the same time which is not merged properly at the software side

It would be interesting for me to see the whole MIDI In log during a code upload (you can copy&paste the messages)

Best Regards, Thorsten.

[TK.]

Another input: at the M-Audio webpage it is stated, that there are problems (...can lead to interferences) with motherboards stuffed with VIA chipset. It's recommented to install the latest windows version, and the most recent VIA 4-in-1 driver. Did you already take this into account?

Best Regards, Thorsten.

[stryd_one]

Those VIA chipsets have always been dodgy, and I mean always, not a single one has been any good with audio stuff... I highly recommend avoiding them.

[Digispunk]

i just swpped MIDI interfaces, so now im trying with an EDIROL UM2x

i did some tests to make sure it sends and receives sysex, i connected the 'in' to the 'out' with midi cable (i did this with both leads that i will use), sent the hex file in MIOS studio , and monitored the ports, it seems to send and recieve properly, i get exactley the same messages apearing in the 'in' as the 'out' monitors. so i presume the interface works,

now when i hook up to core board and set up the hex, with the 'wait for request before uploading;, i switch on the core, the core sends the request message, MIOSstudio sends the first block - and then nothing comes back in,

so i aborted the hex upload, and just powered down the core, and switched it back on to see if it would send the request again,

and there was nothing on the input monitor.

so i checked the midi connections in the MIOS device routing, i disconnected and then reconnected the MIOS routings, and then the monitor started showing the core request message again,

bizarre ???  it seems to be disconnecting the midi routing in miosstudio, i did this five time to check and it happens the same every time,

- with your other suggestions -

power supply - i am using the 'sid optimised'power supply made from the c64 power block, should i use a different power supply when uploading to the core?

i am going to check again with the MIDISPORT UNO interface, and get that midilog you asked for

[Digispunk]

this is what i get using the midisport uno interface -

it is obviously not the same as the message going out, also the hex upoad self-aborts after three atempts and prompltly displays  this error message ' Error: Received unexpected Upload Request Aborting after 3 errors'

MIDI IN MONITOR -

timestamp [unknown] | Sysex message: F0 00 00 7E 40 00 01 F7

timestamp [unknown] | Sysex message: F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 01 F7

timestamp [unknown] | Sysex message: F0 00 00 7E 40 00 01 F7

timestamp [unknown] | Sysex message: F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 01 F7

timestamp [unknown] | Sysex message: F0 00 00 7E 40 00 01 F7

timestamp [unknown] | Sysex message: F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 01 F7

timestamp [unknown] | Sysex message: F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 01 F7

[TK.]

thanks for the info!

so i checked the midi connections in the MIOS device routing, i disconnected and then reconnected the MIOS routings, and then the monitor started showing the core request message again,

bizarre Huh  it seems to be disconnecting the midi routing in miosstudio, i did this five time to check and it happens the same every time,

I know this effect from a bad USB connection I had some time ago. I used an USB hub in order to extend the USB wire by 3 meters, but this had lead to an unstable connection. Under heavy load, the MIDI interface was shortly not available, and I had to re-select the interface in the device list to initialize the driver again.

But I guess that this is not the problem here. Something seems to be wrong with the MIDI interface, the driver or with Java.

I'm not sure, but maybe it's related to the same Java problem which is mentioned at the bottom of this page: http://www.ucapps.de/jsynthlib.html. Although nobody has noticed this issue with MIOS Studio yet, maybe you are the first one?

Could you please try the proposed workaround which uses MIDI Yoke and MIDI-Ox?

And could you please try it with and without the "waiting for upload request" feature?

Best Regards, Thorsten.

[Digispunk]

would it be possible for some kind hearted soul to post me a link to download the sysex version of the hex file - please please please!

i tried to convert it myself with pearl installed but im a bit of a retard, although i can easily send a sysex using midi-ox -  :D

the hex i need is - pic18f452\midi\update_without_installed_mios.hex

here's hoping!!!

[TK.]

Just type "perl hex2syx.pl -os_upload update_without_installed_mios.hex"

(attend the "-os_upload"!)

Best Regards, Thorsten.

[Digispunk]

where do i type this command?

i am using windows xp -

do i type it in a 'pearl shell'

or in a 'command prompt shell'

im sorry im not able to understand this stuff unless its spelled out in simple terms because i dont have any experience with language programmming :-[