|
Title: EEPROM TOOL Post by: 2002MK4GTI on March 15, 2023, 02:00:10 PM Howdy, I've successfully used the EEPROM tool on many other of my ECUs, and never come across this issue before, but have never attempted to use it on a 400BB ECU, so I'm assuming something different must be done for them. What is it that I am missing? I've scoured the forum like I usually do, but I just couldn't find the answer this time. The error I am getting is WARNING: cannot decode ImmmoID. It previously said the same about the VIN, but I set the VIN and no longer have the error. The ECU is from a 2000 TT 1.8 180hp if it makes any difference. To the best of my knowledge, the car did not even have an immobilizer from the factory but throws a code for the immobilizer, and the immo light flashes if ECU is put in a car that came factory with an immobilizer. Below is what I have in CMD. Pardon the goofy file path. Thanks in advance for any words of wisdom.
C:\Users\cheab\OneDrive\Desktop\Tuning\Immobilizer>eepromtool_04.exe --in 95040.bin --immo off --out 95040.bin Read in 512bytes WARNING: cannot decode ImmmoID Setting Immobiliser: Off - Immobiliser already set Off C:\Users\cheab\OneDrive\Desktop\Tuning\Immobilizer>ME7EEPROM --bootmode 95040 --CSpin P6.3 -w 95040.bin -p 6 -b19200 ME7_EEPROM v1.40 COM: 6, Baud Rate: 19200 Memory type: 95040, size: 512 Chip Select pin: P6.3 Opening COM6 ... OK Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK Sending Loader + MonitorCore ... MonitorCore successfully launched Initializing registers ... OK Sending EEPROM driver ... OK Configuring SPI Interface ... OK Checking EEPROM Status Register ... 0x00FF Writing EEPROM OK Closing COM6 Title: Re: EEPROM TOOL Post by: 2002MK4GTI on March 15, 2023, 02:42:29 PM Another look at cmd.
C:\Users\cheab\OneDrive\Desktop\Tuning\Immobilizer>eepromtool_04.exe --in 95040.bin Read in 512bytes WARNING: cannot decode VIN, try setting VIN to fix WARNING: cannot decode ImmmoID EEPROM Status: - Type: ECU_eeprom - Version: Immo3 - VIN: - SKC: 065535 - Immobiliser: Error, set Immo - Current values: 0x12 = 0xFF, 0x22 = 0xFF - Checksum: Invalid Checksum - Size: 512bytes - Cluster Code: FF FF FF FF FF FF FF - P0601 DTC: set to FF FF - Immo ID: - Softcoding ID: 65535 - Tuner Tag: Not Set - Flash Programming (successful): 255 - Flash Programming (attempts): 255 Title: UPDATE Post by: 2002MK4GTI on March 15, 2023, 03:12:00 PM I found a solution without necessarily solving the problem. I took a known good .bin from another of my ECUs which is an 800BB and flashed it to the problematic ECU. There do not appear to be any issues yet, and the car starts as it should now. Hopefully, this helps someone that needs a quick fix. If anyone does know how to properly solve the problem, all knowledge is appreciated.
Title: Re: EEPROM TOOL Post by: royce5950 on March 20, 2023, 02:59:02 AM My guess is even if the car didn’t come with immo from the factory, that doesn’t mean that the instrument cluster wouldn’t have the ability to detect whether or not the ECU has an activated immo. Interesting find if that’s the case on your TT. Also there are different versions of argdubs tool. I think that’s who developed it I forgot.
Title: Re: EEPROM TOOL Post by: 2002MK4GTI on April 09, 2023, 06:00:39 PM What other versions of the tool are there? I recall seeing a UI version a long time ago but have been unable to find it again since. Is there a version specifically for 400BB ECUs? It's an incredibly useful tool and I'd love to be aware of all available versions.
|