|
turboat
|
 |
« Reply #120 on: October 03, 2018, 12:09:50 PM »
|
|
|
EEpromtool is now hosted on github. Please pull it down, test and let me know if there are any issues.
If anyone has feedback or improvements to suggest, that would be super useful. I would like to improve the handling of immo2 bins, and it would be good to document what it does/does not do. Also if anyone has information on cluster checksums, that would be good to add.
|
|
|
|
|
Logged
|
|
|
|
Risky
Full Member
Karma: +4/-0
 Offline
Posts: 107
|
|
« Reply #121 on: October 03, 2018, 04:21:44 PM »
|
|
|
Worked for me  Thanks! |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #122 on: October 03, 2018, 09:43:49 PM »
|
|
|
Thank you!
|
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
kutscher
Newbie
Karma: +0/-0
Offline
Posts: 2
|
|
« Reply #123 on: October 29, 2018, 09:55:19 AM »
|
|
|
Thanks, great work turbat
Can confirm that eepromtool can immo off a ME 7.1.1, Golf 5, R32, 022906032CD, with 95160 eeprom.
Read in 2048bytes
Setting Immobiliser: Off
- Immobiliser Off
- Setting backup pages
- Correcting checksums
- Write Successful
Read in 2048bytes
EEPROM Status:
- Type: ECU_eeprom
- Version: Immo2
- VIN: WVWZZZ1KZ6W0..... (VW 2006 - Golf and Jetta 5, 6, Wolfsburg, Germany)
- SKC: 06520
- Immobiliser: Error, set Immo - Current values: 0x12 = 0x04, 0x22 = 0x04
- Checksum: Invalid Checksum
- Size: 2048bytes - 512bytes expected, check this is a eeprom bin
- Cluster Code: 87 9E 5D 0B EA F2 5F
- P0601 DTC: not set
- Immo ID: VWZ7Z0E27.....
- Softcoding ID: 0132
- Tuner Tag: Not Set
- Flash Programming (successful): 4
- Flash Programming (attempts): 149
|
|
|
|
|
Logged
|
|
|
|
|
turboat
|
|
« Reply #124 on: October 29, 2018, 04:04:21 PM »
|
|
|
Did you write it back onto the ecu and check that it's working OK? I've never tested it on a mk5 r32 and it doesn't look like it's parsed it properly based on that output. Please can you post the bin?
|
|
|
|
|
Logged
|
|
|
|
kutscher
Newbie
Karma: +0/-0
Offline
Posts: 2
|
|
« Reply #125 on: November 04, 2018, 06:39:45 AM »
|
|
|
Yes, the car is running. Although parsing was not perfect. Bins say more than 1000 words |
|
|
|
|
Logged
|
|
|
|
|
turboat
|
|
« Reply #126 on: November 04, 2018, 12:53:40 PM »
|
|
|
OK that's great, glad it's running. I'll try and improve the parsing, thanks for the bins.
|
|
|
|
|
Logged
|
|
|
|
|
bamofo
|
|
« Reply #127 on: November 15, 2018, 09:48:03 AM »
|
|
|
Fixed nm.
|
|
|
|
« Last Edit: November 15, 2018, 09:49:44 AM by bamofo »
|
Logged
|
|
|
|
dal
Full Member
Karma: +6/-7
Offline
Posts: 210
|
|
« Reply #128 on: November 26, 2018, 05:43:34 AM »
|
|
|
Hi turboat!
First thanks for this great tool. Been using a lot for some testings here.
There is one thing that I didnt manage to do yet.
Last year I converted my car to wideband ECU (from ME7.5.1 032S to ME7.5.5 032LP with HP flash). Been running perfect since then.
The only problem is that I never managed to make the IMMO work again. Today I ran with an immo off EEPROM on ECU, but I have the wish to fix this, and put the IMMO back on.
Do you know what I can do, using your tool?
I dont if helps, but I attached the cluster bin and an printscreen of the VAGeepromprogrammer screen.
|
|
|
|
« Last Edit: November 26, 2018, 06:02:09 AM by andredalmolin »
|
Logged
|
|
|
|
Turbopower
Newbie
Karma: +0/-0
Offline
Posts: 2
|
|
« Reply #129 on: December 31, 2018, 06:48:53 AM »
|
|
|
Hello, this is my first post with several questions to the EEprom. Sorry for my bad english.
I have an A3 8L year 2003 with AUM-engine and a strange history.
The car was running, no lights in the dash, cruise-control was working.
Then the OE-ECU was killed by flashing a file without proving the CS.
As my skills in soldering are not good, I gave the ECU to a recommended company to reset it to the old condition. They damaged the ECU physically. I bought another identical ECU 06A9066032HJ. They desoldered the EEprom and soldered it into the other used ECU.
The EEprom-dump I have is from this situation.
The result was, that the car started for 1 second and stopped.
Then immo3 was set off and the car was running. At first the rev-counter was dead and I could see communication-probs between ECU, powertrain and dash. The can-bus and the ABS-ECU got checked and a new dash with the old EErom-dump was mounted. Now the dash works, but the communication-probs stayed, ABS-light is on and the car is only running with Immo-off.
Now I tried to solve it by myself even if I didn’t work with Immo3 before.
I read the EEprom from ECU by bootmode without soldering – thanks to your great tool!!!
The EEprom of the dash I read too. After quite a while of research I could see, that VIN, Immo-ID, cluster-code and login-code are correct matching.
Based to this here are my specific questions:
1. Quite simple: is the login-code (used in VCDS) the same as SKC? If not, where do I find the SKC in ECU and dash?
2. What is the meaning of the bytes 014H and 015H in the 95040 ECU-EEprom and does it has to match in the dash-EEprom?
3. What is happening in the page 110H?
4. What is written in the page 140H?
5. Can you see something generally wrong in the dumps of ECU or dash (1st after crash, 2nd with Immo-off, changed after running and 3rd dash)?
Thanks!
|
|
|
|
|
Logged
|
|
|
|
nxm08240
Newbie
Karma: +0/-0
Offline
Posts: 5
|
|
« Reply #130 on: January 09, 2019, 09:54:19 AM »
|
|
|
Trying to turn immo off on this car and I get this when I read the EEPROM over OBD
Read in 512bytes
EEPROM Status:
- Type: ECU_eeprom
- Version: Immo3
- VIN: XXXXXXXXXXXXXXXXX
- SKC: 065535
- Immobiliser: Error, set Immo - Current values: 0x12 = 0x04, 0x22 = 0x04
- Checksum: OK
- Size: 512bytes
- Cluster Code: 00 00 00 00 00 00 00
- P0601 DTC: not set
- Immo ID: XXXXXXXXXXXXXX
- Softcoding ID: 16201
- Tuner Tag:
- Flash Programming (successful): 0
- Flash Programming (attempts): 0
|
|
|
|
|
Logged
|
|
|
|
nxm08240
Newbie
Karma: +0/-0
Offline
Posts: 5
|
|
« Reply #131 on: January 10, 2019, 09:15:33 AM »
|
|
|
I got the last ECU sorted. I have an ECU from an AMB and I keep getting this error when trying to read in bootmode. I got it to read a couple of times with cspin6.3 but it did not read correctly. Any ideas?
ME7_EEPROM v1.40
COM: 1, Baud Rate: 10400
Memory type: 95040, size: 512
Opening COM1 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... FAIL. (error=0x40E01)
Closing COM1
Edit: Needed 57600 baud...
|
|
|
|
« Last Edit: January 11, 2019, 05:36:32 PM by nxm08240 »
|
Logged
|
|
|
|
TTRPh
Newbie
Karma: +0/-0
Offline
Posts: 1
|
|
« Reply #132 on: January 18, 2019, 02:12:50 PM »
|
|
|
Hi! All! Newb here, and I've tried to read all the threads in the last few days but didn't come across the right answer
Problem: I have a 2000 audi tt 1.8T ATC that has a tune from a remote tuner. I have been unable to get a pin using ME7 EEPROM programmer with either v1.31 or v1.40. I wanted to duplicate the 95040.bin onto a spare ECU to run different injectors and have a spare for safety. For the spare I have the matching cluster, and I believe they are from a 2005 Audi TT quattro. The only difference in the ECUs is that original has a C and the the spare has S at the end.
I have been able to pull the pin from that ECU with v1.31, by using the --screen command and copying that into a Hex Editor Neo, but unable to do the adaptation to use the key that I have. The pin allows me to log into some controllers but not into instruments and not into immobilizer. It usually times out in each attempt, and the car starts for a second and turns off.
When I try using original, I get the No response from the ECU error.
What seems to be a solution is to pull the 95040.bin from original ECU to write onto spare. Alternatively, write a virgin file to spare.
Questions:
1. Can this EepromTool pull my original ECU SKC?
2. Does the remote tuning software interfere with the process?
3. I've been confusing the terms bootmode vs benchtop in the forum and it makes it difficult to figure out what I need for the writing process onto 95040 chip.
--Do I need a benchtop set up to write in bootmode?
--What way is the appropriate way to ground pin 21, ie. can that be done when the ECU is on the car, and then using bootmode on the car?
--Do I need to de-solder the chip and use a USB-eeprom burner?
Thanks in advance.
|
|
|
|
|
Logged
|
|
|
|
B5Quattrolife
Jr. Member
Karma: +2/-0
Offline
Posts: 27
|
|
« Reply #133 on: January 22, 2019, 07:27:17 AM »
|
|
|
I got the last ECU sorted. I have an ECU from an AMB and I keep getting this error when trying to read in bootmode. I got it to read a couple of times with cspin6.3 but it did not read correctly. Any ideas?
ME7_EEPROM v1.40
COM: 1, Baud Rate: 10400
Memory type: 95040, size: 512
Opening COM1 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... FAIL. (error=0x40E01)
Closing COM1
Edit: Needed 57600 baud...
im getting the same issue, mind copying your screen? |
|
|
|
|
Logged
|
|
|
|
B5Quattrolife
Jr. Member
Karma: +2/-0
Offline
Posts: 27
|
|
« Reply #134 on: January 22, 2019, 07:55:24 AM »
|
|
|
im getting the same issue, mind copying your screen?
Also this is what im looking at if anyone has any insight C:\Users\Owner>C:\Users\Owner\Desktop\ME7-Bin-Def's-Tools\ME7EEPROM.exe --bootmode 95040 -r -p 1 95040.bin ME7_EEPROM v1.40 COM: 1, Baud Rate: 10400 Memory type: 95040, size: 512 Opening COM1 ... OK Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK Sending Loader + MonitorCore ... MonitorCore successfully launched Initializing registers ... OK Sending EEPROM driver ... FAIL. (error=0x40801) Closing COM1 |
|
|
|
|
Logged
|
|
|
|
|
