|
JeanAwt
|
 |
« Reply #945 on: December 28, 2024, 05:08:42 AM »
|
|
|
i am using blue kkl cable but its ch340 and keeps saying comunnication fail how do i fix???
Buy ft232rl |
|
|
|
|
Logged
|
A4 B5 1.8T ONLY
|
|
|
mRj
Jr. Member
Karma: +0/-0
 Offline
Posts: 38
|
|
« Reply #946 on: January 06, 2025, 11:32:55 AM »
|
|
|
Could you please tell how do you solve this problem?
i have the same error, struggling to write it back. i have read it fine. This is the error on both 1.31 and 1.40 on me7.5 out of an Audit TT (BAM) Happens on both win10 and xp Ver: 1.31 Com Port: 2 Baud Rate: 10400 Opening COM2 ... OK Starting Boot_mode ... uC identification response = 0xC5 (C167 derivatives) ... OK Sending Loader + MonitorCore ... MonitorCore successfully launched Initializing registers ... FAIL. (error=0x01) Closing COM2 |
|
|
|
« Last Edit: January 06, 2025, 12:57:50 PM by mRj »
|
Logged
|
|
|
|
mRj
Jr. Member
Karma: +0/-0
Offline
Posts: 38
|
|
« Reply #947 on: January 08, 2025, 01:50:47 AM »
|
|
|
i have the same error, struggling to write it back.
i have read it fine.
This is the error on both 1.31 and 1.40 on me7.5 out of an Audit TT (BAM)
Happens on both win10 and xp
Ver: 1.31
Com Port: 2
Baud Rate: 10400
Opening COM2 ... OK
Starting Boot_mode ... uC identification response = 0xC5 (C167 derivatives) ...
OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... FAIL. (error=0x01)
Closing COM2
I have fixed this, using a red VAG.KKL cable (shown as serial port on device manager) Also, only 1.31 worked, 1.40 failed to verify the Eeprom. |
|
|
|
« Last Edit: January 11, 2025, 08:00:19 AM by mRj »
|
Logged
|
|
|
|
Rick81
Full Member
Karma: +0/-11
Offline
Posts: 119
|
|
« Reply #948 on: January 10, 2025, 07:58:55 PM »
|
|
|
I'm glad it worked out. I've also got the Vag kkl cable and carnt get the program to read. How long did you leave the boot pin on for. Or should I say what did you do
|
|
|
|
|
Logged
|
|
|
|
|
|
Andre20VT
Jr. Member
Karma: +1/-0
Offline
Posts: 32
|
|
« Reply #950 on: March 27, 2025, 11:41:50 AM »
|
|
|
Hi, just tried to read the eeprom from 2 me7.5 ecu's, the first one without problems but the other one gives a error when trying to read the eeprom. I keep getting the error Searching Chip_select pin..... Fail (error=0x01) Anybody a idea what is going wrong?  Thanks |
|
|
|
|
Logged
|
|
|
|
Andre20VT
Jr. Member
Karma: +1/-0
Offline
Posts: 32
|
|
« Reply #951 on: March 27, 2025, 12:02:14 PM »
|
|
|
Fixed it... used latest version 1.40 and manual put in --cspin4.7 in command line and now it worked  |
|
|
|
|
Logged
|
|
|
|
V70user
Newbie
Karma: +1/-0
Offline
Posts: 9
|
|
« Reply #952 on: May 10, 2025, 05:36:27 AM »
|
|
|
I can confirm that ArgDub tool works almost perfect with Volvo ECM ecus ME7 (only in bootmode)
I say almost perfect just because writing file verification error pops up, but without affecting its content.
EEPROM data are correctly written. So, don't bother this writing file verification fail error at all.
I checked it several times and the results were always the same - EEPROM data correct.
In Volvo case an OBD mode doesn't work.
Serial cable based on Max232 and USB cable with FT232RL chip was used to reading and writing.
Commands wrote in commandline have given back positive outcomes.
Thank You a lot Argdub !
First tested ECM ecu :
Volvo V70 II B5244T3, MY 2000, 147KW/200PS (HP), AUT, FWD
Infineon SAK C167CR - LM ; ME7 HL.2 ; 0 261 206 828
'**************************************************************************************************
Reading example (bootmode required)
me7_v140 -p1 -b10400 --CSpin P4.7 --bootmode 95P08 -r 95P08_47_0905.bin
C:\>me7_v140 -p1 -b10400 --CSpin P4.7 --bootmode 95P08 -r 95P08_47_0905.bin
ME7_EEPROM v1.40
COM: 1, Baud Rate: 10400
Memory type: 95P08, size: 1024
Chip Select pin: P4.7
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
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00F0
Reading EEPROM ... OK
File saved
Closing COM1
'*************************************************************************************************
Writing example (bootmode required)
me7_v140 -p1 -b10400 --CSpin P4.7 --bootmode 95P08 -w 95P08_47_0905.bin
C:\>me7_v140 -p1 -b10400 --CSpin P4.7 --bootmode 95P08 -w 95P08_47_0905.bin
ME7_EEPROM v1.40
COM: 1, Baud Rate: 10400
Memory type: 95P08, size: 1024
Chip Select pin: P4.7
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
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00F0
Writing EEPROM ................................................................
OK
Verifying EEPROM write ... FAIL. (error=0x70101)
Closing COM1
'*************************************************************************************************
'*************************************************************************************************
'*************************************************************************************************
Second ECM
Volvo V70 II B5234T3, MY 2004, 184kW/ 250PS (HP), AUT, FWD
Infineon SAK C167CS - L40M ; ME7 L6.2 ; 0 261 207 712
'*************************************************************************************************
Reading example (bootmode required)
me7_v140 -p1 -b10400 --CSpin P8.2 --bootmode 95P08 -r V70T5_95P08_82_1005.bin
C:\>me7_v140 -p1 -b10400 --CSpin P8.2 --bootmode 95P08 -r V70T5_95P08_82_1005.bin
ME7_EEPROM v1.40
COM: 1, Baud Rate: 10400
Memory type: 95P08, size: 1024
Chip Select pin: P8.2
Opening COM1 ... OK
Starting Boot_mode ... uC ID response 0xD5 ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Reading IDCHIP ... 0x0C43: C167CS ... OK
Initializing registers ... OK
Sending EEPROM driver ... OK
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00FC
Reading EEPROM ... OK
File saved
Closing COM1
'*************************************************************************************************
Write example (bootmode required)
me7_v140 -p1 -b10400 --CSpin P8.2 --bootmode 95P08 -w V70T5_95P08_82_1005.bin
C:\>me7_v140 -p1 -b10400 --CSpin P8.2 --bootmode 95P08 -w V70T5_95P08_82_1005.bin
ME7_EEPROM v1.40
COM: 1, Baud Rate: 10400
Memory type: 95P08, size: 1024
Chip Select pin: P8.2
Opening COM1 ... OK
Starting Boot_mode ... uC ID response 0xD5 ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Reading IDCHIP ... 0x0C43: C167CS ... OK
Initializing registers ... OK
Sending EEPROM driver ... OK
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00F0
Writing EEPROM ................................................................
OK
Verifying EEPROM write ... FAIL. (error=0x70101)
Closing COM1
|
|
|
|
|
Logged
|
|
|
|
R32_BUB
Newbie
Karma: +0/-0
Offline
Posts: 3
|
|
« Reply #953 on: May 19, 2025, 02:50:06 PM »
|
|
|
I have an issue with Golf MK5 R32 ME7.1.1 ECU 022906032CE 0261208468 377419  HW looks like HW III Family 52 therefore I put a 1k resistor CNF1 and now I can put the ECU into Bootmode. I managed to read ECU flash with MPPS in Bootmode. BUT, I cant' read EEPROM with ME7eeprom CMD tool (I have already some experience with the tool with previous ME7.1.1 and could read E2P) EEPROM is a 95160 chip I get this FAIL report  Please for your help ! I have the exact same issue and that Text could be me in the last hour. I have the same Tools same Mainboard same Error Message in M7Eeprom CMD Tool "0x1143 not supported". Also a ME7.1.1 with 95160 EEprom ECU from, a 2008 R32 022906032KG HW4. Any solution to read the eeprom ? Thanks and Greetings |
|
|
|
|
Logged
|
|
|
|
Artemisia
Full Member
Karma: +24/-0
 Online
Posts: 92
|
|
« Reply #954 on: May 19, 2025, 06:24:25 PM »
|
|
|
I have the exact same issue and that Text could be me in the last hour. I have the same Tools same Mainboard same Error Message in M7Eeprom CMD Tool "0x1143 not supported". Also a ME7.1.1 with 95160 EEprom ECU from, a 2008 R32 022906032KG HW4. Any solution to read the eeprom ?
Thanks and Greetings
Try with this program |
|
|
|
|
Logged
|
|
|
|
R32_BUB
Newbie
Karma: +0/-0
Offline
Posts: 3
|
|
« Reply #955 on: May 20, 2025, 02:11:37 PM »
|
|
|
Try with this program
Thank you I just tested it and it worked perfect. I now could read the 95160 Eeprom without problems. |
|
|
|
|
Logged
|
|
|
|
|
