b4A4nowA6
Full Member
Karma: +1/-4
 Offline
Posts: 117
|
 |
« Reply #540 on: December 21, 2015, 10:24:46 PM »
|
|
|
so what do we say to a verify eeprom write fail? <error 0x70101> ?
|
|
|
|
|
Logged
|
|
|
|
|
dream3R
|
|
« Reply #541 on: December 25, 2015, 04:41:06 PM »
|
|
|
Well it failed, error code might be in this thread or on the eeprom datasheet.
Post the full output also.
|
|
|
|
|
Logged
|
|
|
|
Kenmaira
Newbie
Karma: +0/-0
Offline
Posts: 2
|
|
« Reply #542 on: December 29, 2015, 09:58:24 AM »
|
|
|
I actually have a question in regards to this tool.
For some reason every time that I pull the file off, it ends up pulling a 1024 bit file instead of a 512 bit, am I doing something wrong?
|
|
|
|
|
Logged
|
|
|
|
|
dream3R
|
|
« Reply #543 on: December 30, 2015, 08:02:21 PM »
|
|
|
Set the chip and pins manually. Is the latter 512k all FF?
Big eeprom both. Something wrong.
You're not getting confused with the flash?
|
|
|
|
|
Logged
|
|
|
|
NitroX5
Newbie
Karma: +0/-1
Offline
Posts: 2
|
|
« Reply #544 on: January 05, 2016, 12:57:59 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
|
|
|
|
|
Logged
|
|
|
|
|
dream3R
|
|
« Reply #545 on: January 05, 2016, 01:20:03 PM »
|
|
|
Try chip 95080 100% works done it b4 a couple of years ago on that ecu. Writing I never did though.
|
|
|
|
« Last Edit: January 05, 2016, 01:54:27 PM by dream3R »
|
Logged
|
|
|
|
NitroX5
Newbie
Karma: +0/-1
Offline
Posts: 2
|
|
« Reply #546 on: January 05, 2016, 02:21:06 PM »
|
|
|
No, unfortunately the same result with 95080, 1Kb file. Strange. Try chip 95080 100% works done it b4 a couple of years ago on that ecu. Writing I never did though.
|
|
|
|
|
Logged
|
|
|
|
|
dream3R
|
|
« Reply #547 on: January 05, 2016, 02:27:30 PM »
|
|
|
No, unfortunately the same result with 95080, 1Kb file. Strange.
1KB is correct is it not? The software not writing it is a different issue. |
|
|
|
|
Logged
|
|
|
|
|
dream3R
|
|
« Reply #548 on: January 05, 2016, 02:39:57 PM »
|
|
|
2 choices if this s/w doesn't work for you:
1. Lift and burn it (1kb is right)
2. It can be done over obd2 (if VIDA can e.g.)
|
|
|
|
|
Logged
|
|
|
|
MeNewbie
Full Member
Karma: +1/-2
Offline
Posts: 50
|
|
« Reply #549 on: January 15, 2016, 04:46:15 PM »
|
|
|
2004 Volvo Bosch ME7.5 error. Ecu read success but EEPROM programmer didn't work. me731 --bootmode -b 9600 -r -p 1 read.bin
Ver: 1.31
Com Port: 1
Baud Rate: 9600
Opening COM1 ... OK
Starting Boot_mode ... uC identification response = 0xFF. Unknown ID. (error=0x01)
Closing COM1 |
|
|
|
|
Logged
|
The right way to do things successfully is IDA.
|
|
|
|
dream3R
|
|
« Reply #550 on: January 15, 2016, 07:52:33 PM »
|
|
|
2004 Volvo Bosch ME7.5 error. Ecu read success but EEPROM programmer didn't work. me731 --bootmode -b 9600 -r -p 1 read.bin
Ver: 1.31
Com Port: 1
Baud Rate: 9600
Opening COM1 ... OK
Starting Boot_mode ... uC identification response = 0xFF. Unknown ID. (error=0x01)
Closing COM1 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 |
|
|
|
« Last Edit: January 15, 2016, 07:56:49 PM by dream3R »
|
Logged
|
|
|
|
gonzo42
Newbie
Karma: +0/-0
Offline
Posts: 2
|
|
« Reply #551 on: January 15, 2016, 11:45:25 PM »
|
|
|
First off thanks for this cool free tool!
I cant seem to get a eeprom read to work no matter what I try. I read through this entire thread a few times and tried all the fixes I could find with others that had a similar error. I get a connection on comm 1 and the tool talks to the ecu and returns the first bit of info but when it tries to read the ECU it fails with the x07 or x01 error. I tried pulling the instrument cluster fuse and that didnt work either. Tried both v3.1 and v4 both only get the initial connection and fail on eprom reading. Coudnt seem to get the ecu in bootmode either but wasnt sure I was doing that correctly over OBD.
Goal:
Im trying to get the secret code to so I can code a new key to my 2000 D2 A8 4.2 Through the OBD port.
Im using a Ross-Tech Hex+Can cable running with the virtual comm port drivers set to Comm 1. Also the VCDS software is set to NOT be in "boot intelligent mode"
Any help is appreciated! Thanks!
|
|
|
|
« Last Edit: January 16, 2016, 12:06:22 AM by gonzo42 »
|
Logged
|
|
|
|
|
dream3R
|
|
« Reply #552 on: January 15, 2016, 11:52:04 PM »
|
|
|
First off thanks for this cool free tool!
I cant seem to get a eeprom read to work no matter what I try. I read through this entire thread a few times and tried all the fixes I could find with others that had a similar error. I get a connection on comm 1 and the tool talks to the ecu and returns the first bit of info but when it tries to read the ECU it fails with the x07 or x01 error. I tried pulling the instrument cluster fuse and that didnt work either. Tried both v3.1 and v4 both only get the initial connection and fail on eprom reading. Coudnt seem to get the ecu in bootmode either but wasnt sure I was doing that correctly over OBD.
Goal:
Im trying to get the secret code to so I can code a new key to my 2000 D2 A8 4.2 Through the OBD port.
Im using a Ross-Tech Hex+Can cable running with the virtual comm port drivers set to Comm 1. Also the VCDS software is set to NOT be in "boot intelligent mode"
Any help is appreciated! Thanks!
post the cmd output mate,can't help otherwise |
|
|
|
|
Logged
|
|
|
|
gonzo42
Newbie
Karma: +0/-0
Offline
Posts: 2
|
|
« Reply #553 on: January 16, 2016, 12:09:09 AM »
|
|
|
post the cmd output mate,can't help otherwise
Thanks for the quick reply, the CMD readout is attached now. |
|
|
|
|
Logged
|
|
|
|
|
dream3R
|
|
« Reply #554 on: January 16, 2016, 12:22:55 AM »
|
|
|
nope lol
|
|
|
|
|
Logged
|
|
|
|
|
