NefMoto

Hi Gang,

I'm sure some of you read that I'm doing a swap. ddillenger sent me a file to flash my auto to a manual. I have yet to be able to do it with the nefmoto software, although it did seem to take with he galletto. As some of you know I have 2 ecu's, which seems pretty common. before I risk my working auto, I would like to get the used ecu working first. Both ecus are the m7.1.1 types. Both are 95160 eeproms types. I think I read that the eeprom doesn't matter as such if I flash the file given to me with the nefmoto software, Is that correct? Should I need the eeprom to match VIN and SKC, still how to go about correcting the checksum of a virgin 95040 into a 1024b from the 512 ? I know how to make it into a 1024 file adding the zeros but the tool from turboats still shows it expecting 512. I feel I'm on the right track, just wandered off the main path, If not please school me.

Thanks in advance for any and all advice

NWFDUB

You are confused and mixing EEPROM and FLASH size numbers  ;D
The eeprom is 0.5kb. you can flash your eeprom files from one ecu to another (this is actually cloning the vin and immo etc).

Ugh, thoroughly confused now! I went back and reread it just to make sure, Argdubs tool is for the eeprom correct? That is the tool I used to read what I thought were my eeproms and they are both 1024 in size. So your saying that is not my eeprom and that is my flash? Yet in the hex editor, I can see my VIN. Can someone please set me straight? I think i'm getting lost in the verbiage.

1024 what? kb or b?

The file size is 1KB

EEPROMs are usually 512 or 1k, Flash images are usually 512k or 1Mb

So then the eeprom IS the 1KB file then. OK where can I get a virgin 1kb file ? All of the virgins I see here are 0.5kb variety.  BTW Thanks Nyet.

Why dont you just write the one eeprom on the other? Can you maybe attach it so someone can check out how it is written. I thought you where making the mistake of b>kb, that happens more often. I only know the eeprom as a 0.5kb version, but yours seems to be 1kb then. I would not bother with a virgin file if you have a working ecu you could clone.

I have attached both in my previous thread here.

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

I have tried to use hex editor to do the cloning. Whenever I write back to the eeprom with Argdub's tool, the write says ok, but the verification fails. When I read it again, the only change is at the beginning of the file that says no hardware. I played with Turboats tool, and made a file that matches my IMMO, VIN, SKC. Even made it into a 1KB file, though I am missing the hex that tells the tool it IS a 1KB file. it reads it as a 1kb file, expecting a 0.5kb file. Turboats tool can't read my file correctly. As I stated in my previous thread my files appear different than those I have seen here. Were there a bang head emoticon I would use it here!

But.. with cloning I mean you are going to put the original eeprom file on your new ecu! No need for hex editing anything. You are overcomplicating things. Whats the use of writing the data in another file that will then match one you already have?