Problems flashing MS2 chip - where am I going wrong?

[squirrelgripper]

I'm upgrading from the standard MS2 code and having problems.

When I try to run MS on the stim, all I get is a flashing fuel pump LED and LED D14 stays on constantly.

Using the "Download-Firmware" program in the Megasquirt program menu generates 1 of 2 errors:

ERROR: unkown error status response e=0X79
-or-
ERROR: timed out reading response 0XE0

I also can't revert to the original MS2 code, and Megatune does cannot communicate with the COM port I am using. I took the advice of the MS2-Extra manual and increased the COM port serial data rate to 115200, it didn't make any difference.

Is this a problem with flashing the chip, or something else?

[racingmini_mtl]

You're not using the correct method for loading the new code. You have to use the "download-MS2-firmware.bat" file that comes with the beta release you want to load.

Just run this file and follow the instructions on the screen

Jean

[squirrelgripper]

You're not using the correct method for loading the new code. You have to use the "download-MS2-firmware.bat" file that comes with the beta release you want to load.

Just run this file and follow the instructions on the screen

Jean

Thanks Jean,

I tried to download the code as you suggested, I still get an error code and it doesn't work.

[muythaibxr]

Which instructions did you follow on the screen?

[squirrelgripper]

Which instructions did you follow on the screen?

(selected correct COM port)
Upgrading from standard MS2 code? (I tried this both ways, same outcome).


Is there any kind of chance I've fried the MS2 board? Would there be any response? That's kind of a long shot, I know, just wondering if theres' a "typical" response when this happens. I have the same V3 main board I've been trying to upload with currently running another MS2 chip (the original 32K chip), so the main board seems fine. it also uploards firmware updates to the 32K chip just fine, FWIW.

[jsmcortina]

I'm not sure if you are trying this or not, but neither MS2/Extra nor latest MS2 versions will work on the 32k chip. You have to have a C64 to use these codes.

However, if you are simply using the C32 chip to confirm that serial works ok and loaded v1 code to it as a test then that's fine. It would confirm your COM port selection is ok and serial works right.

let us know which you were trying to do

James

[squirrelgripper]

Thanks James.

Using the C32 only to confirm that the box still works (and it does) !

Trying to upload the MS2-extra firmware to a C64 chip.


Iain

[offtrack]

what hardware are you using.?
name the PC , and model #
name the com port exactly. " built in com, or add in, or usb converter?"
there are at least 5 ways to communicate.
name the software or script you are running.

[6040solder]

name the com port exactly. " built in com, or add in, or usb converter?"

...and the chipset that is on/in that device!

and maybe driver revision.

[offtrack]

works perfect;
QX16CF950 Cardbus pcmcia 15mbps com port. in to Dell CPX
software ver:
oxser.sys , 6.05.01.05
oxui.dll 6.5.1.5
from colordrives.com

DOA any Dell CPX with
intel 82371AB/EB PCI to isa bridge com1.
measured clock rate is inaccurate by 3%, by design.

running XP , sp2, with xp2 serial driver.
tests: many times and at different temperatures ( tricky for clocks)
Megatune with MSxtra release latest
same with beta 18
and using the batch file down loader ,
many times .

total spent $20 to get a good com port. piece of cake
MS rules.

[squirrelgripper]

Thanks Offtrack, I have the same USB >> Serial cable. I've updated the driver, we'll see if that helps.

My computer: ACER Aspire 3000, Windows XP
Texas Instruments PCI-1410 CardBus Adaptor.

The computer and USB-serial cable have worked fine with the MS1 code variants, I'm not sure if this is the problem, but I have 2 other computers that I can use to check.