NefMoto

(http://www.nefariousmotorsports.com/hosted_files/Nefmoto%20ECU%20Flasher%201.8.0.0%20Screenshot.png)

Summary:
The NefMoto ME7 ECU flasher is a free tool that allows you to read and write the flash memory in your ME7 ECU in car over the OBD port. All that is required is a FTDI based USB OBD cable that works in "dumb" mode. Dumb mode cables pass the raw serial data straight through without applying any higher level protocols.

Features:
-ECUs can be written through the OBD port in about three and half minutes.
-ECUs can be read through the OBD port in about five minutes.
-User defined memory layouts allow for flashing any memory arrangement.
-Writing erases and programs one memory sector at a time to allow you to recover the ECU in case of failure.
-Written and read data is verified with checksums to insure data was sent correctly.
-Reading and clearing error codes is also supported.

This software does NOT:
-Does not update checksums or validate the file you are flashing in any way.
-Does not allow you to edit any maps, value, etc. It is just for flashing.

System requirements:
-32bit or 64bit Windows Vista or Newer (Will work if run inside a virtual Windows machine on Mac and Linux as well)
-.NET 3.5 (installed as part of install process)
-FTDI USB D2XX driver version 2.06.00 or later
-3 megabytes of free hard drive space

Tested supported cables:
-eBay USB VAG KKL using the FTDI D2XX standard driver
-Ross-Tech HEX-KEY-CAN using the Ross-Tech FTDI D2XX driver ("boot in intelligent mode" must be unchecked in the VCDS options screen)
-Any dumb OBDII cable using the FTDI USB chip

Tested unsupported cables:
-Galletto (Does not support dumb mode)
-KWP2000+ Flasher (Does not support dumb mode)
-Old Ross-Tech KEY-USB (Does not support true dumb mode)

Tested supported ECUs list on the wiki:
http://nefariousmotorsports.com/wiki/index.php?title=NefMoto_ECU_Flashing_Software

Known issues:
-No known issues. Please let me know if you find any.

How to install:
Please uninstall any previous versions of the NefMoto ME7 ECU Flasher before installing the latest version.
To install, download and run the attached file ECUFlasherHostInstaller 1.8.0.0.msi.
Then ensure that you have the FTD2XX driver installed for your specific cable.
If you have a generic cable, download CDM20600.zip, then extract it and install the generic FTDI D2XX driver.

What's new in this version:
-Lots of communication and multi-threading bug fixes
-Support for resuming failed flashing attempts from the current sector
-Support for licensed features
-Added ability to cancel the current operation in progress

You can find out how to enable the premium features here: http://nefariousmotorsports.com/forum/index.php/topic,954.0.html

How do we enable premium features?

Wow Tony thanks for all you do man.

Hot damn!

You need to buy a license file from me to enable the premium "Fast Read Flash" and "Fast Write Flash" features.

I haven't finished the main product page for the website yet, so I will update the second post in this thread with info on buying premium licenses.

Tony, any info about premium license?

^^^^^^^^^^^^

"You need to buy a license file from me to enable the premium "Fast Read Flash" and "Fast Write Flash" features.

I haven't finished the main product page for the website yet, so I will update the second post in this thread with info on buying premium licenses."

Do you have something to read the eeprom 95040?

Good work BTW!!

Just a quick question about read and write speed.  I was able to read a bin file from the ECU in about 6 minutes.  (ME7.5 MKIV GTI).  However I am in the middle of writing a new file to the ECU and it's taken over 60 minutes so far.

The 1.8.0.0 software information suggest that it should take less time to write than it should to read.  3 and a half minutes (write) vs 5 minutes (read).  I am set to the fastest baud setting, but the long write time makes me think I'm doing something wrong.

Hi Tony,
Any luck on adding the EDC16 ecu's to the software?

Thanks :)

Would be nice to see support for the windows xp platform.

I am hoping to add support for Windows XP around the end of September if all goes well.

The ECU prevents you from reading all of the memory sectors of the 95040 eeprom. Reading the eeprom is on the list of future features, and I can already do it. But since I need to add special handling to communicate to the user which sectors can't be read, I have held off on getting this feature done.

If you post a log file or email me one I can take a look at what may be going wrong.

I second that. Looking forward to that development.

Doug

If anyone runs into an issue trying to read ECUs with this version of the software, it is possible that it is related to a bug introduced in this version. If anyone is having an issue, let me know, and I will get a fixed released sooner rather than later.

I think the issue may be that the wrong Memory Layout was used.  The Supported ECU Wiki page states that 06A906032PL uses AM29F800 however, I can see AM29F800BB clearly written on the flash chip inside the ECU.  The xml layout files for the 800 and 800BB are certainly different and have a different number of sectors.  19 vs. 16.  I think this accounts for the writing speed problem.

I'm having issues with reading certain ME7 ecu's. I tried a 2000 1.8T AWD 400bb..Tried 4-5 times and after having a hard time getting the memory layout to verify it failed on the read everytime at anywhere from 25-75%. Plus it was s u p e r s l o w. I tried with a battery charger, removing the fuse for the ABS module, nothing would work. I've been having issues with other cars as well majority VW's. All stock cars. I'm using a Ross tech cable, and I've tried to reload the drivers twice. When I first started using it always worked like a charm..I've always used the most recent version. Windows 7 Pro.

I have yet to upgrade from rev 7.   Never had any issues with it.

Also wanted to add, when reading with nef it seems very voltage dependent. 90% of the time I need a battery charger on the car to have success. Anyone else have this issue?

I didn't see this kind of problem in 2 cars i tried the software. The one of them had a semi dead battery.

I've flashed my car a few times with the cluster showing under 12V... never had an issue (but I was worried).

What cars? What cable?

Hi :)

I just tryed first time the flasher...but no luck.

S4 2001 2.7 BiTurbo 265 CV ME7.1

I can connect to ecu,read dtc..fast init..slow init..all fine..
But i get no button read or write :o

Do i need any license to use it?

Best regards.RS

Im definitely excited to use this but I only have XP, are you still planning on implementing support for XP this month?

I have posted here before about how a lot of auto places sell conventional batteries when most of these cars actually use deep cycle batteries.  Conventional batteries do not provide enough voltage for reliable reading/flashing in most cases.

Interesting, Jason..I didn't see that post. Have you have issues like I mentioned?

Yes, and several friends who sell OTS tunes have had problems with aftermarket batteries as well.  The OEM batteries are expensive, but they are very good.

http://nefariousmotorsports.com/forum/index.php/topic,322.msg1984.html#msg1984

I am planning on trying to have support for Windows XP available by early October.

I will try to release a small update soon to address a couple small issues with ECU reading, and the FTDI info tool tips.

If the ECU read button is disabled, then hover your mouse over the button and it will tell you why it is disabled. You are required to have selected a memory layout and an FTDI device.

The ECU is flashed by sectors, but the ECU only requires that you flash entire sectors. What this means is that it should be OK to use a 29F800 memory layout with a 29F800BB or 29F800BT chip. This is because the only between these chips is that either the first or last memory sector is divided up into a bunch of smaller sectors. But it works perfectly fine to flash all of these smaller sectors as one sector, because the ECU only checks that the flashing memory range ends at the end of a sector. If you can confirm that ECU flashing works better with your ECU with the 29F800BB layout instead of the 29F800 layout, then let me know, and we can update wiki.

As for battery voltages. The NefMoto software officially warns you about flashing the ECU when you are below 12v. I have found that some OBD cables seem to be more sensitive to voltage requirements. It seems as though the more expensive OBD cables have more capacitors in them and are more tolerant to low voltage conditions.

I tried using nef software yesterday to no avail. There are logs attached here. I  have a hunch it may be my generic ebay cable. I am going to try today with genuine rosstech vcds cable in dumb mode and see how it goes. I thought someone could have a look at the log and see if I'm doing something wrong. I tried a few times, and it seemed to be working, and then it would fail :(    Thanks guys.

Ok, Rosstech cable read it great! 100%. It made 1024 size file. This may be a stupid ?, but how do I open it. It doesn't seem to open direct into winols. Thanks.

Edit: I'm computer dumb. I can't figure out how to open this in Winols. Someone help? What am I doing wrong?

Edit2: Nevermind, I got it. User error, lol. I'm still not sure why it doesn't save it as a bin.file? At least all the other bins I have say bin after them. This says "8 file". Can anybody clue me in why?

your file seams ok my friend.

Readout is o.k.

4B0906018CH - 0002 - 0261207216 - 1037360854 - 2001AudiA41.8 - 0x4924

Cheers,

PvL

add the .bin after the file name. you named it a '.8' file by not using an extension :)

I think new users should be warned that there is a possibility of bricking your ECU while writing, and should have access to a bench harness or an in car boot mode method, be prepared to remove your ECU if it goes bad, etc.  Especially if it is your daily.  Saying that there are no known issues isn't really fair, I get a bad flash and wind up on the bench 5-10% of the time.

I think the "bricked" ecu has nothing to do with nefmoto software. In contraire i think that it helps recover from stupid checksum errors and many more. The software is not responsible for cheap - crap china cables nor for low battery voltage etc. This is common for every software i have ever encounter. Also if you consider the money you are paying (0$) i think it is great. Finaly think that messing with ecu software and hardware always has the possibility of errors since it is for hobby use and is not for everyone especially the ones who don't want to risk. No pain no gain. I locked my ecu twise and i had to pay 100euro each time to unlock, before i was able to find all the "tricks" to do it right. My mistake both times.

One of the main reasons the NefMoto software is free, is because ultimately the responsibility of properly flashing the ECU rests with the user. Everyone wants to use their $5 eBay USB cables and flash their ECUs with a half dead car battery, as well as using BINs that don't match their ECU or have bad checksums.

But ultimately there should be more warning for new users that problems can occur when flashing your ECU.

Tony: stupid question. Is there a way to convince the ECU to let you send the flash standard CFI or AMD ident queries? You know... to autodetect flash layout...

Tony,

C box still doesn't want to play ball.  Has anyone else reported success with C box?  I can read it fine OBD with MPPS.

Rick

As far as I know, there is no way to detect the memory layout using KWP2000 or KWP1281. You can do it in boot mode with custom code though, by sending command instructions to the flash memory chip.


Do you know if MPPS uses KWP2000 or KWP1281? What part of the process fails? Does it connect?

I believe MPPS uses 1281 to connect and then usually switches to 2000 for faster flashing.

is there a version that will work with XP?

Not at this time

Tony,

with the C box MPPS tries to connect, then says mode not supported.  It then asks you to cycle the ignition and reconnects, so it must be switching protocols.

Rick

I believe the C box S4 only supports the KWP1281 protocol. The NefMoto software doesn't currently support KWP1281.

The C box supports KWP2000, but i think the problem is it doesn't allow the "simple"
security access algorithm. Also the upload service is not supported as far as I remember
-> no reading using the standard KWP2000 services.

Here are two K-line logs of the C box, one with failed secacc and the other one showing
successful secacc, rejected file upload service and successful file download service.

Anyone have any NefMoto logs trying to connect to a C box?

I believe the C box has to be flashed data area first...

Hi !
Tony, I've read almost all of this forum, You mentioned in march 2011 (it looks like before release 1.8.0.0) that You consider to implement automatic disconnection after flashing in next version, does version 1.8.0.0 automatically disconnects?


Why I'm asking, I was a little in a hurry and I screwed up checksums in my 032HJ and I get P0601 DTC. I've tried two times to flash just using NefMoto and each time disconnection was done automatically at the end and DTC was still present.

Now I've flashed in boot mode using galletto my ECU, left it "on power" for about one hour, tomorrow I'll try to flash ECU using nefmoto but it would be nice to know why I can't disconnect manually after flashing. Now it's to late (or to early, 3 a.m.), to cold to go outside to the car and flashing ;)

Thanx for reply.

EDIT: After flashing, nefmoto disconnected itself automatically. Bricked ECU now works perfectly.

Tony, You're the MAN!! Some day, people will write songs and poems about You!

Hey guys I'm having a very strange issue, I have been using the nefmoto flashing software for some time and first let me say thank you Tony because it is AWESOME.  However I went to go flash a new file yesterday and I cannot get nefmoto to open.  I click on it and it acts like its loading but doesnt do anything...  I tried removing it and downloading it again with the same results, I just don't get how it would do this all of a sudden, any suggestions guys?

Try running it in XP compatibility mode and let me know.

Already tried it with no luck, the only thing it does differently is ask for permission for the program to make changes or whatever, I click yes and it acts like its loading and nothing happens.  I feel like I'm going crazy over here it just doesn't make any sense.

installed software and was connected to my rosstech cable. However, it never gave me option to flash or copy the ecu.

2004 audi s4.

So I tried every memory layout, and not one of them passed the test. Tells me "to many unsolicited messages from ecu"....

Can I make it work? Thanks.