NefMoto

[ed] This post has been entirely replaced by me - nyet [ed]

Latest release will always be here: https://github.com/NefMoto/NefMotoOpenSource/releases/latest

I have created a fully functional version (with fast read/write, no need for license) of the flasher based on Tony's released code (https://github.com/NefMoto/NefMotoOpenSource) and SB's changes.

The installer is barebones, it does not make a program group, or anything, and if you have nefmoto already installed it will prompt to remove it. By default it will install to C:\Program Files (x86)\NefMotoECUFlasher

https://github.com/NefMoto/NefMotoOpenSource/issues/1

All that will get done later at some point. If you are a developer, help in the form of pull requests is appreciated. Please consider giving back to the community.

Bootmode support is also incomplete

https://github.com/NefMoto/NefMotoOpenSource/issues/6

Please report bugs and feature requests here:

https://github.com/NefMoto/NefMotoOpenSource/issues

Note: Any attachments to this post may be out of date. Please use the above link instead of anything attached to this post

Tony, thank you for this!  So many possibilities opened up now that the source is available.

What sort of features would you like to see added to Nefmoto? 

Please provide:

• description of the feature
• a use case that exhibits that it would benefit the entire community and is not for the sole purpose of your own personal gain

bootmode. fast flashing mode (unless tony wants to keep that as part of the premium version etc), command line version

i will probably work on the last one permitting.

What about me7correction integration?
To prevent flashing unsummed files.
And/or automatic checksum correction before flashing starts.

If you forgot to sum the file before flashing.
Or simply preventing some oblivious person "bricking" the ECU,
Resulting in a flood of post asking for help to do something
Which has been discussed a million times over.  :P

me7_95040 integration?

Will the new flasher recognize a brand new Vag Com V2 USB cable?

Med9 flashing and logging possibilities?

Agreed! I think this will be the first thing I add in.

Ability to read DSG TCU's would be a cool feature.

Thanks Tony! And all that will add in the code thanks in advance!  :) Known bugs like  baudrate change before any new /extra features I would say!

SB is nothing like prj; you're way off target. Let alone Tony.

There is absolutely nothing secretive about the nefmoto software; it now literally is all there on github. It took me quite some time to convince tony to release the source (there were actually other real reasons why doing so was problematic, not the standard "I can't give things away to noobs" attitude).

If you don't have a background in software dev, it is extremely hard to explain why some projects are harder to build than others, but trust me, it is NEVER because somebody is trying to keep something secret or because they're elitist.

It is because writing good documentation is a ton of work, even when the target audience is experienced devs.

If you expect somebody to just do all of that work for nothing, then complain when they don't, you're simply not seeing the big picture.

It took me 10+ years to compile the basics of the s4wiki tuning page. I never took a dime from anyone, nor did I play the glass bead info trading game which would have prevented me from publishing things I had promised to keep secret in order to learn them. I could easily complain that is because of the toxic nature of the tuner industry, but that would be vastly simplifying the point; the bigger issue is that for some, that is their bread and butter, and they do jealously guard everything they learn because that is part and parcel of their business model. The arrogance and condescension comes from that.

But never confuse that with the frustration expressed by somebody who just doesn't have time to explain something to somebody who has literally zero experience in either tuning OR software development. It is a daunting amount of work, and tiring to post the same explanation over and over and over and over again.

BTW this not the first time i've posted an explanation like the above. It pains me to have to do it yet again for the umpteenth time. Now that you know, feel free to help me and post the same information when the next guy complains about stuff ;P

Thanks nyet.  I never meant my post to come off as arrogant.   I thought I described what needed to be done was enough.

Simply stated, there are already buttons on the form which will allow you to fast write / diff write...whatever you want to call it.  They are disabled if a license isn't present.  All you have to do is modify the code that says

diffWrite.Enabled = hasLicense;
to
diffWrite.Enabled = true;

Anything more than that, and I would have to explain how to develop a .Net application.

In case anyone was wondering where the source repo was:

http://nefariousmotorsports.com/forum/index.php?topic=12861.0title=

this thread is a sticky in this very subforum.

SB: if you have time, can you make a build with free premium? Tony has pretty much given us the ok to do so.

I would do it myself but as I mentioned before I'm swamped with a new job.

Next on my list would definitely be to fix the baud rate changing issues.

Yes, I can do that.   Might be a couple of days until I get time to do it.  I work and stuff too.  :P

The open sourced version already has the baud rate issue fixed

I made that up; it does compile.  Not sure what was wrong with the version I downloaded.

OnlyWriteNonMatchingSectors = false.

Set to true, should be good to go.

I've forked the open source git, and committed the changes needed to enable diff writing.  Feel free to look at the changes that were needed for this.

https://github.com/sbloom82/NefMotoOpenSource

I will test it and make sure the rest of the tool is good to go before uploading an exe.

That's what I though too the first time I tried it.  Just a bit more than that to make it work. :)

Hey thanks man! I was looking through the github repo yesterday and could not line things up with my installed version. Now I see why  ;D

well if its legal for now, ive played some time ago with it but not finished :(
+ 249k baud
+ checksum verify // but it doesnt work when different file was loaded dunno why
- checksum correction built-in func doesnt work iirc

SB_GLI can send u sources for a stable ver cos have no time

uhhh pull req?

no git acc

All available for download on git.

dude cmon. You can't expect to get sent a bundle of sources.

learn git, do it right

I get a security access rejected on that version. Will have to dig deeper tonight.

Me too, but only before I had set the baud rate. Fast write worked fine (did not test other functions).

Yep, if you don't set it, it defaults to 10400 and then it doesn't work.  :)

and LOL, I deployed a shortcut in that zip that is specific to my pc's hard drive... yeah that'll work real good.

I have pushed all the changes to the main repo, and added an installer target using wix (requires wix 3.x)

Ill be updating the OP whenever I release a new installer.

In the meantime, somebody needs to fix the baud problem :)

Please submit bug reports and feature requests here

https://github.com/NefMoto/NefMotoOpenSource/issues

See op for release.

http://nefariousmotorsports.com/forum/index.php?topic=12861.0

Can you confirm this is still a problem?

https://github.com/NefMoto/NefMotoOpenSource/issues/2

Tony says he thought he fixed it.

Latest .msi release gives me install error "Source file not found: cab1.cab cannot be found".

thanks i'll take a look

added 1.9.4.3 to OP, can you try it again? Thanks.

No problem and yes 1.9.4.3 installed correctly, thanks! Ill give it a shot flashing to see if the baud rate issue is happening for me.

I can confirm this is still an issue, if not set (left at unspecified Baud) on initial connection it will default to 10400 Baud, and then it has an issue with communication to the ecu.

I wonder if it's ACTUALLY connecting at 10400.  I'll need to debug it later on.

I believe it is.   I traced the code and it pointed to 10400 default and I didn't see another way around that.  I can't confirm 100% though.

If you are running a debug build you should get the more detailed debug logs in the log window and file.

Thank you for your hard work ! 

Issue added to Git.

**update***

Deleted all "nefmoto" registry values, re-installed, and it's working.

I'll update the Git.

Hey guys thanks for this ,only saw it yesterday when I came to  look into getting the licence for fast write  access.
anyways, I tried  the checksum Tab but the program crashes on win7, I then  moved on to try the fast write which was successful
until I realized I uploaded a file without corrected checksums lol  ( I was always careful before)
gonna try the boot mode feature now  :-[

you guys are awesome

Bootmode has never worked.

well that's it for me  :(,thanks for the info

https://github.com/NefMoto/NefMotoOpenSource/issues/6

thanks for that information  Nyet,after opening the ecu , soldering wiring and switch for boot mode (for future  mistakes lol)
I reinstalled the ecu and was able to connect to it normally and flashed successfully ,no boot mode needed.
I think I got away today ....thanks

I just saw this. Is there a list somewhere of the changes made? I have the actual paid version like before the source code was released. What improvements are there?

I just noticed that Tony thinks tabs are equivalent to 4 spaces.

Bad monkey.

How can i use fast init mode ? Is it only in premium version ? And if its it only there where can i pay to receive full version ?

Also i have a little problem with the program. Usually im flashing with MPPS but today i decided to try Nefmoto Flasher.I like it, works faster but car cant start after flash is ready.The file is checksum-ed but dont know where is the problem.Used 10400 Baud and 800BB Memory. My car is Audi A4 B7 ME7.5 Wideband with 1024kb file. After nefmoto flasher, Flashed the SAME file with MPPS.It flashed for half a minute and car starts without problem. Tried again, flashed with nefmoto and doesnt start, after that mpps and start. After that just read the flash with nefmoto flasher, ONLY READ, after that car doesnt start and i needed to flash over it again with mpps. What im doing wrong ?

There is no longer a premium version.

Likely your file has checksum problems. You did not post the output of me7sum (or the version of me7sum) you are using so there is no way for anyone to verify you did it right.

So can i use fast write mode ?

Now im posting the file that im flashing with Nefmoto Flasher and MPPS. Its same file that works with mpps flash and not work on nefmoto. The file is exported from Full version WinOLS, so its checksum ready, because i started the project from original file.Also checked it with me7sum but it tells me it doesnt have errors. Im Attaching the files.Posting also Original file if needed.

Can be wrong memory layout ? I used 800BB, but what about BT or 800 ?

Yes, that looks right. Also fast write should work
you can try writing with MPPS then trying a read and comparing it to the file you tried to write with.

If you have NLS on that file, remove it, it will interfere with RSA, which MPPS patches out completely where me7sum does not.

Do i need Fast init connection to use fast write ? Because fast init doesnt work for me.Tried all baud but cant connect.

I writed a file with mpps.After that i read it with Nefmoto Flasher, after that car refused to start before another mpps flash. I have a file but dont know how to compare them.Uploading file that i flashed with mpps and the other that i read with nefmoto flasher.

Dont have NLS

Those are identical.

So i made everything right, but car cant start with Nefmoto Flash. Even worse, after Nefmoto reading car wont start.It makes something but dont know what.After flash Nefmoto says its ready and tell me what was the time for flashing.After that i click ok and in console see it Disconnected.Should i do something more after that ?

Any codes?

http://nefariousmotorsports.com/forum/index.php?topic=981.0title=

You have a problem with cable/driver or you PC.
I have that problem long time ago on my laptop... after clean instal of windows problem was gone

Sorry it will not help you, beacuse your flash proces finish to end. I have problem, that nefmoto stop at some point when flashing

My ecu is not on the list. Mine is 8E0 909 518AQ.
Will try older version of Nefmoto Flasher - 1.8 which have Memory layour verify.

That list keeps growing ;)

Do you see any dtcs? After flashing with nef, does VCDS connect?

http://nefariousmotorsports.com/forum/index.php?topic=981.msg125298#msg125298

Will check again tommorow for DTC and VCDS connection. Like BlackT mentioned, maybe my ecu wont work with Nefmoto. Too bad

Just pick a different binary or patch AQ with the fix.


http://nefariousmotorsports.com/forum/index.php?topic=6719.0

Dont know what means pick different binary. Also tried to open the file that i want to flash with winols 8bit search or HxD but on both i dont have any results.Nothing close to the fix in the topic.
And if fix worked, should i do it every time im exporting new file for flash ?

Yes the fix is worked. With little help found the line that should change and now the problem is gone.Thanks.
Want to ask, if Diff write flash i good option ? Tried it 5 times today and work good.Should i use full flash from time to time or when i have only little correction i can use Diff flash ?

Yes, fast write should always work.

Struggling to get this downloaded and installed right.  Downloaded the fully functional version off the github.  But cant seem to find out how to get it installed.    THe .msi installs the 1.9.4.3 version of the flasher, but still cant see any fast write part of it.

"fast" is actually "diff write"

Thats what I normally use when flashing.  Normally takes in region of 4mins 30seconds.

Thought you could get it much quicker than that?

The less you modify the less it will have to write. Also you can try increasing baud rate.

even a 1x1 KRKTE byte will take the same amount of time :(  Normally have 10400 baud rate with a VCDS lead

That's about as fast as it will go, since even a single byte change alters quite a few checksums.

Also, because of the way flash works, changing a single byte requires erasing and rewriting an entire flash sector.

It shouldn't take 4 minutes 30.  Single/small changes typically take ~1 minute for me.

My flash time is always 1 min 20sec to 1min 40 sec
No mather if I change 1 byte or 10 scalars and  10 maps
Diff write, baudrate max

With diff write im always 1.50 to 1.55, no matter what im changing.My file is 1mb.Using Baud - 38400

Is there anyway to get this to work with Openport2.0?

Sure, it's open source.

In its current form, no. It's hard-coded to use FTD2XX and the FTDI driver DLLs. OpenPort 2.0 is J2534.

Hi!

What could be a problem with my car if I cannot read the flash with max baudrate? Only the lowest speed is working. With other baudrates it fails around 15%. I havent tried the write because of the reading issues.

You may need a dedicated k-line or pull the cluster fuse. Also try bench reading it if you dont have immo.

Im getting a weird problem with reflashing on Write Full vs Diff Write on ME7.1.1 B6S4. IT seems when i do full write it doesnt close out the ECU correctly or something after the reflash is done isnt the same as Diff write. For instance i can do a full flash. "no-start condition" then i diff write the same rom OBD mode nothing different. it says YUP its all the same, closes out and poof car starts again.

Do you guys still make updates to this application or should i just know that DIFF write is what i want to use? If you need logs i can get them if not just at least mention this in the software release notes?

I believe this is a known issue with st10 flashing, which isn't 100% supported. I don't know that there is an issue for it that is logged in github.

Program works great otherwise. If logging could be fixed with the right security key like the melogger program and that full write... it would be mint. But i spent countless hours getting visual logger to work finally so, meh.

If you need logs to put something in github let me know. I know now so im happy...

No, i don't, i need someone to submit pull requests :)

Or open an issue anyway.

Had a more odd outcome on another B6S4 today. I would diff write. it wouldnt start, i would diff write the same file (checked 19 sections with no changes) closed the ecu out and then boom it starts. Weird. Mine doesnt do that. Same ECU same revision code on it.

Possible support for MED9.1 down the line?

Unfortunately, no, very different.

Would be a ton of work and likely totally different app

Quote from me7_95040 eeprom thread.

@nyet, can this code be found and enabled in this open source version?

Yes, it is possible, but requires somebody to go do it.

This software can be used with a generic KKL cable (don't know at this moment which FTDI chip has) or with a Galleto 1260 to flash EDC15P? It has same flash chip as ME7, 29F400BB  and cpu Infineon C167, but I don't know if it uses same communication protocol. My MPPS cable is lent to someone and I don't trust anything else to flash EDC15P, like Galleto 54, or 1260, or Kess.
Thanks.

Only me7 it wont flash edc15

I'm trying to use this awesome program for logging. It connects and reads the ECU info no probs,  but keeps getting an error when logging.  Its an ST10 with IMMO off, on the bench. BTW ,VCDS works fine with forced kwp2000.  I don't need to flash, just need logging.

May/2021 02:48:47.487: USER: Starting variable reading.
05/May/2021 02:48:47.497: LOG: Starting DevelopmentSession diagnostic session with 10400 baud rate.
05/May/2021 02:48:47.497: USER: Starting diagnostic session.
05/May/2021 02:48:47.524: LOG: Sent message with service ID StartDiagnosticSession
05/May/2021 02:48:47.565: LOG: Received message with service ID: NegativeResponse
05/May/2021 02:48:47.565: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SecurityAccessDenied_SecurityAccessRequested
05/May/2021 02:48:47.565: USER: Start diagnostic session failed, ECU reports security access is required.
05/May/2021 02:48:47.566: USER: 100% complete.

anyone manage to solve the verify checksums tab crashing for win7? github thread doesnt look like there's progress. Don't mean to be greedy.I very much appreciate this awesome piece of software. I'm not a developer so I wouldn't know where to begin solving this.

this was the event report:

I have problem with Nefmoto flasher 1.9.4.3 via OBD. It refuses to write. Cable is blue kkl with 232RL and it works perfectly with other programs (writing with me7eeprom etc).
Whether the car's immo is enabled or not didn't make any difference, I tried both ways. Car is -00 Audi TT (1.8T AJQ)


Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: 8N0906018AB 1.8L R4/5VT
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Connected

Writing ECU flash memory.
ECU reports programming session preconditions have been met.
Negotiating communication timings.
Succesfully changed to new communication timings.
Requesting security access.
ECU reports that security access is not supported.
Starting diagnostic session.
Succesfully started diagnostic session.
Negotiating communication timings.

Disconnecting because no response was received for the Tester Present message.
Disconnected
Writing ECU flash memory failed.
100% Complete.

Is the ECU stock? Does it have a riser?

Yes, ecu that car has come with, and no riser

pin 121 powered up?

http://nefariousmotorsports.com/forum/index.php?topic=13149.msg107893#msg107893

Does the cable work on other ME7.5 ecus?

pin 121 did not exist in the wiring harness in ecu connector, was empty i.e. there is no power. Looking for schematics of autodata it should have direct connection to ignition coils' black/violet wire, but it did not.

I don't have other ecu's to try...

However, with the china-clone mpps v18 cable and its program, I can write through the obd in this situation, so I'll use it for now until I try to add pin 121.

Reading is also not possible with the nefmoto program.

512kb ECUs can't be write or read with nefmoto soft.
Use mpps(2 min to write)  or galleto 1260(slow 12 minute to write flash)

Nefmoto is working for me with 512kb ECUs, but with "some special procedure".

- turn ignition ON and connect to ECU
- select 400BB layout and file to write
- click write and wait for it to fail with messege "A communication error was encountered while flashing. Press Cancel to abort, or OK to continue after reconnecting."
- click OK and wait for it to disconnect
- turn ignition OFF and click reconnect

It will say now "THIS-IS-THE-RAM-PROGRAM-" in KWP info, get SecurityAccessPositiveResponse and start write.

I don't even remember how I came up with this, but it works for me every time for many years...

Thank you, this helped.

I got the writing to succeed when I waited a good moment after that dialogue (and pressing ok), and pressed the connect fast/slow init button again. it started writing!

I also tried turning off / cycling the ignition there like you suggest, but that prevented the operation.  

however, I get "erase report failed" errors, despite that the writing goes through and no problems occur.





even this functionality is enough and makes nefmoto a winner, but what could be the reason for those? I'm already fed up with the fact that mpps v18 is not 100% reliable, it randomly brickes the ecu, and has to be repaired via boot mode. I can't get the Galletto 1260 to work, it freezes in all operations, no matter what I try to do with it.  :-\

I'm not 100% sure of what is going on, but the RAM program is what runs when the flash process totally fails... its basically the ECU running in a failsafe mode (from RAM) which means if it loses power, you have a brick.

For whatever reason, NEF can get the flash process to complete when the ECU is in that failsafe mode, but NOT when it is (normally) running out of flash.

Presumably its a minor bug in nef... not sure who is qualified to debug it