2002MK4GTI
Newbie
Karma: +0/-0
 Offline
Posts: 12
|
 |
« 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
|
|
|
|
|
Logged
|
|
