Lkz666
Newbie
Karma: +0/-0
 Offline
Posts: 10
|
 |
« Reply #930 on: January 12, 2024, 10:41:51 PM »
|
|
|
I am trying to Immo-OFF my 2001 Audi TT ECU 8N0906018AT. I soldered a jumper on pin 24 of the flash chip to short to ground, power on, wait 6-7 seconds, remove jumper, now I am in Bootmode I think.
I have a KKL USB on COM 10 of my machine, and a bench ME7 harness
I can read out the 512 EEPROM bytes (95040) successfully.
Then I write a new file into the EEPROM.
C:\me7_95040_v1.31>me7_95040.exe --bootmode -wp10 off.bin
Ver: 1.31
Com Port: 10
Baud Rate: 10400
Opening COM10 ... OK
Starting Boot_mode ... uC identification response = 0xC5 (C167 derivatives) ... 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 ... 0x00F0 ... OK
Writing EEPROM ......OK
Closing COM10
It says it wrote to EEPROM, no errors.
But when I do a read and print to file or to the screen to verify, there are bytes in the last several lines of the file that DID NOT GET CHANGED in the EEPROM.
It seems that all 512 bytes in my file not writing to all 512 bytes in the EEPROM. Am I doing something wrong?
|
|
|
|
|
Logged
|
|
|
|
JeanAwt
Full Member
Karma: +10/-12
Offline
Posts: 242
|
|
« Reply #931 on: January 13, 2024, 06:38:03 AM »
|
|
|
I am trying to Immo-OFF my 2001 Audi TT ECU 8N0906018AT. I soldered a jumper on pin 24 of the flash chip to short to ground, power on, wait 6-7 seconds, remove jumper, now I am in Bootmode I think.
I have a KKL USB on COM 10 of my machine, and a bench ME7 harness
I can read out the 512 EEPROM bytes (95040) successfully.
Then I write a new file into the EEPROM.
C:\me7_95040_v1.31>me7_95040.exe --bootmode -wp10 off.bin
Ver: 1.31
Com Port: 10
Baud Rate: 10400
Opening COM10 ... OK
Starting Boot_mode ... uC identification response = 0xC5 (C167 derivatives) ... 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 ... 0x00F0 ... OK
Writing EEPROM ......OK
Closing COM10
It says it wrote to EEPROM, no errors.
But when I do a read and print to file or to the screen to verify, there are bytes in the last several lines of the file that DID NOT GET CHANGED in the EEPROM.
It seems that all 512 bytes in my file not writing to all 512 bytes in the EEPROM. Am I doing something wrong?
hello can you post your file here. I'll see if I can help |
|
|
|
|
Logged
|
A4 B5 avant 1.8T 2000 NO QUATTRO
|
|
|
Lkz666
Newbie
Karma: +0/-0
Offline
Posts: 10
|
|
« Reply #932 on: January 13, 2024, 08:35:45 PM »
|
|
|
Here is the file I'm trying to write to the EEPROM.
|
|
|
|
|
Logged
|
|
|
|
stuydub
Full Member
Karma: +25/-12
Offline
Posts: 230
|
|
« Reply #933 on: January 13, 2024, 11:18:33 PM »
|
|
|
Here is the file I'm trying to write to the EEPROM.
all good |
|
|
|
« Last Edit: January 13, 2024, 11:28:59 PM by stuydub »
|
Logged
|
|
|
|
Edbtz-A4
Newbie
Karma: +0/-0
Offline
Posts: 1
|
|
« Reply #934 on: April 08, 2024, 10:21:33 AM »
|
|
|
Struggling hard here...
Get the same result whether im using a VM machine with WinXP and a amazon kkl cable or win10 using a ross tech hex can1 with vcp drivers to create a com port. tried all the eproms, except one, keep getting "argument --in" message on eepromtool-0.4.
anyways, here's my script. any help would be immensely appreciated, been struggling for 3 weeks trying to get my skc code on my 2008 audi a4
C:\Users\Misha>C:\Users\Misha\Desktop\ME7EEPROM.exe --OBD -r -p 1 audi.bin
ME7_EEPROM v1.40
COM: 1, Baud Rate: 10400
Opening COM1 ... OK
Initiating communication ... FAIL. (error=0x21007)
Closing COM1
|
|
|
|
|
Logged
|
|
|
|
Schumo
Newbie
Karma: +2/-0
Offline
Posts: 18
|
|
« Reply #935 on: April 09, 2024, 03:01:28 AM »
|
|
|
Honestly, get a CH341 eeprom reader with a testclip and NeoProgrammer to read it and EepromTool to get the SKC. I sadly also never got ME7_Eeprom to connect.  |
|
|
|
|
Logged
|
|
|
|
ecuprog7
Full Member
Karma: +3/-0
Offline
Posts: 55
|
|
« Reply #936 on: April 09, 2024, 03:11:21 AM »
|
|
|
Hi, bootmode worked for me, try --bootmode instead of --obd and short bootpin on power on
|
|
|
|
|
Logged
|
|
|
|
Turbopower
Newbie
Karma: +0/-0
Offline
Posts: 2
|
|
« Reply #937 on: May 04, 2024, 09:37:49 AM »
|
|
|
Hello,
I was working with the tool at ME7 95040 and it worked fine. Thanks!
Now I tried at Bosch (Fiat, not VAG) EDC15C7 with 95P08.
When initiating communication it fails (error=0x21007) or with another cable (error=0x20201).
Is there a chance of reading the EEprom without desoldering?
Another question: Does someone know, where CS-error is written in the EEprom 95P08 HW 0281011755 SW 379274?
Thanks
|
|
|
|
|
Logged
|
|
|
|
Schumo
Newbie
Karma: +2/-0
Offline
Posts: 18
|
|
« Reply #938 on: May 04, 2024, 10:36:44 AM »
|
|
|
Is there a chance of reading the EEprom without desoldering?
CH341A Programmer + Clip + Neoprogrammer |
|
|
|
|
Logged
|
|
|
|
ecuprog7
Full Member
Karma: +3/-0
Offline
Posts: 55
|
|
« Reply #939 on: May 06, 2024, 01:56:38 AM »
|
|
|
@ Turbopower: are you working with bootmode? post a screen shot of call line and output
|
|
|
|
|
Logged
|
|
|
|
mrbarista
Newbie
Karma: +0/-0
Offline
Posts: 3
|
|
« Reply #940 on: May 15, 2024, 08:55:00 AM »
|
|
|
Hey,
I read my ME731 ecu and saved eeprom file with this tool. I'm editing hex file. I tried flash this file to eeprom but it didnt verify. Then i read eeprom and save the file again. It seems nothing changed in the eeprom.
I attached eeprom .bin file i read. I want to virginate my ECU.
|
|
|
|
|
Logged
|
|
|
|
unicorn89
Newbie
Karma: +0/-0
Offline
Posts: 18
|
|
« Reply #941 on: June 26, 2024, 01:37:36 PM »
|
|
|
I can never get this tool to work for me. Trying to get this to work on 05 New Beetle ME7.1.1 ECU. Command: ME7EEPROM.exe -p 3 --bootmode 95040 --read --CSpin P6.3 95160.bin ME7_EEPROM v1.40
COM: 3, Baud Rate: 10400
Memory type: 95040, size: 512
Chip Select pin: P6.3
Opening COM3 ... OK
Starting Boot_mode ... uC ID response 0x4A. Unknown ID. (error=0x40201)
Closing COM3 |
|
|
|
|
Logged
|
|
|
|
Artemisia
Full Member
Karma: +13/-0
Offline
Posts: 59
|
|
« Reply #942 on: June 26, 2024, 03:44:55 PM »
|
|
|
I can never get this tool to work for me. Trying to get this to work on 05 New Beetle ME7.1.1 ECU. Command: ME7EEPROM.exe -p 3 --bootmode 95040 --read --CSpin P6.3 95160.bin ME7_EEPROM v1.40
COM: 3, Baud Rate: 10400
Memory type: 95040, size: 512
Chip Select pin: P6.3
Opening COM3 ... OK
Starting Boot_mode ... uC ID response 0x4A. Unknown ID. (error=0x40201)
Closing COM3 It looks like you are trying to read a 95160 chipset but you specify --bootmode 95040 You can try the following: ME7EEPROM.exe -p 3 --bootmode 95160 --CSpin P6.3 -r 95160.bin You can try with a lower baud rate and by using P4.8 if it doesn't work with P6.3 |
|
|
|
|
Logged
|
|
|
|
dal
Full Member
Karma: +6/-7
Offline
Posts: 210
|
|
« Reply #943 on: August 13, 2024, 01:36:31 PM »
|
|
|
I can never get this tool to work for me. Trying to get this to work on 05 New Beetle ME7.1.1 ECU. Command: ME7EEPROM.exe -p 3 --bootmode 95040 --read --CSpin P6.3 95160.bin ME7_EEPROM v1.40
COM: 3, Baud Rate: 10400
Memory type: 95040, size: 512
Chip Select pin: P6.3
Opening COM3 ... OK
Starting Boot_mode ... uC ID response 0x4A. Unknown ID. (error=0x40201)
Closing COM3 This Beetle is 2.5 manual transmission? |
|
|
|
|
Logged
|
|
|
|
|
