MeNewbie
Full Member
Karma: +1/-1
 Offline
Posts: 50
|
 |
« Reply #555 on: January 16, 2016, 07:28:47 AM »
|
|
|
com port or ecu is not in bootmode issue, also your syntax is wrong for pin and chip Also it's ME7.01 ME7EEPROM.exe -p 3 --bootmode 95080 --CSpin P8.2 -r eep.bin Simply upgraded to v1.40 and it works! Thanks for right pins. Read 1kb OK and write 1kb OK but on write Verify give me error. me740 -p 1 --bootmode 95080 -b 9600 --CSpin P8.2 -w eep.bin --reconnect
ME7_EEPROM v1.40
COM: 1, Baud Rate: 9600
Memory type: 95080, size: 1024
Chip Select pin: P8.2
Opening COM1 ... OK
Testing monitor communication ... MonitorCore successfully launched
Initializing registers ... OK
Sending EEPROM driver ... OK
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x0080
Writing EEPROM ................................................................
OK
Verifying EEPROM write ... FAIL. (error=0x70101)
Closing COM1
error=0x70101 what is it? I checked EEPROM by read it again and my modification are here so basically write was OK. Why does it have ME7_500 in flash if it ME7.0? Pic attached. |
|
|
|
|
Logged
|
The right way to do things successfully is IDA.
|
|
|
|
dream3R
|
|
« Reply #556 on: January 16, 2016, 10:53:51 AM »
|
|
|
Simply upgraded to v1.40 and it works! Thanks for right pins. Read 1kb OK and write 1kb OK but on write Verify give me error. me740 -p 1 --bootmode 95080 -b 9600 --CSpin P8.2 -w eep.bin --reconnect
ME7_EEPROM v1.40
COM: 1, Baud Rate: 9600
Memory type: 95080, size: 1024
Chip Select pin: P8.2
Opening COM1 ... OK
Testing monitor communication ... MonitorCore successfully launched
Initializing registers ... OK
Sending EEPROM driver ... OK
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x0080
Writing EEPROM ................................................................
OK
Verifying EEPROM write ... FAIL. (error=0x70101)
Closing COM1
error=0x70101 what is it? I checked EEPROM by read it again and my modification are here so basically write was OK. Why does it have ME7_500 in flash if it ME7.0? Pic attached. I have used this tool a few years ago but now do it over OBD2, I'll check that error code later. Did you chek the EEPOM itself, it hasn't been replaced has it? Edit: Once written it reads the EEPROM again and if the files don't match it displays that error |
|
|
|
« Last Edit: January 16, 2016, 11:01:40 AM by dream3R »
|
Logged
|
|
|
|
MeNewbie
Full Member
Karma: +1/-1
Offline
Posts: 50
|
|
« Reply #557 on: January 16, 2016, 01:01:44 PM »
|
|
|
I have used this tool a few years ago but now do it over OBD2, I'll check that error code later. Did you chek the EEPOM itself, it hasn't been replaced has it?
Edit: Once written it reads the EEPROM again and if the files don't match it displays that error
I read EEPROM, edit, write with error. Read EEPROM again and it was replaced with my edited. Then compare both by bytes - everything is OK. |
|
|
|
|
Logged
|
The right way to do things successfully is IDA.
|
|
|
|
dream3R
|
|
« Reply #558 on: January 16, 2016, 01:06:19 PM »
|
|
|
I read EEPROM, edit, write with error. Read EEPROM again and it was replaced with my edited. Then compare both by bytes - everything is OK.
Good, just a bug in the code then. |
|
|
|
|
Logged
|
|
|
|
MeNewbie
Full Member
Karma: +1/-1
Offline
Posts: 50
|
|
« Reply #559 on: January 16, 2016, 01:28:36 PM »
|
|
|
Good, just a bug in the code then.
Yeap, primary reported here for ArgDub. |
|
|
|
|
Logged
|
The right way to do things successfully is IDA.
|
|
|
|
dream3R
|
|
« Reply #560 on: January 16, 2016, 01:30:16 PM »
|
|
|
Yeap, primary reported here for ArgDub.
I'm guessing the second read is zero bytes |
|
|
|
|
Logged
|
|
|
|
MeNewbie
Full Member
Karma: +1/-1
Offline
Posts: 50
|
|
« Reply #561 on: January 16, 2016, 03:24:52 PM »
|
|
|
I'm guessing the second read is zero bytes
Read it in new file. |
|
|
|
|
Logged
|
The right way to do things successfully is IDA.
|
|
|
|
dream3R
|
|
« Reply #562 on: January 16, 2016, 03:38:48 PM »
|
|
|
I meant the software reads it and compares it in RAM  |
|
|
|
|
Logged
|
|
|
|
|
dream3R
|
|
« Reply #563 on: January 16, 2016, 06:40:45 PM »
|
|
|
Dear All,
suffering to read out immo chip. Searched a lot, problem is quite unique as far as I saw.
Connect, establish, read but the result is only 1Kb !!! Which as I know wrong?! (because when I want to write it back got error for file size...)
My ECU is 2004 Volvo S60R Me7.01.
Immo IC labeled: 5P08C3 (so it means 95P08 should be used but tried 95080 also)
Tried a different ECU, even an older ME7.0 ECU same result.
Used KKL Serial interface with FTDI Serial to USB converter. (even tried via serial port, same result.)
1.31 not works nor in OBD mode.
Any suggestion?
E:\ME7\Progik>ME7eeprom -p 1 --bootmode 95P08 -r --CSpin P8.2 immo.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
Reading EEPROM ... OK
File saved
Closing COM1
see above |
|
|
|
|
Logged
|
|
|
|
Power
Newbie
Karma: +0/-0
Offline
Posts: 3
|
|
« Reply #564 on: January 19, 2016, 11:45:07 PM »
|
|
|
hello guys, sorry for my bad english, I'm a foreigner)) please help me with a problem  . I have the ECU from skoda 2005(year of issue), put it on audi 2002(year of issue). I want to change EEPROM from my own ECU(audi), but I'm can't read the ECU skoda with the programm me7_95040(v.1.31) to save EEPROM skoda ECU. What's I do wrong ? the programm write the mistake: (in OBD mode) error 0x07 (in bootmode) no response from ECU error 0x07 |
|
|
|
|
Logged
|
|
|
|
Power
Newbie
Karma: +0/-0
Offline
Posts: 3
|
|
« Reply #565 on: January 20, 2016, 12:21:53 AM »
|
|
|
and what's mean errors 0x07 and 0x01?
|
|
|
|
|
Logged
|
|
|
|
|
dream3R
|
|
« Reply #566 on: January 20, 2016, 12:48:59 AM »
|
|
|
Just boot mode it mate, works better also 1.40 is the latest. 0x07 = ecu com issue (Cluster mb) 0x01 = no com port seen |
|
|
|
« Last Edit: January 20, 2016, 12:54:21 AM by dream3R »
|
Logged
|
|
|
|
Pali33
Newbie
Karma: +0/-0
Offline
Posts: 2
|
|
« Reply #567 on: January 20, 2016, 02:07:06 AM »
|
|
|
I have problem with Bosch ME3.1 (Alfa,Fiat) - 95080
I can read it, but write not works. The write process works normaly, but at the end comes "Verify error 0x70101".
I use this command:
--bootmode 95080 -w -p3 --CSpin P4.7 file.bin
I think, the 95080 have aktive software Write protect (BP1,BP0). Hardware Write protect PIN3 is not active, there is 5V.
So my question: is it possible to change the status register (write protect bits BP1,BP0) with this famous software? Or would be possible to add this function to new version?
Or is this any other problem?
Many thanks in advance.
Pali.
|
|
|
|
|
Logged
|
|
|
|
|
dream3R
|
|
« Reply #568 on: January 20, 2016, 02:21:27 AM »
|
|
|
I have problem with Bosch ME3.1 (Alfa,Fiat) - 95080
I can read it, but write not works. The write process works normaly, but at the end comes "Verify error 0x70101".
I use this command:
--bootmode 95080 -w -p3 --CSpin P4.7 file.bin
I think, the 95080 have aktive software Write protect (BP1,BP0). Hardware Write protect PIN3 is not active, there is 5V.
So my question: is it possible to change the status register (write protect bits BP1,BP0) with this famous software? Or would be possible to add this function to new version?
Or is this any other problem?
Many thanks in advance.
Pali.
Did you check the pin before running that? The 0x70101 code is a bug, but you should read the ecu eep again and compare. |
|
|
|
« Last Edit: January 20, 2016, 02:24:29 AM by dream3R »
|
Logged
|
|
|
|
Pali33
Newbie
Karma: +0/-0
Offline
Posts: 2
|
|
« Reply #569 on: January 20, 2016, 02:35:00 AM »
|
|
|
what pin you mean?
After write, i have read again and compare. The content of eep is not changed (the same content as befor write).
Unfortunately, i'm not sure if it was exactly code 0x70101 . And i can't check it now ... maybe later, next week.
EDIT: now i understand, which pin you mean.... yes, i have check the PIN3 on eeprom (hybrid ECU). It is not easy, but is possible. Because i can not write this eep with your software, i have write this with UPA-Programmer (by direct connection on the eeprom). It is possible, but very dangerous. So i search the "safe" writing solution :-)
|
|
|
|
« Last Edit: January 20, 2016, 03:21:35 AM by Pali33 »
|
Logged
|
|
|
|
|
