Keith-the eeprom I'm referring to isn't the main flash (29f800bb), but rather the 95040 that stores immobilizer data/adaptations/skc. Having the contents of the 95040 as well as the cluster dump would help me identify where the skc is stored in the cluster, and how it interacts with the rest of the systems.

The file I'm looking for (off the ecu) is 512 BYTES in size (very, very small). It is stored on a small SOIC-8 chip on the ecu (labeled 950403, on me7.5 it's on the bottom of the board, me7.1 the top).

Hmm-it's commonplace for tuners to (for lack of a better word) "tag" the 95040, altering it's contents (even nefmoto does this) but I honestly can't see any of them doing something as irresponsible as erasing the immobilizer data. It's always a good idea to back up the eeprom prior to tuning just in case. When you get it back read it off, the procedure is outlined in argdub's thread (linked here).

Your assumption is correct, I'm looking for some insight into the relationship between the ecu and the cluster. A matching set would make life MUCH easier

That's the thing. Galletto, nefmoto, etc-all they do is copy the main flash eprom, not the 95040. That's your responsibility to make a backup of (It's not really made that clear). The poor me7.1.1 guys end up with cars that won't start all the time after flashing.

All you need to know is attached young grasshopper.

 

Virgin eeprom dump attached. Writing this to the eeprom will allow you to complete adaptation of the immobilizer as though the ecu were new from the dealer.

My experience has been removing the ecu from the car, defeating the immobilizer, flashing it, and re-installing it is usually the best way to avoid drama. My 2001, and 2002 are both VERY finicky about flashing in the car-sometimes taking 5-6 minutes to complete a flash, failing multiple sectors, restarts, etc. On the bench, They flash in a consistent 3:00 without fail.

If you want to keep your immobilizer active (keep in mind this is only possible if you are using a flash from an immobilizer equipped car-flashing an m or l-box bin will bypass all immobilizer functions), my advice is to back up the 95040, defeat the immobilizer, flash it, then restore the original 95040 (or use the virgin dump I've attached 2 posts down and complete adaptation as though it were a new ecu).

Backing up the eeprom prior to flashing, then restoring it also has the added benefit of not having it tagged with "nefmto" (not that it matters, but I don't like anything modifying an immo-equipped 95040 for many reasons)

I really hope Tony returns (more than that, I hope he's ok) and approves a subforum for immobilizer/cluster posts. I think with all the questions, it would be beneficial.

UPDATE:

I ran into something earlier today I thought I'd share. If it happened to me, it could happen to you.
Allroad owners(and BEL a6 owners as well), pay attention.

Prerequisites:

You've read this thread and understand how to pull your eeprom data.
You have a hex editor

The immo-off files in this thread won't work on the me7.1.1 allroads. If you flash one, you'll get a
p1640, EEPROM error. The only option here is to off your own file. You need to get out your trusty hex
editor, and browse to locations 12 and 22. The values in these locations will be 01, indicating an
active immobilizer. Change these to 02, and you have off'd your file. Chances are you're doing this on a used ecu, now is the time to correct the vin if you'd like. It's location in the eeprom dump is obvious. When you've finished modifying the file, correct the checksums (for simplicity's sake I have attached the tool to do so. Big thanks to the creator, and 360trev for re-writing it.) Flash the off'd file, and you're good to go.

This next part is for those of you that have either:

A: Had APR flash your ecu and turn it into a brick
B: Flashed a file with a bad checksum

If either of the above has occurred chances are you have ended up with p0601, memory checksum error,
and been unable to clear it. No amount of flashing in the world will solve this, the code is stored in
the eeprom, not the main flash. Pull the eeprom bin, and whip out your trusty hex editor. Browse to
offset 1c.



If you have the previously mentioned DTC chances are the value stored in this location (and
right below it in 2c) will be 01, or 33. You need to change these values back to 00 to clear this code.
Afterwards, correct your checksums and flash your fixed file back to the ecu. p0601 will be gone.

Usage instructions for 95040sum:

1. Save the exe into your user directory (C:\Documents and Settings\usernamehere)
2. Place your eeprom bin into the same folder
3. Open up a CMD line, and type: 95040sum (name of your eeprom).bin (desired name of corrected file).bin
4. Click enter

Example:

95040sum eeprom.bin fixed.bin

The checksum corrector, and an IMMO off'd bin compatible with ME7.1.1 is attached.

Big thanks to K0mpresd for allowing me to bounce Idea's off of him throughout this. Appreciate it.