Hi, I have a problem that i cant seem to troubleshoot from any other info off the web. When I use the Megasquirt Embedded Code Update Utility to try and load the latest code onto MS2 I get the following message during the verify stage.

Verification failed: At 0x4940 expected 0x06, found 0x00.
Exception caught: 4

Its very annoying and I have had no luck searching the web. Quite frustrating! All connected properly - power supply is good to the stim - I have done all test up until this stage and all passed - i'm stumped!

Anyone help please.

have you put a paperclip in the boot hole i had to do that to load new code on mine

have you read the manual

http://www.msextra.com/doc/index.html#ms2

Have you set the jumper on the MS2 daughterboard.

also note this from the MS web site

Note that 'File/Update' does not work on the downloader to fetch the latest code and INI anymore. You can get the latest code and matching INI from this link: www.megamanual.com/ms2/code.htm

Yes I put the jumper on the boot load pins/header. Yes i'm happy that the updater part doesnt work. I downloaded the code and used the 'open option.

Not sure what you mean by boot 'hole' - do you mean the jumper for the jumper headers on the ms2 daughter board?

yes i mean the jumper lol could not think what it was called
on mine i had to upload it to the new code to my laptop then start again with the ms and load the new code

Thanks for the link - i tried it with the .bat file which runs in ms dos prompt / command prompt.
Thought it was going to sort it but when it come to the verification stage it still fails after a few stages!

Annoying! Tried all the tests again - no problems, it seems to fail at exactly the same point.

By all accounts this means the fault is the interface between the computer and MS2 and not MS2 being faulty (according to the website)

Hmm - any ideas?

Do I need to Verify???

If i write the correct code and its ok - whats to say i cant just use it - or am i missing the point

Could be the serial to USB lead you are using notoriously unreliable

try running it with i think option 3 or 4 (what ever one so that it goes slower) that usually works. aslo have you checked that you are running on the correct baud rate?

Baud rate is definitely 115200 for the correct com port. I have tried using 0,1,2 and 5. Will try 3 and 4 but I'm pessimistic about the outcome. Maybe the USB to serial cable is not great. Does anyone know of one which definitely works.

If the USB to serial cable passes the loop back tests, does that still mean it could be unreliable??