Firmware mismatch
Moderators: jsmcortina, muythaibxr
Firmware mismatch
Well this cant be good. I just assembled an ms3.0 from DIYautotune and uploaded the 1.4.1 firmware (freshly downloaded). It seemed to be successful but upon opening tuner studio i get confronted with this:
Your MegaSquirt is using firmware:
'MS333333333elease 20160421 12:211111111 JSM/KC ********'
Project Serial signature: 'MS3 Format 0524.05 '
MegaSquirt Serial signature: 'MS3 Format 0524.0555'
I have tried 2 different USB cables with win10 and Linux. It all results in corrupt firmware. So something is wrong.
Where do i go from here?
Your MegaSquirt is using firmware:
'MS333333333elease 20160421 12:211111111 JSM/KC ********'
Project Serial signature: 'MS3 Format 0524.05 '
MegaSquirt Serial signature: 'MS3 Format 0524.0555'
I have tried 2 different USB cables with win10 and Linux. It all results in corrupt firmware. So something is wrong.
Where do i go from here?
-
- Site Admin
- Posts: 39587
- Joined: Mon May 03, 2004 1:34 am
- Location: Birmingham, UK
- Contact:
Re: Firmware mismatch
Even though you tried two different cables, that still points to serial corruption somehow.
James
James
I can repair or upgrade Megasquirts in UK. http://www.jamesmurrayengineering.co.uk
My Success story: http://www.msextra.com/forums/viewtopic ... 04&t=34277
MSEXTRA documentation at: http://www.msextra.com/doc/index.html
New users, please read the "Forum Help Page".
My Success story: http://www.msextra.com/forums/viewtopic ... 04&t=34277
MSEXTRA documentation at: http://www.msextra.com/doc/index.html
New users, please read the "Forum Help Page".
Re: Firmware mismatch
Also, are you certain the PS you are using for MS is up to it? I had one which seems to run a Stim and MS OK on test - but caused problems when trying to load new software.
Rover SD1 3.5 EFI
MS2 V3
EDIS
Tech Edge O2
London UK.
MS2 V3
EDIS
Tech Edge O2
London UK.
-
- Site Admin
- Posts: 39587
- Joined: Mon May 03, 2004 1:34 am
- Location: Birmingham, UK
- Contact:
Re: Firmware mismatch
Nothing wrong there.
James
James
I can repair or upgrade Megasquirts in UK. http://www.jamesmurrayengineering.co.uk
My Success story: http://www.msextra.com/forums/viewtopic ... 04&t=34277
MSEXTRA documentation at: http://www.msextra.com/doc/index.html
New users, please read the "Forum Help Page".
My Success story: http://www.msextra.com/forums/viewtopic ... 04&t=34277
MSEXTRA documentation at: http://www.msextra.com/doc/index.html
New users, please read the "Forum Help Page".
Re: Firmware mismatch
James. Those pins are supposed to be shorted?! That seems really odd.
Re: Firmware mismatch
Keep pluggin at this.
All voltages doubled checked as per 13.5 in the MS3X/V3.0 manual, I measure 4.88v. swapped power supplies. Was using 1.5A wall wart and now 70A computer PSU. No difference...
After flashing this thing a couple more times I notice it doesnt always flash nicely. Using debug 3 i get:
Record 4353 results in Status code 0xe0. Is this normal? Then at the end it aborts. It doesnt seem to do this repeatable. Only maybe, half the time.
All voltages doubled checked as per 13.5 in the MS3X/V3.0 manual, I measure 4.88v. swapped power supplies. Was using 1.5A wall wart and now 70A computer PSU. No difference...
After flashing this thing a couple more times I notice it doesnt always flash nicely. Using debug 3 i get:
Code: Select all
Sending record 4352:7ca780
TX: c1 7c a7 80
TX: e2 cd 72 b8 39 7d f8 39 7e 7c 39 7d 18 87 fc 33
RX: e0 00 3e
Sending record 4353:7ca790
TX: c1 7c a7 90
TX: a3 87 c4 0f b7 46 cc ff ff eb e2 22 ac 89 00 35
RX: e0 e0 e0
Status code 0xe0
Prompt was α
Sending record 4354:7ca7a0
TX: c1 7c a7 a0
TX: ac b1 27 06 08 8e 00 0f 23 ec b7 54 59 b7 45 ec
RX: e0 00 3e
Sending record 4355:7ca7b0
TX: c1 7c a7 b0
TX: e2 cd 72 b8 37 a7 f8 37 a8 7c 37 a7 20 58 f6 2c
RX: e0 00 3e
Sending record 4356:7ca7c0
TX: c1 7c a7 c0
TX: 11 c1 05 26 4c fe 33 a3 b7 54 87 c4 f0 8c 00 20
RX: e0 00 3e
Sending record 4357:7ca7d0
TX: c1 7c a7 d0
TX: 26 3f b7 54 87 c4 0f 59 b7 45 ec e2 cd 72 b8 39
RX: e0 00 3e
Sending record 4358:7ca7e0
TX: c1 7c a7 e0
TX: 7d f8 39 7e 7c 39 7d 18 87 fc 33 a3 87 c4 0f b7
RX: e0 00 3e
Sending record 4359:7ca7f0
TX: c1 7c a7 f0
TX: 46 cc ff ff eb e2 22 ac 89 00 35 ac b1 27 06 08
RX: 3e 00 3e
Error code 0x3e
Aborting - send_block()
-
- Super MS/Extra'er
- Posts: 6828
- Joined: Sun May 15, 2011 11:41 am
- Location: Walnut Creek, Calif. USA
Re: Firmware mismatch
Have tried a pure RS232 (DB9) connection, no USB adapters or cables?
Re: Firmware mismatch
Well bill oldschool wins again here.
Usb>Serial interface works just fine. I finally got the firmeware on the daughterboard.
So using serial it seems to work just fine. Near i can for now.
but USB is still dead. even with correct firmware TS reports a mismatch with a garbled version number. bummer.
Usb>Serial interface works just fine. I finally got the firmeware on the daughterboard.
So using serial it seems to work just fine. Near i can for now.
but USB is still dead. even with correct firmware TS reports a mismatch with a garbled version number. bummer.
-
- Super MS/Extra'er
- Posts: 6828
- Joined: Sun May 15, 2011 11:41 am
- Location: Walnut Creek, Calif. USA
Re: Firmware mismatch
Don't give up on USB completely, it can work and is more convenient, since RS232 isn't so common anymore. I have just found that the USB was more fussy, wouldn't work with some laptops, but has been fine with my latest. There were no changes to the MS or cable, it must have been something with the computers or the way I installed the drivers.