|
turboat
|
 |
« Reply #30 on: October 23, 2014, 04:12:40 AM »
|
|
|
Ok, I think we can safely say that this doesnt work for S4 clusters! So far I've only tested it with mk4 platform clusters, but that s4 dump is totally different. I'll update it if I get time, but the varience between different eeproms is going to take a while to deal with.
|
|
|
|
|
Logged
|
|
|
|
byzan a4
Full Member
Karma: +0/-1
 Offline
Posts: 73
|
|
« Reply #31 on: October 23, 2014, 02:26:33 PM »
|
|
|
Ah ok. No worries. Bloody cars. I just want to stop the damn light flashing
|
|
|
|
|
Logged
|
|
|
|
|
turboat
|
|
« Reply #32 on: October 23, 2014, 03:02:49 PM »
|
|
|
I take it you've tried adapting the cluster and ecu with Vcds?
|
|
|
|
|
Logged
|
|
|
|
byzan a4
Full Member
Karma: +0/-1
Offline
Posts: 73
|
|
« Reply #33 on: October 24, 2014, 03:09:52 AM »
|
|
|
Yeah. I've changed to me. 7.5 and updated to later cluster all in one hit. So I don't have the old skc or anything as new dash is reported as immobiliser 3 in epromthingy despite it set on immo2
|
|
|
|
|
Logged
|
|
|
|
tpzd3fq
Newbie
Karma: +0/-0
Offline
Posts: 8
|
|
« Reply #34 on: November 11, 2014, 12:50:02 AM »
|
|
|
Awfully sorry for mine supidity : I mistake author of this great tool---you as ArgDub  download these two deffrent software several months and really tested quite a few times pardon me for my blindness  |
|
|
|
|
Logged
|
|
|
|
Allabout
Full Member
Karma: +0/-2
Offline
Posts: 54
|
|
« Reply #35 on: November 18, 2014, 03:13:55 AM »
|
|
|
Was playing with the IMMO off on my ECU bin file.
Now I'm only working from examples provided within this thread and the -h suffix command.
This is the error I received.
C:\ME7\eepromtool>eepromtool.exe --in IMMO_on.bin --immo off --out immooff.bin -
-status --fixcs
95040 Eeeprom Tool - 0.3 - No warranty implied or given, manually verify all cha
nges before saving eeprom to ECU, this tool could cause permenent damage to ECU
and prevent vehicle running
Read in 1048576bytes
WARNING: cannot decode VIN, try setting VIN to fix
WARNING: cannot decode ImmmoID
EEPROM Status:
- VIN:
- SKC: 062534
- Immobiliser: Error, set Immo
- Checksum: Invalid Checksum
Size: 1024kb - is this a flash bin not an eeprom bin?
Exiting
Traceback (most recent call last):
File "eepromtool.py", line 730, in <module>
File "eepromtool.py", line 675, in main
File "eepromtool.py", line 230, in printStatus
File "eepromtool.py", line 247, in getLength
NameError: global name 'exit' is not defined
C:\ME7\eepromtool>
I have checked both the ECU and cluter bin files. There is no VIN set anywhere?? Only displays as XXXXXXXXXXXX
I now also understand why I was struggling to decode the ECU bin for the SKC. As that is the number I kept coming up with.
The cluster bin reveals completely different skc.
So any suggestions or recommendations?
I tried using the 95040tool first with no success at all.
Here is the results of the 95040 tool.
C:\ME7\95040tool>95040tool.exe --in immo.bin --out immooff.bin --immo IMMO --fi
xcs
95040 Eeeprom Tool - 0.1 - No warranty implied or given, manually verify all cha
nges before saving eeprom to ECU, this tool could cause permenent damage to ECU
and prevent vehicle running
WARNING: cannot decode VIN, try setting VIN to fix
WARNING: cannot decode ImmmoID
- Setting backup pages
- Correcting checksums
Warning: Error correcting checksum, checksums in output file may be invalid
Writing eeprom bin to: immooff.bin
- Write Successful
C:\ME7\95040tool>ME7Check.exe immooff.bin
==============================================================================
ME7Check v1.12 (c) mki, 06/2004-05/2012
Checking file immooff.bin (size=1048576)
Reading Version Strings...
-> Bootrom Version = F0.61 (UNKNOWN)!! ** NOT OK **
-> EPK = 42/1/ME7.̵5/6001.01//X22.Ú/Dstt2t/260599¸þ
-> Contents of ECUID data table:
-> ECUID data table not found ** NOT OK **
-> file not recognized as ME7, stopping analysis
C:\ME7\95040tool>
|
|
|
|
|
Logged
|
|
|
|
|
turboat
|
|
« Reply #36 on: November 18, 2014, 04:07:54 AM »
|
|
|
Theres a few things wrong here, first up you are confusing eeprom and flash in the ECU, eeprom is where the immo settings, adaptation, SKC, etc are stored. Flash is where your maps are stored - and you use me7check for the flash, not the eeprom, hence that would report the errors. Secondly,eepromtool reported the file size as '1048576bytes', which makes me think that you are looking at a 1MB flash bin, not a 512B eeprom bin. Did you read this bin using nefmoto? If so, go and read the bin from your ECU using argdubs tool |
|
|
|
|
Logged
|
|
|
|
Allabout
Full Member
Karma: +0/-2
Offline
Posts: 54
|
|
« Reply #37 on: November 18, 2014, 01:01:27 PM »
|
|
|
Theres a few things wrong here, first up you are confusing eeprom and flash in the ECU, eeprom is where the immo settings, adaptation, SKC, etc are stored. Flash is where your maps are stored - and you use me7check for the flash, not the eeprom, hence that would report the errors. Secondly,eepromtool reported the file size as '1048576bytes', which makes me think that you are looking at a 1MB flash bin, not a 512B eeprom bin. Did you read this bin using nefmoto? If so, go and read the bin from your ECU using argdubs tool yes it was a nefmoto bin read. ok well that makes sense, thanks which tool of argdubs are you refering to? this one perhaps - http://nefariousmotorsports.com/forum/index.php?topic=1168.0title= ? |
|
|
|
« Last Edit: November 18, 2014, 01:03:02 PM by Allabout »
|
Logged
|
|
|
|
|
turboat
|
|
« Reply #38 on: November 18, 2014, 01:54:41 PM »
|
|
|
Yeh that one, commonly refered to as 'argdubs tool'
|
|
|
|
|
Logged
|
|
|
|
spawn2death
Newbie
Karma: +0/-0
Offline
Posts: 3
|
|
« Reply #39 on: December 21, 2014, 05:30:07 AM »
|
|
|
Hi. I read eeproom with me7_95040 in boot mode (version 1.31 in not boot mode does not work).
C:\Temp\eepromtool>eepromtool --in eeprom_2.bin
95040 Eeeprom Tool - 0.3 - No warranty implied or given, manually verify all cha
nges before saving eeprom to ECU, this tool could cause permenent damage to ECU
and prevent vehicle running
Read in 512bytes
EEPROM Status:
- VIN: XXXXXXXXXXXXXXXXX
- SKC: 065535
- Immobiliser: On
- Checksum: Invalid Checksum
- Size: 512bytes
- Cluster Code: 00 00 00 00 00 00 00
- P0601 DTC: not set
- Immo ID: XXXXXXXXXXXXXX
- Softcoding ID: 5712
ECU 4b0907551f
I want replace my magnetti marelli panel with vdo and off immobilizer. I fear do it this with eepromtool. Invalid checksum and xxxxxxxxx vin.
|
|
|
|
|
Logged
|
|
|
|
spawn2death
Newbie
Karma: +0/-0
Offline
Posts: 3
|
|
« Reply #40 on: December 21, 2014, 11:22:27 AM »
|
|
|
I cross my fingers and off immo with eepromtool and write it. All is fine Thank you for this great tool. |
|
|
|
|
Logged
|
|
|
|
aRd
Newbie
Karma: +1/-1
Offline
Posts: 13
|
|
« Reply #41 on: December 24, 2014, 06:18:40 AM »
|
|
|
Hi turboat
as discussed, attached is an ecu and cluster file.
|
|
|
|
|
Logged
|
|
|
|
aRd
Newbie
Karma: +1/-1
Offline
Posts: 13
|
|
« Reply #42 on: December 24, 2014, 06:22:42 AM »
|
|
|
hi
attached is copy of the cluster and ecu I would like the data out of the cluster to be copied into the ECU
Thank you
|
|
|
|
|
Logged
|
|
|
|
aRd
Newbie
Karma: +1/-1
Offline
Posts: 13
|
|
« Reply #43 on: December 24, 2014, 06:23:38 AM »
|
|
|
ECU file
|
|
|
|
|
Logged
|
|
|
|
tabster
Newbie
Karma: +1/-0
Offline
Posts: 15
|
|
« Reply #44 on: December 26, 2014, 03:49:55 PM »
|
|
|
hi
attached is copy of the cluster and ecu I would like the data out of the cluster to be copied into the ECU
Thank you
Ray, check your email and you will find updated ECU eeprom, with cluster immo data inside |
|
|
|
|
Logged
|
|
|
|
|
