Pages: [1]
Author Topic: EEPROM/Immobilizer issues  (Read 2478 times)
ImNOTsmart
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 3


« on: December 27, 2020, 01:41:04 PM »

Hey all,
I'm attempting to delete the immobilizer from my mk4 Jetta ECU (06A 906 032 HS) for a mk2 golf swap. I had no trouble reading the EEPROM through OBD and editing it so the immobilizer was off. I checked this by rereading the new file (002.bin) I created. I then wrote the new file to the ECU as follows.

C:\Users\aaron\Downloads\vw>ME7 --bootmode 95040 -w -p3 002.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
Closing COM3

This seems to have worked fine and all seemed well until I tried to read the EEPROM through OBD off the ecu after rebooting. It connected but failed to read.

C:\Users\aaron\Downloads\vw>ME7 -r -p3 --OBD check.bin
ME7_EEPROM v1.40
COM: 3, Baud Rate: 10400
Opening COM3 ... OK
Initiating communication ... OK
ECU ID response: 06A906032HS
                 1.8L R4/5VT     G
                 0007
                 SoftCod: 07500, WSC: 00066
Reading EEPROM ...FAIL. (error=0x21007)
Closing COM3

Any advice is welcome. I have a feeling I may have selected the incorrect memory type as I wasn't sure which one to pick. I decided against trying to write it again before I have some other input. Am I missing something obvious like a command error? Thanks in advance. (note: I renamed the EEPROM writing tool)
Logged
ImNOTsmart
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 3


« Reply #1 on: December 27, 2020, 02:07:48 PM »

Also to note I have been having some driver issues as well. The EEPROM programs did not work with the FTDI drivers from the guide but windows automatically installed drivers which stopped the com port errors. Is the driver issue an issue with the blue KKL cable I'm using?
Logged
adam-
Hero Member
*****

Karma: +124/-33
Offline Offline

Posts: 2179


« Reply #2 on: December 27, 2020, 03:50:08 PM »

Read it in bootmode.
Logged
ImNOTsmart
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 3


« Reply #3 on: December 28, 2020, 02:39:48 PM »

Well shit. I tried to read in boot mode but got an error saying no ECU response, then tried OBD again and now it can't even initiate communication. I may have bricked it.
Logged
tao13
Sr. Member
****

Karma: +17/-47
Offline Offline

Posts: 471


« Reply #4 on: December 30, 2020, 10:36:03 AM »

Do you make the checksum for new eeprom file?
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.014 seconds with 16 queries. (Pretty URLs adds 0s, 0q)