NefMoto

If you brick your cluster and get a DEF error, the only way to repair it, short of super expensive tools is to desolder and write an original encrypted read back into the eeprom. The backup you made (you DID backup your old file right?) via OBD will not work as it's been decrypted by the cluster by the time you get it.

It must be written as 8bit.

This one is good for 03-05. I'll post 01-02 later.

I'm just going to thank you in advance for this one....

I'm going to thank dd retroactively on this one :)

It sucks hat it happened, but at the same time it was an opportunity to learn something new that not many people know (and the ones that do shroud it in secrecy). Glad the cluster's fixed :P

DD do you test the VAG Eeprommer on bench or OBD with those clusters?

I did, and it works well, but once you've bricked it you can't write the cluster without desoldering.

Hello, Mr ddillenger.

I have similar problem with bricked dash, after some bastard tried to capture my car :-/
My Allroad 2.7T AT is 2001, so would You post such file to fix a problem?

Thank You!
Sebastian

Do you have a DEF error? Give me some details, I will get you sorted.

Hi,

Were you able to get this to work?  I think they compare the 93C86 EEPROM with an internal EEPROM in the Micronas CPU. I can take the 93C86 EEPROM from a cluster that is working properly and install it into the one with the DEF fault.  New mileage appears as according to the EEPROM I just transplanted, but the DEF fault is still there.  So there must be a comparison taking place with an internal EEPROM of the CPU.  When I take that EEPROM back off and install into the good cluster, everything is okay again.

Also, did you happen to get the 01-02?  My cluster is an '02 and will try it and report back.

Yes, must have the same bitmask to work. I have 02, just need to know your cluster info so I can get you what you need!

I´ve bricked my cluster last weekend and have tryed to restore it with your file using an EZP2010 Flasher.

The problem i got is, everytime i want to write the file i got a write error using the Atmel 93c86 8 or 16 bit chip specs. Using the Fairchild 93c86 dosent get an error message, but the cluster is dead anyway :(

Do you have any ideas or can you tell me how to flash the file to the eeprom?

Thank you.

ddillenger,

I am not sure if you even have to desolder it. I was able to successfully read cluster from 2001-2003 Jetta and 2005-2006 TDIs using elnec bench eeprom programmer. What I used was a 8-pin clip that attaches on the top of the chip and the other end plugged into programmers ISP port.  I am pretty sure the programmer read bit by bit directly from the chip.

So you are saying that if you use software (such as VAG K+CAN), the output read from the eeprom is decoded first and then sent out? Are you positive about this?

These are the files from 2001-2003 gasoline (I am not sure which one, just picked up a cluster on a junkyard) - 93C86 and 2006 TDI 24C32.

Both read using ISP port on ELNEC programmer. Power was provided by the programmer.

*** Note: 2006JY is from a 2006 TDI vehicle!

elnec programmers do it for sure. I have erased with 0xFF, then restored original, and tried reading it again and all functions work correctly. I am not sure what chip setup I used, I can check when I get home and let you know..I think it was atmel as well.

When you finish flashing the eeprom make sure you can read from it, and the make sure the result is not all FF or all 00.

Hello hytron,

Thanks for your help. I cant fix my problem.

I will write it as detailed as i can.

I can write your 01-03 file via EZP2010 Programmer with choosen Chip: Atmel93c86 16Bit(!) SOP8
I can read it out after programming it and it will show me the same file as the one you posted, so i think writing the chip is ok.

Then i put the cluster in the car:

No lights working ( I can Read Clock and Date and in the milage field FUSE  if i put a lamp on it )
I Can go through it via VAG Com ( Part Number is wrong and un readable, but i can start the output tests Analog outputs are NOT working, everything else is fine )
I Cant read or write it via VAG Dash Com
I CAN read it via K+Can commander ( the file i can read out isn´t the file i wrote to it via EZP2010 its just like .t.m.t.m.t.m and so on. )
If i want to write another file on it via K+Can he wrotes, but the cluster did not save it to the rom, no changes to before.
The FIS Display blinks the whole time ( it starts very bright and then fades out to dark, that repeats the whole time )
The Beeps for runing out of Gas light or low Batterie arent as loud as they normaly are.

Any ideas?

I have noticed that every time you turn ignition on and off, content of the eeprom changes...but only a few bits...I assume that is normal (talking about my 2006 TDI). I have also tried using VAG K+CAN and you cannot write a bin file into the cluster and expect it to work. Recently I have discovered that EEPROM is the one storing the mileage and VAG K+CAN will not restore it the right way. EEPROM programmer will do the job. I am not sure what the guys who wrote the software for VAG K+CAN were thinking...Made in China??? Not sure.

Make sure the cluster is off and not powered when you are restoring it. Also there are different clusters with different firmware versions which will not work if you use different eeprom content. For example I have two clusters from 2006 Jetta TDI and one is multifunction and the other is not...swapping content of eeproms makes clusters unusable, so the only way is to use the correct versions.

Remember while software errors are mostly the cause of problems, there could be also other components that have failed in your cluster.

Tried it one more time today.

In my cluster from a 2003 ( i think ) A6 there is a Fairchild 93C86 inside. I can only Read or Write it in 16Bit mode ( FM93C86AM8 or FM93C86AN ) as selected chip. These are the same chips i think, the only difference is the typ SO or DIP.

Tried one more time to write DD´s image to the chip. I opend it in ECP2010 Tool and im not able to read a FIN or a Part number out of the selected File. Is this correct? With every other file opend im able to read a Part number or FIN in the lower Part of the file.

@hytron

Thanks for your help. Everytime i do changes on the chip i desolder it from the cluster so writing the chip while ignition is turned on is not possible for me.

Got a solution for my problem last week:

Throw it in the trash and buyed a new one :D

Problem solved!

i have restored 4 speedos at this moment. with FUSE in display... there is 9 versions of crypto files and speedo must have the same version. if someone have crypto files to this clocks we can share them and try to solve our problems.

I am getting FUSE message as well....does that mean bad write was put on cluster...I swapped EPROMS between Gauge Clusters.