NefMoto

So I flashed my ECU with the file attached, I used Galletto and put the car into boot mode, flash was successful and car started, I drove the car, came back to my house and shut it off. Now it won't start. I put my friend's ECU in my car and it starts. What can I do?

I tried flashing that ECU with Galletto with a stock file, 2 other modified files, and the file I drove it last time with and nothing. The ECU connects to Galletto, flashes success but it won't start.

Anyone have any idea of what happened?

I know it's not my computer or cable because I flashed my friend's ECU after all this occurred and it worked fine.

Yes, I did, well, TunerPro did it for me. The thing is, I actually drove the car with that file on it, then when I shut it off it wouldn't start back up, then I tried reflashing the ECU back to stock using Galletto and the flash completed but it still wouldn't start.

Can you connect with VAG?

I don't have VAG. But I tried connecting it to an other diagnose software I have (on my HTC touch pro) and it connected.

Can you try flashing with Nefmoto? at least then you'll get some verification feedback sector by sector.

Also, can you read out the flash and do a hex compare with the ori file to see if the flash chip has gone bad?

I haven't tried flashing with the NefMoto software yet, I will try that tomorrow.

Also, how can I read the flash? How can I check if the original flash has gone bad?

The checksums in your file are not updated! Seems like you have an error stored in the
eeprom now. Sounds typical that you once can drive and for the next driving cycle the
engine won't start. I am not sure if the ecu will clear this error after some time when
you have flashed an image with correct checksums. You could give it a try and
flash your orig file, then leave ignition on for several minutes to allow the internal checksum
process to finish. A complete checksum run inside the ecu needs more than 15 minutes.

Thanks, i will fix the checksums.  How can I verify they are correct other than my checksum pluggin popping up in a little window? I would like to not post any more files with bad checksums.

Okay, awesome, thanks soo much. I will definitely give this a try today. But what if it doesn't work? Should I consider the ECU done?

Are you sure you're loading the same XDF each time? TunerPro ties your checksum settings to the XDF. If you load a different on disk XDF file, even if it is identical content, then I sont knot that your checksums will update. I'll try this tonight and see.

Also, if your XDF headers are correct and you're not getting the checksums updated I think you need to contact MTX about the problem.

There is one indication in TunerPro that does tell you about the checksum updates. When you save the bin keep an eye on the status bar near the bottom left. When the checksum pluton update the file you'll see a green (yellow?) status indicator with the words "Checksums updated" or similar. I'm on the train right now and don't remember the words/colors exactly.

Tried this and it didn't work.

Anyone have an idea of what I could do to fix it?

Just to be sure, because I forgot to say: after flashing with your original you need to first
turn off ignition before then checking wether ecu would clear the error after ignition stayed
on for longer time. But most probably you tried it already this way.
Nevertheless, I don't think your ECU is done, it just needs to clear the checksum error.
Did you try to flash with the NefMoto flasher? I think a successful flash with this would
also clear the ecu's checksum error.

You need to flash using the NefMoto ECU Flasher!  ;D

Two out of the three checksums are checked by the ECU on startup. The third checksum is only checked every few driving cycles. If you have an invalid checksum error code, the car will refuse to start.

The only way to remove the invalid checksum error code is to flash over OBD using the KWP1281 or KWP2000 protocols. The NefMoto ECU Flasher uses the factory protocols over OBD with the KWP2000 protocol.

If you use boot mode with a tool like MiniMon, Galletto, or KWP2000Plus, then you reprogram the flash without the ECU knowing, and it won't clear the invalid checksum error code.

Reflashing your ECU with the NefMoto ECU Flasher will clear the invalid checksum error code.

That is why it is awesome, and boot mode tools suck.  :D

;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D

I'm trying right now with my FT232R and I will let you guys know how it goes.

I recommend upgrading to version 1.7.0.0 if you haven't. It contains a bunch of bug fixes just for you and your evil cable.

I will for sure! I already downloaded it  ;)

Thanks so much Tony.

Tried flashing with NefMoto's software, first I tried with Maximum Baud and Slow Init and it wouldn't flash at all and I had to do it in 10400 Baud and Slow Init, first try failed at 8%, second time at 51%. Decided to call it a night, and I will try again tomorrow. The flashing was really slow, I think I just need a new cable.


Since it flashed all the way to 51%, maybe it did the checksums and now I can flash it Galletto?

It may have completed enough of the flashing process to clear the invalid checksum error codes.

You can try this latency adjustment to see if it helps with your cable:
http://www.nefariousmotorsports.com/forum/index.php?topic=409.0

Do you have a log file of what went wrong?

Sorry, I thought I had uploaded it already.

I finally got to flash my ECU with NefMoto with no errors and the car won't start still =(

I'm going to use Galletto again, maybe it will work this time?

According to your log file, the flash failed after the ECU did not respond to a message for 9 seconds. I blame your cable, cause it doesn't make sense otherwise.

Do you know what your battery voltage is?
Did you try adjusting the latency in the FTDI device settings?

As for why the car won't start, can you check for error codes?

Battery Voltage is at 13-13.5V, I tried adjusting the latency.

When I flashed with NefMoto this last time (after I sent you the log) the flash was succesful, but it took about 10-15min.

Now, the car won't start, and the ECU won't go into boot mode.

Did you check for error codes?

You should always be able to get into boot mode. Boot mode is provided by the hardware in the ECU.

Update: After a lot of tries I got it to go into boot mode, it flashed, the car won't start though.

Just cleared the DTC's and nothing.  

Here is the log

What were the error codes?

If the first two digits of calibrationEquipmentSoftwareNumber are not zero, the ECU is unhappy. Your calibrationEquipmentSoftwareNumber is 0x80190000, where the 8 in the first digit means the ECU is unhappy.

I don't know. I gave up, I'm shipping it to a forum member that thinks that can fix it. I flashed it again using NefMoto and still nothing.

By the way, the flash took 11 minutes. I'm ordering a new cable tomorrow.

were you able to read the ECU after the final flashing to verify the code programmed was 100% correct?

If it was I suspect you have a fault in stored in the serial eeprom that isn't clearing or can't be cleared without manually reading and writing it.

Flashing with the NefMoto ECU flasher should clear any invalid checksum error codes, and the flashing process already validates that all data was written correctly.

All I can think is that you flashed the ECU with a tune that still had invalid checksums.

I was flashing the ECU with a stock file. I don't know what else could be

All I can suggest at this point would be to retry flashing.

Turn on ignition.
Flash a stock file that is known working.
Make sure it gets 100% complete and says flashing was successful.
Check for error codes.
Turn off ignition.

I got the checksum error code once, and Nefmoto cleared it.

Rick

Okay. Last time I flashed the flash was completed 100%, the window popped up. Do I use NefMoto to check for codes ''Read DTCs''? then clear DTCs?

W00t! As designed.  ;D



Make sure the pop up window says "success".
Yeah, do a "Read DTCs".

I took a picture. I will read the DTC's and clear them and see what happens. Tony, did you see my PM?

Let me know what the DTCs are.

I saw your PM, still working through my thought process.

These are the DTC's

Disabling Windows sleep mode.
Reading ECU DTCs.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Successfully changed to new communication timings.
Read 2 of 2 DTCs.
DTC: P0601 Status: 0x78 Decoding not licensed
DTC: P1602 Status: 0x22 Decoding not licensed
100% complete.
Reading ECU DTCs succeeded.
Restoring Windows sleep mode.

=/

Also, I flashed the file attached into an other ECU, everything worked fine, I shut the car off, then it started it up. I was driving it around the block and it shut off on me!! Then it started back up after a while.

These are the codes that other ECU pulled:

Disabling Windows sleep mode.
Reading ECU DTCs.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Successfully changed to new communication timings.
Read 1 of 1 DTCs.
DTC: P1602 Status: 0x22 Decoding not licensed
100% complete.
Reading ECU DTCs succeeded.
Restoring Windows sleep mode.

Note: The other ECU stopped working when I flashed the same file into it. Now this one is acting up, I know my checksums are done correctly, if one of you wants to take a look. Go ahead.

P0601 is "Internal Control Module Memory Checksum Error".
P1603 is "Terminal 30 low voltage"

As long as the P0601 error code is there, the car won't start.

Do you have the log file from the last successful flash?

When flash completes, do you click the disconnect button?

The ECU does some clean up of the programming mode in the StopCommunication message handler. It is possible that if the ECU doesn't receive the StopCommunication message correctly, it may not finish programming and reset the invalid checksum error codes.

Attached is the log file, I believe the successful flash happened in March 2. I will try to flash it again using NefMoto's software, and make sure I click on ''Disconnect'' when I finish the flash.

I sent you an email with some more details of my latest problems.

Sometimes you have to flash an extra chip on the ECU after you trigger checksum error code for it to come back. I can't remember correctly but I'll find info on it.

Okay, thank you very much.

Your log file does not show a StopCommunication message being sent after a successful flash. Both times the flashing succeeded in the log file, the connection was closed because the ECU eventually stopped responding to TesterPresent messages.

Please try flashing again, and when it succeeds click the disconnect button. Then we can double check the log file to make sure the StopCommunication message was successfully handled.

Okay, I will try that today. Did you see my email?

Yup, just started reading it.

Clicked on Disconnect and that did the trick!!!! =) =)

Tony, you're the man!

Thank fucking god. :D

Maybe I should force a disconnect after writing flash in future versions...

Lol

My night just got 100000x better since I fixed the ECU. hehe Thanks again Tony.

Pretty sure this would be why Galletto has you turn off the ignition for 10 seconds after the flashing is done. The ECU needs a little time to "finish up", patience is always a good thing with this kind of stuff.

Galletto using boot mode and boot mode flashing in general bypasses the factory flashing protocols, and so it won't remove the "invalid checksum" error code.

It bypasses the factory flashing protocols even when not using boot mode?

I updated the previous post to be clear I was only referring to Galletto in boot mode.

I have never been able to flash an S4 ECU with Galletto when not using boot mode.

Damn right Tony......lol

Good work Gwerks and team. Thought I was gonna have to loan you a box bro!

Reflex.

I just had this issue too using the v3.2 tune from judeisnotobscure. I tried following the same steps on here: complete a successful flash, disconnect etc... And didn't have any luck. After flashing and disconnecting I could connect again/start the car once before it wouldn't connect/start again. Only DTC that showed was P1602 which I think is just from disconnecting the battery so I could connect to the ECU again.

Any ideas?

You have to flash a stock file back on with the Nefmoto flasher, then click disconnect when the flash is done before unplugging your cable....
I'm working with mtx right now to fix my checksum plugin, sorry for all the problems it is causing.

Have added a checker: http://www.nefariousmotorsports.com/forum/index.php?topic=447.msg3150#msg3150

Thanks... this will be perfect.

Hello mates i have the same problem here i am using the nefmoto flashing tool about a week now and in my 3rd flash suddenly yesterday my car just won't start. I double checked my checksums reflashed old working version nothing. Even tried the 20minute ignition on trick. Nothing. Can anyone help? I will try tommorow again by connecting a power suply to the battery but during my previous efforts i didn't have any problems with the voltage. Please help i would appreciate any help provided.

Did you check the car for error codes?

yes nothing about chechsums only the code after flashing DTC: P0562 Status: 0x62 Decoding not licensed (witch appeared and the previous time) about low voltage on ecu or somthing.

Any ideas???Is there any chance that the ecu holded the error but that error can't be displayed?

well i am starting to make sense of all of this. I found an original flash for my ECU and i am getting the DTC P601 all the time without the possibility to clear it. I did the disconect trick but still nothing. I will post any progres.

Sorry for the slow response. Can you post which error code you are currently getting?

Do you have a log file from the NefMoto flasher showing it flashing the ECU and disconnecting afterwards?

At last the ecu woke up after the flashing with galletto in boot mode but i tryed 2 or 3 times reflash the file with the nefmoto flasher and suddenly it managed to clear the bad chechsum error code. Thank you all for the support and help. Tony you and your program are great. I attached the log that you asked anyway. Thank you again.

Thanks for the log file. Looking at the log I can't see any problems, as there are no bad echos, and no occurrences of the word "error" or "fail". :)

The trick with clearing the invalid checksum error code is to flash over the OBD port using the KWP2000 protocol that the NefMoto flasher uses. If you flash with Galletto it updates the flash memory, but it doesn't clear the invalid checksum error code.

Whoa. Is there no other way to clear that code?

You can desolder the eeprom and erase it yourself in a chip programmer. The only time the ECU will clear it on it's own is when the ECU is flashed over the OBD port using the standard VAG protocols.

Yes but you have to find a way to keep backup of your eeprom. So you can't escape the desoldering. I personaly prefer Tony's way and when everything fails the boot mode. Today i  flashed my car by boot mode with the ecu still attached to the car.

Similar situation as in first post happened to me. My ECU was still responding, no problem with connection, reading error codes etc. Probably boot mode on bench was not required but I did it.
First I've flashed in car with original bin using nefmoto, twice. P0601 error still on.
Next, I've flashed it with original bin using galleto in bootmode, simulated ignition off (pin 3), after 10s on, and left ecu on bench connected to power for about 50 minutes. After that I've plugged ECU into the car, fault code P0601 was gone! Engine starts and runs like before :)

So, my situation is another to confirm that this works!

i am trying this, it writes correctly - but the error DTC wont go, is still there.

car wont start either.....any help?

error code is the P0601- Internal Control Module - Memory Checksum error.

any advice greatly appreciated, as cant get the car started :(

Read "understanding/retrofitting immobilizer" in the cluster and immobilizer section. Look for the part about the death code. It must be cleared manually if flashing doesn't take care of it.

thanks, how do i get the eeprom off as i have no programmer/desolder to do so :(

You obviously didn't read the thread. If you did, you'd realize this is done via bootmode with no soldering required. I took a lot of time to write that, the least you can do is read it before asking questions that have been answered.

sorry, just read that bit on the first page i jumped in to the deathcode bit...arrgh bootmode :(

just read and digested it all.

understand i need boot mode, understand i need to correct in hex to 00 and then use commandline to fix the checksum with the tool provided.

only thing im unclear of, is
a: im struggling to get my ecu in bootmode Me7.5 06a 906 032 hn
b: what software/tool is used to flash to 95040 chip

btw great help so far, and apologies again for not reading it all...i understand this advice is free and know one has to help out.

Argdubs tool, linked on page is used to read and write the eeprom. me7_95040.exe.

thanks, found that now to.

will try tomorrow, but i have to do through obd and at present, getting ecu in boot mode is proving a pain in the arse!

hi

got the eeprom off, struggling with boot mode on the m7.5 ecu.

is there a proper procedure to do it, and is it ok to ground pin 24 from the negative off the battery?

(http://youyoukiller.free.fr/boot_mode/pin%20VAG/boot%20pin139.bmp)

this is the ecu i have

yes short this to ground battery to bootmode

[ed] Don't do this.

thanks, still no luck at the moment :(

i did manage to fix my eeprom (and get it off the car) - also i have deleted the two 33 33 and checksumed the correction

i just need to get it back on!  arrgh :'(

try with 5seconds short

You might need to use a resistor I once spent the whole night trying to bootmode and tried a resistor and on the first try it worked

hi a 10 ohm resistor?

10 or 8 is fine

argh at my wits end - tried for 2 days now to get bootmode, still no luck

i must be doing something wrong!!!!!!!!!!

i suppose you short circuit first the boot pin and after power on the ecu.

yup, ground pin - flip on power supply, count 1-2-3-4-5, remove ground, bootmode should be "enabled"

been trying all night, still no luck ???

FINALLY!!!!  ;D

after some advice from @vdubnation and some remote assistance, i have finally got it in to bootmode and remove the deathcode

i made a very crude bench flasher, used a 10ohm 1/2w resistor and BANG, bootmode first time and the eprom was written.

thanks for all that helped, also learnt loads just going through this little drama.

Well done! Cheers to vdubnation for the help!

hi, I have The same problem with several ME7 1MB cars. Would like to find a solution that deactivates the checksum detection e.g. by finding the code area which sets death code bytes in EEPROM to 33H and changing it to 00H. Any hint how to access EEPROM in ME7 ecus?
br - cruuz

NEIN NEIN NEIN NEIN!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

DO NOT GROUND PIN 24 TO THE BATTERY, YOU WILL FRY YOUR ECU!!!!!!!!!!!!!!

You need to ground pin 24 to the edge of the circuit board. The object is for pin 24 to have 0V for five seconds and then it will go into bootmode.

If you ground to the battery then you are giving the ECU 12V and it'll instantly fry it. Ask me how I know............

He said battery ground.

As in, the ground post of the battery.

Yeah, you just don't know what ground is. :P

Hi, i used the nefmoto tool and uploaded a tune, unfortunately I didn't remember to check the checksum and flashed it to the car.  I started it, took it a brief drive and it wouldn't start, I had the car recovered and found the P0601 code which has had me reading the site all day.

My understanding is that if I connect via netmofo again and reflash with the original file (downloaded from reading before any updates) or a fixed version of the tune that the P0601 would clear, is this correct?  I have reflashed as I describe, turned the key off for about 20 seconds and then subsequently left the ignition on for about an hour but the code remains.  I looked at the netmofo logs and everything looked fine.

Any help would be much appreciated as the car no longer starts and is now just an ornament.  :(

Many thanks, Paul

Car: Ibiza 1.8T
Cable used: Blue K line cable

To add some extra info.  I used Me7Check prior to flashing and it reported the file to be ok.  However me7sum found errors when I found info about it and subsequently ran it.  The original map which I flashed back on, I have read this with me7check and logs below.

ME7Check v1.08 (c) mki, 06/2004-04/2011
Checking file C:\Users\Paul\Desktop\Orignal map2.bin (size=1048576)
Reading Version Strings...
-> Bootrom Version = 05.12
-> EPK = 39/1/ME7.5/51/X505R//24C/Dst03o/190504/
-> Contents of ECUID data table:
   - '0261208521'         (SSECUHN)
   - '1037371739'         (SSECUSN)
   - '06A906032RP '       (VAG part number)
   - '0010'               (VAG sw number)
   - '1.8I R4/5VT     '   (engine id)
-> Contents of ECUID data table:
   - 'HW_MAN004'


-> No errors found. File is OK.   *********************