NefMoto

Hi,

I have a 2002 6 speed allroad.  Since I have owned the car it has always been throwing a P0601 checksum error that keeps the CEL on.

After much reading online and this forum in particular I obtained a stock bin file for my ECU.    I ran a checksum on the file before flashing just in case but no errors were found,  once flashed
the P0601 was still present. 

At this point I figured I just have a bad ECU so I purchased a compatible ECU from a 2002 automatic allroad.    I built a bench flash rig, cloned the immoblizer, and reflashed the ECU with the stock bin file.
Once again I am still seeing a P0601 checksum error on this "new" ECU.   

At this point it seems hard to believe that both ECUs are bad.    The car runs fine with both ECUs,  the CEL comes on after a few starts and stays on until the clear the code (it doesn't really clear its always present).

Has anyone else seen such a problem?   Attached is the bin file I have been using along with the stripped txt file containing the nefmoto logs.  (only contains the logs from the flash session).

Any insight would be appreciated.

Thanks.


http://www.filedropper.com/nefmotolog (http://www.filedropper.com/nefmotolog)
http://www.filedropper.com/4z7907551l (http://www.filedropper.com/4z7907551l)

you should erase death code from EEPROM and then flash it via boot mode
use visual me7logger -> EEPROM tool

Thanks I did some more reading on "death code" and I just ran 95040sum.exe against my original EEPROM bin, it found an error and corrected it.

I am going to flash this new file tonight and see what happens.

The problem is not the checksum of the eeprom. It's the error stored in the eeprom. Read the understanding/retrofitting immobilizer sticky in the cluster section :)

It shows the issue, and how to fix it.

I also read through the following post and looked at a pic that describes a couple of fields showing anything other than 0 will cause the P0601.

I opened my file with a hex editor and mine already shows 0's

Maybe I am missing something.

http://nefariousmotorsports.com/forum/index.php?topic=2973.15 (http://nefariousmotorsports.com/forum/index.php?topic=2973.15)

(http://i45.tinypic.com/2czwork.jpg)

Please upload your eeprom and flash here (not offsite). I will look.

Both are attached.   The EEPROM is from before I ran a checksum on it.

Update:

I haven't tried anything with my ECU yet but I did run 95040sum.exe against the original EEPROM bin from the new ECU and it came back clean.

If I run this against the EEPROM bin attached in this thread it does find an error and corrects it.   I was planning on reflashing the corrected bin last night but the rain here in my area stopped me.

I may get to it tonight but most likely I will have to wait until Friday.

See how it says REVO in your eeprom? That's your problem. Either the ecu WAS Revo, or currently is. These files will fix your problem.

I noticed that as well, must have had a custom tune on it at some point?

The odd thing is in order to pull the ECU out I had to use a dremel to cut slots into the security screws.   Maybe they just used an alligator clip on the back of the ECU without pulling it.

I edited my post to include the repaired file. Use both of them on your ecu and there should be no issues.

that ecu is no virgin.

Thanks for the help.   Can you enlighten me on what you did to the files?

I just looked into REVO dealer locator and the shop I bought the car from in Minneapolis MN is a revo dealer....

Makes sense, glad to get this figured out finally.   That annoying yellow light may go away yet.

I copied your vin and immo id, as well as logins and lock codes into a new eeprom and checksummed it. Then I just uploaded that, and a stock 551L file for you.

Another update,

First I flashed the ECU while it was still in the car with the provided 551L file.   After that I pulled the ECU flashed the EEPROM.

After installed in the car it was still showing the same error.    I then flashed the 551L file to it again but I am still seeing the same error.

Any ideas on what could be causing this?   The car still runs fine, I just drove it about 15 miles.

If you used the files I wrote, there is no way you still have that error. I think you're somehow not writing the eeprom.

I will write it again tonight and take a screenshot of the command prompt.

It must be doing something since its a used ECU and the stock eeprom would be giving me grief.

You are right, I don't think I wrote the file properly.  I must have overlooked the error message.

For some reason now I can only get version 1.31 of me7 to work.   However I am able to write any file I want without any error.

The only files that will let the car run are the original file I uploaded along with a checksum'd copy of the original.   Both of them work just fine but the error code is present when either is in use.

Here is a copy paste of my code:

me7_95040.exe --bootmode -wp8 -b 10400 551Le2p.bin

Ver: 1.31
Com Port: 8
Baud Rate: 10400
Opening COM8 ... OK
Starting Boot_mode ... uC identification response = 0xC5 (C167 derivatives) ...
OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... ... OK
Sending EEPROM driver ... OK
Searching Chip_Select pin ... P4.7
Configuring SPI Interface ... OK
Checking EEPROM status ... 0x00F0 ... OK
Writing EEPROM ................................ OK
Verifying EEPROM write ... OK
Closing COM8

Using the file you provided the immoblizer light blinks.    I'll start doing some more research on this site.   This is a lot of effort to make a CEL go away.

Thanks a lot so far for all of the help.