NefMoto

So with Tony's excellent flasher I have flashed an M box bin onto an H box ECU and am using it in a C box car.  I have modified it to use the Bosch MAF and 630cc injectors.  It was running really well, and gradually i've been upping the boost.  Last thing i did was alter the ignition map.  

When i loaded it into WinOLS, after editing in tunerpro, this time it didn't say any checksums need correcting.  Strange i thought.  Flashed the ECU and car drove perfectly.  But then I came to a stop, and tried restarting engine - nothing.  VCDS reports error code, checksum failed...

Error is P0601- Internal Control Module - Memory Checksum error.

What am I doing wrong?  WinOLS says all checksums ok.  Is there anyway I can force it to recheck?  I tried reflashing the file and clearing the fault code but it still comes back.

Rick

I've just tried to flash a previous tune which seemed to be working fine, and it is still throwing up a checksum failed code which won't clear, car won't start.  Does something need to be done once the ECU has  thrown this code to reset it?

I have attached the bin which caused the issue, can someone check it?

Rick

Do you have a copy of the bin before you made changes with tunerpro?

Jason,

yes it's a std Mbox file being used as the original, i've attached it.

I flashed this original file back, then cleared the DTC's with the Nefmoto flasher.  That started the car.  So put the other file back, and now i can't get it to generate a checksum failure.  Before connecting it to the car, i have power cycled several times as I know some checksums aren't checked everytime.

However, i have only started and warmed up the car, not driven it/taken it on boost.  I wonder if some checksums are only checked when they are being used - ie high load areas of the table.

Rick

File looks ok...

Just thinking out loud here - but the checksums are there for data integrity obviously - is there a chance you had a bad or incomplete flash?

Only thing I can think of.

Car drove perfectly though, engine off, 10 mins later no start...

I've modded the tune further, taken her on boost and so far all seems good.

Strange.

Rick

When the "Internal Control Module - Memory Checksum error" fault code shows up, the only way to clear it is after reflashing the ECU. If you don't reflash the ECU you can't clear that error code. This code was really fun to deal with before I knew the VAG flashing protocol, since it meant I had to desolder the serial EEPROM to reprogram it to erase the fault code.

The checksum that covers the map data section of the flash is only checked every few times you start the car. So you can end up tuning your car, going for a dew drives, and then your car won't start anymore.

When tuning my car, I always carry a spare backup ECU with me. That way in case something goes horribly wrong, I can always swap in the backup. I have never needed it, but I'm glad I have it with me when tuning my car.

This reminds me of the days when APR used to supply dealers with a special file "checksum clear" to kill that error.  Subsequent re-flash with correct software was required! 

Tony,

I'm getting this error again after I flashed a bad file.  I can connect to the ECU and have flashed a good file but still can't clear the code with your software.  Don't know how I did it last time this happened - ECU was on the bench, now it's in car.  Any particular order/procedure?

Rick

No worries  I sorted it.

For reference, I connected to ECU, cleared codes then immediately flashed.  Once finished, cycled ignition and then cleared codes again.  All good now.

RIck

Wait, im confused :)

To summarize, if you have a bad image AND a bad checksum (but you can VAG it)

you can

1) connect via VAG
2) clear the checksum dtc
3) immediately reflash with good image (via bootmode, or Tony's flasher?)

I assume if you go directly from 2) to bootmode, the ecu never has a chance to reset the Checksum dtc?

and if you use tony's flasher, he takes care of whatever "bad thing" happened when you booted *to the REAL "bad" code* between 2) and 3)

Flashing (with the protocol NefMoto uses) over obd clears the checksum error  in the e^2. Boot mode won't clear the the flag.

Sorry if I'm stating the obvious.

Not at all obvious, thank you! I'm a bit late to the party. I had read before this DTC was not clearable by VCDS, but that last post confused the hell out of me and made me think that it was.

So one last time: that checksum error CANNOT be cleared by VCDS, nor booting a "good" image x times, ONLY via the NM flasher?

Sorry if this question has been asked and answered, but the whole topic has me hopelessly confused ..

I'm sure Tony will correct if needed...

It's not just NefMoto, but the protocol itself. The act of a successful flash using it clears the error flag. I know this from threads here.  Pretty fundamental to know if you're doing OBD tuning I'd say!

This right here...

A few days ago I had the exact same issue... I download the NefMoto Stg 3 tune, and opened it in WinOLS, the checksum modules wouldn't recognize the changes/file and wouldn't report that they needed correction.

I tried different M box tunes after and found they worked, so I re-downloaded the file and it worked after that... So even though the file "looked" good, it wasn't.

Sorry. I agree, it is critical to know this stuff :)

So: more dumb questions: The protocol used by NON bootmode flashers?

I don't know 100%. take a peek at the NefMoto log to check or see if you can find the thread where Tony discussed this issue. Sorry, I'd check myself buy I'm on my phone and it's a ballache.

To clear the invalid checksum error code you have to flash using the VAG programming protocol and then successfully disconnect. In the KWP2000 message handler for the StopCommunication message, it handles clearing the invalid checksum error code when successful programming has occurred.

Boot mode allows you to flash the flash memory, but it doesn't do anything to the eeprom where the error codes are stored.

Thanks for the clarification, Tony. I need to add a note to the S4wiki to that effect.

Successful disconnect! That's the key then.  I reflashed a couple of times and it didn't clear the code, mustn't have disconnected buy cycled the ignition instead?

Rick

Once flashing completes, you need to click the disconnect button. The disconnection process is what clears the error code.

The next release of the NefMoto flasher has changes to auto disconnect when flashing completes.

Cool :)

Just wondering when Tony's new flasher will be available...?  ;)

The changes for the next release have been going and going and going. I have a stable release that just adds support for premium fast flashing, but I am still working on fixing a number of communication issues before officially releasing the next version.

Hello.

I have the same problem. I have flashed my friends car with my custom map. Car drove perfectly for five days and next morning he couldnt get it to start. we counted he had started the car 17 or 18 times before dtc came up.
i pulled of the code P0601- Internal Control Module - Memory Checksum error.

car had an unknown remap on it before that had rsa failure when cheched. also boost sensor and throtle sensor map where ff-ed and some other maps have been modified in an unusal way.
we agreed to make a whole new map from ori file from web. its a seat cupra 1.8t 180 2006 ecu 06A906032RP 371739.

map i have uploaded is attached - can someone verify checksum please?

car alows me to read/write but doest let me cleard DTC p0601.  I have read most of the threads on here regrading p0601 and im still not sure which route to go to solve it?

thank you for your help



 

oh yes
here's also the file which was read from car

So nobody is going to paste the output of me7sum? Just make us do the work? Or mention if the NLS script was used on it?

Hey.

winols reported chechsum ok, used two other programs to verify it both reported cheksum ok.

NLS script? (no lift shift)? 

from what i know file i modified was an original file

Maybe ORI you downloaded is not okay, post original bin. Also flash original bin on car see what will happen
And post your mods, what did you change on bin

File i used is attached.

i did flash my file again - no change
i did flash file which came with car - no change
can try ori file and see

maps in blue are the ones i changed
others that can be seen in folder my maps have been changed on map that car came with

74 cs' on ori - 1 not okay, 73 on modded

hmm, winols problem here?
i see 74 ok

Dude cmon

oh sh*t

@nyet
which file is that? the one the car came with? (reply#25 attachement)?

Well it is an RSA error, which ECUFix ignores by patching out the RSA routine. I believe some versions of WinOLS ME7 plugins do this as well, but I could be wrong.

So i tried flashing both maps several times, which was successful, but DTC can not be deleted. Car still wont start.

What are my options here? I have read many topics regarding P0601 and im still lost what to do next...

1. In boot mode write old eeprom( one you pulled out when there is no DTC)
2.turn off ECU
3. Again start ECU in boot mode and write ori flash
4.Turn off ECU, put in car and start

and then when you go to tune, use one and only one known good "checksum corrector" (i suggest me7sum as you will get the best support here). on ECUs with RSA, the different methods of "fixing" RSA (disabling using various code patches vs. self-signing like me7sum) will clobber each other in very unpredictable ways. using more/multiple tools does not make checksums "more correct."

Hello,

back from camping weekend with family.

Thank you for all the guides and help.

Im going to attempt to solve this today. ive never done this before but looks doable.

Ive gone thru ME7 EEPROM programmer topic - will give it a try. ( i should see death code in eeprom?)

Made a new map which looks clean in and out

any more advice - i dont have ori eeprom

eeprom succesfully read. this is what i got

that is not a valid eeprom file

hello

first a big thanks and heads up to a member of this forum who helped and guide me solving P0601 problem. wouldnt have been able to done it myself.

and ofcourse all the guides, executables from this forum are amazing.

it took some work but mostly understanding - and seeing how much one still has to learn  and can learn from community.

hopefully one day i can help another member...

few pics

For the love of god stop posting potato cam pictures of your screen.

Learn how to use screen shot and if its text, copy/paste using the \[code\] tag