alexrae
Jr. Member
Karma: +0/-0
 Offline
Posts: 32
|
 |
« Reply #435 on: October 14, 2014, 04:50:37 PM »
|
|
|
finally tried my ecu (A8 2000) with immo off - works as suppose to  () Just to be consistent with VINS decided to map cluster to the ECU (it was my initial need - new cluster was with all working displays - and I swap everything before - cluster/ECU and immo chips). Turns out - I cannot link cluster with matched immo chips, had to swap immo chips first, then link cluster to the ECU (not sure - maybe it will work with virgin immo chips)... 1 side effect from such mapping - it shows additionally old VIN number in cluster general info page in vag com... Luckily this panel not encrypted, will try to modify all vins there directly when have a time |
|
|
|
|
Logged
|
|
|
|
redtop
Jr. Member
Karma: +5/-0
Offline
Posts: 44
|
|
« Reply #436 on: October 15, 2014, 10:29:16 AM »
|
|
|
I think so as well... Can it be related to manual configuration for CSpin and some bug in program if it try to autodetect it for validation? Today pouring rain - cannot check everything on the car... Will update as soon as verify
Just tried to read directly after write with the --reconnect parameter, and it works, so it's possible to read without rebooting the ECU. If ArgDub could have a look at it and see if there is a bug, that would be great! |
|
|
|
|
Logged
|
|
|
|
TijnCU
Hero Member
Karma: +60/-4
Offline
Posts: 690
flying brick
|
|
« Reply #437 on: October 21, 2014, 11:36:37 AM »
|
|
|
I have a very hard time getting this tool to work with my 4B0906018AA ECU, finally I managed to write my immo off bin to the EEPROM, but it failed to check? Can I consider the file to be done or should I keep trying to read it again? Would feel best to verify... NVM, managed to pull the bin after a few more try's. 100% identical   yeah |
|
|
|
« Last Edit: October 21, 2014, 11:47:30 AM by TijnCU »
|
Logged
|
|
|
|
|
aef
|
|
« Reply #438 on: October 21, 2014, 11:51:56 AM »
|
|
|
Had the same problem minutes ago...
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #439 on: October 22, 2014, 12:59:04 PM »
|
|
|
Please use right-click->mark to copy paste the text output itself rather than using screen shots!
|
|
|
|
|
Logged
|
|
|
|
kanaan
Newbie
Karma: +0/-0
Offline
Posts: 5
|
|
« Reply #440 on: October 23, 2014, 01:42:08 PM »
|
|
|
try p6.3 when writing
|
|
|
|
|
Logged
|
|
|
|
|
turboat
|
|
« Reply #441 on: October 28, 2014, 05:58:52 AM »
|
|
|
I've had this issue with version 1.40, while 1.31 writes with no complaints:
User@USER-PC /c/Mapping/Immo
$ me7_95040_old.exe --bootmode -wp1 4B0906018AD_A6_18t_2.bin
Ver: 1.31
Com Port: 1
Baud Rate: 10400
Opening COM1 ... 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
Verifying EEPROM write ... OK
Closing COM1
User@USER-PC /c/Mapping/Immo
$ me7_95040_old.exe --OBD -rp1 4B0906018AD_A6_18t_readback.bin
Ver: 1.31
Com Port: 1
Baud Rate: 10400
Opening COM1 ... OK
Initiating communication ... OK
ECU ID response: 06A906032RT
1.8L R4/RTP
0002
SoftCod: 11500, WSC: 02325
Reading EEPROM ................................................................
...... OK
File saved
Closing COM1
User@USER-PC /c/Mapping/Immo
$ me7_95040.exe --bootmode 95040 -wp1 4B0906018AD_A6_18t_2.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 ... 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 COM1
User@USER-PC /c/Mapping/Immo
$ me7_95040_old.exe --OBD -rp1 4B0906018AD_A6_18t_readback_after_failed_write.bin
Ver: 1.31
Com Port: 1
Baud Rate: 10400
Opening COM1 ... OK
Initiating communication ... OK
ECU ID response: 06A906032RT
1.8L R4/RTP
0002
SoftCod: 11500, WSC: 02325
Reading EEPROM ...................................................................... OK
File saved
Closing COM1
Wierdly whenever I write an eeprom to this ECU and read it back, 4 bytes change. If I write back the changed eeprom, the 4 bytes change again - Diff the attached files to see, 0x112 to 0x115.
|
|
|
|
|
Logged
|
|
|
|
Cabok
Newbie
Karma: +4/-0
Offline
Posts: 12
|
|
« Reply #442 on: October 28, 2014, 09:37:41 AM »
|
|
|
I figured I could add both 1.31 and 1.40 versions in the GUI, since I see that sometimes 1.31 works better.
I've added 4 preset buttons after playing with the GUI yesterday. I guess I could add more of them, but I don't want a huge window, my workshop PC is an old laptop with an external screen, in low resolution...
So this is ME7gui version 1.06.
Included are the GUI, ME7 v1.40 and ME7 v1.31.
(screenshot attached)
|
|
|
|
|
Logged
|
|
|
|
tpzd3fq
Newbie
Karma: +0/-0
Offline
Posts: 8
|
|
« Reply #443 on: November 09, 2014, 07:17:52 AM »
|
|
|
Great job and nice man ArgDub !
many thanks !
|
|
|
|
|
Logged
|
|
|
|
tpzd3fq
Newbie
Karma: +0/-0
Offline
Posts: 8
|
|
« Reply #444 on: November 09, 2014, 07:21:55 AM »
|
|
|
Somebody so kind telling me
Does ver 0.2 not support setting new skc? if so how about other version
D:\VAG>me702 --in on.bin --out skc.bin --skc 01234
95040 Eeeprom Tool - 0.2 - 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
Not Yet Supported for ECU Bins
Traceback (most recent call last):
File "95040tool.py", line 702, in <module>
File "95040tool.py", line 677, in main
AttributeError: ecueeprom instance has no attribute 'setSKC'
|
|
|
|
|
Logged
|
|
|
|
|
turboat
|
|
« Reply #445 on: November 09, 2014, 01:46:05 PM »
|
|
|
Somebody so kind telling me
Does ver 0.2 not support setting new skc? if so how about other version
>Not Yet Supported for ECU Bins
No, Eeeprom tool doesnt support setting SKC in ECU eeproms, only in cluster eeproms (because I never needed to set it in an ECU). You could set the SKC in the bin using a hex editor and then use that tool to set the checksum, or add the function yourself, the source code is in the thread (and if you do, edit version 0.3). Also, please ask about each tool on the thread for that tool, took me a while to figure out what you were talking about on this thread. |
|
|
|
|
Logged
|
|
|
|
tpzd3fq
Newbie
Karma: +0/-0
Offline
Posts: 8
|
|
« Reply #446 on: November 09, 2014, 10:28:19 PM »
|
|
|
No, Eeeprom tool doesnt support setting SKC in ECU eeproms, only in cluster eeproms (because I never needed to set it in an ECU).
yes I got it and thank u very much by this tool we get both skc,original ecu and swapping one and then we can easily mach the swapping ecu by scan tools dont need to set skc of the swapping ecu by hexeditor,really thanks again |
|
|
|
|
Logged
|
|
|
|
Allabout
Full Member
Karma: +0/-2
Offline
Posts: 54
|
|
« Reply #447 on: November 19, 2014, 02:16:26 AM »
|
|
|
so been adviced to use this tool When I use a generic Galetto cable I can get it to read and will take about 30 seconds indicating it's working with an indication bar running accross the screen and fails. If I use VCDS genuine in dumb mode with VCP port it fails almost instantly. With or without the cluster connected. Thinking the K-line communication between ECU nad cluster is flooding communication. C:\ME7>me7_95040 -r -p 1 95040.bin Opening COM1 ... OK Starting Boot_mode ... FAIL ... No response from ECU. (error=0x07) Closing COM1 C:\ME7>me7_95040 -r -p 2 95040.bin Opening COM2 ... Unable to open comport. (error=0x01) Closing COM2 Which indicates to me that being a Euro ECU with Immo this maybe the cause? So I would need to boot mode the ECU?? |
|
|
|
|
Logged
|
|
|
|
|
turboat
|
|
« Reply #448 on: November 19, 2014, 04:25:49 AM »
|
|
|
Which indicates to me that being a Euro ECU with Immo this maybe the cause?
So I would need to boot mode the ECU??
You should not need to boot mode the ECU to read the eeprom, but some people report issues reading it over ODB - the euro/immo should not affect this thou, I reguarly read 1.8T and 2.7T ECUs over ODB when they have immo active (In fact, I dont think I've ever read a eeprom in bootmode). Make sure you do not click away from the window or try and do anything else while you are reading the ecu, this often causes it to fail to read. What ECU is it? |
|
|
|
|
Logged
|
|
|
|
jakani rachid
Newbie
Karma: +0/-0
Offline
Posts: 1
|
|
« Reply #449 on: November 27, 2014, 02:37:51 AM »
|
|
|
dear nefmoto forum
need source file for Re: ME7_95040 - EEPROM please
because i do programation c , i want know how the soft work
best regards
jakani
thank very much
|
|
|
|
|
Logged
|
|
|
|
|
