Ok this is my first time playing with ECU. i am using k+can commander 1.4 with FT232RQ
ECU is "4B0 906 018 CG" 1.8T AWT, on a bench
I am using this CMD program and reading EEPROM was successful, then i open it with hex editor and change this immo values to 02
Put ECU in boot mode and try to upload new eeprom data
The program shows that upload is succsessful, but it can not read EEPROM data
C:\Documents and Settings\XXXX>C:\tuning\ME7EEPROM --bootmode 95040 -wp3 95040.bin
ME7_EEPROM v1.40
COM: 3, Baud Rate: 10400
Memory type: 95040, size: 512
Opening COM3 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... OK
Sending EEPROM driver ... OK
Searching Chip_Select pin ... P4.7
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00F0
Writing EEPROM ................................ OK
Verifying EEPROM write ... FAIL. (error=0x70101)
Closing COM3
after thet i put ECU in OBD mode, and it connect to ECU but cant read EEPROM...
So i tried to upload original .bin file and got same error
C:\Documents and Settings\XXXX>C:\tuning\ME7EEPROM --bootmode 95040 -wp3 95040.bin
ME7_EEPROM v1.40
COM: 3, Baud Rate: 10400
Memory type: 95040, size: 512
Opening COM3 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... OK
Sending EEPROM driver ... OK
Searching Chip_Select pin ... P4.7
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00F0
Writing EEPROM ................................ OK
Verifying EEPROM write ... FAIL. (error=0x70101)
Closing COM3
But, the difference is after I put ECU in OBD mode i can read EEPROM successfully.
What I am missing?
In attachment the 95040.bin is original file and other id immo off