N1CKY
Jr. Member
Karma: +1/-0
 Offline
Posts: 31
|
 |
« on: September 01, 2014, 05:36:43 AM »
|
|
|
Hello lads, I have a r32 engine with the me7.1.1 ecu and the origional owner failed to immo off the ecu, I then sent it to another guy who tried to IMMO off and it seemed to make it worse, He told me i need an origional dump. Are all me.7.1.1 dumps the same? I found this thread below but i dont know if its safe to flash to my chip? http://nefariousmotorsports.com/forum/index.php?topic=3319.0title=Thanks in advance. |
|
|
|
|
Logged
|
|
|
|
N1CKY
Jr. Member
Karma: +1/-0
Offline
Posts: 31
|
|
« Reply #1 on: September 01, 2014, 05:43:51 AM »
|
|
|
|
|
|
|
|
Logged
|
|
|
|
|
turboat
|
|
« Reply #2 on: September 01, 2014, 06:39:06 AM »
|
|
|
That *may* work, but personally I would not try flashing an eeprom from a totally different vehicle just to do an immo-off.
Immo-off is super easy, you just need the ecu, windows laptop and a blue KKL lead.
|
|
|
|
|
Logged
|
|
|
|
N1CKY
Jr. Member
Karma: +1/-0
Offline
Posts: 31
|
|
« Reply #3 on: September 01, 2014, 07:58:52 AM »
|
|
|
I have all 3, Does the canbus have to be wired into the OBD port or does it flash over Kline? Its not the regular eeprom thats in normal me.7's from what iv read, This eeprom is marked SP08C3 253P. Im abit desperate because at the moment iv got a ecu thats useless.
|
|
|
|
|
Logged
|
|
|
|
|
turboat
|
|
« Reply #4 on: September 01, 2014, 08:13:35 AM »
|
|
|
The regular 7.1/7.5 ecus can be flashed over k-line, dont know if yours is different. Try reading the eeprom out of it and see.
|
|
|
|
|
Logged
|
|
|
|
N1CKY
Jr. Member
Karma: +1/-0
Offline
Posts: 31
|
|
« Reply #5 on: September 01, 2014, 08:36:17 AM »
|
|
|
The regular 7.1/7.5 ecus can be flashed over k-line, dont know if yours is different. Try reading the eeprom out of it and see.
Im unfamiliar on the software that needs to be used, Is it the one below? http://nefariousmotorsports.com/forum/index.php?topic=1168.0 |
|
|
|
|
Logged
|
|
|
|
|
turboat
|
|
« Reply #6 on: September 01, 2014, 08:47:50 AM »
|
|
|
Yep, use argdub's tool to read/write to the ECU.
1. Read eeprom from ECU.
2. Set immo to off in the eeprom dump.
3. Fix checksum
4. Write back to ECU in bootmode.
|
|
|
|
|
Logged
|
|
|
|
N1CKY
Jr. Member
Karma: +1/-0
Offline
Posts: 31
|
|
« Reply #7 on: September 01, 2014, 08:54:04 AM »
|
|
|
Thanks, Sorry for the questions. But is there a specific set of drivers i have to use for the cable? Or just the ones provided on ross tech website? Also, Is that the most up to date version of the software on page 1?
Thanks again.
|
|
|
|
|
Logged
|
|
|
|
|
turboat
|
|
« Reply #8 on: September 01, 2014, 10:12:00 AM »
|
|
|
I use the FTDI drivers from their website (the manufacturer of the chipset) for my blue cable http://www.ftdichip.com/FTDrivers.htm, the D2xx ones seem to work ok. With my rosstech lead, I use the rosstech drivers, but I've never managed to get that working with argdub's tool (although others report that if you use the rosstech Virtual Com Port drivers, it will work). I think the most up to date version of argdub's tool is somewhere in the thread, not in the first post. FYI you may need to mess around inside your ECU to get it into boot mode (required to write the eeprom back to the ecu) - I think you will need to remove a resistor from the board,there are threads on the subject, but I've never paid too much attention as I dont have an R32. |
|
|
|
|
Logged
|
|
|
|
N1CKY
Jr. Member
Karma: +1/-0
Offline
Posts: 31
|
|
« Reply #9 on: September 02, 2014, 11:06:38 AM »
|
|
|
Right, Iv managed to read the eeprom twice. (In about 20 attempts, I keep getting a weird error!) c:\SIR\Nicky\ECU>me7_1.4.exe --bootmode 95P08 -p 3 -b 10400 -r dump3.bin
ME7_EEPROM v1.40
COM: 3, Baud Rate: 10400
Memory type: 95P08, size: 1024
Opening COM3 ... 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
Searching Chip_Select pin ... P6.3
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00F0
Reading EEPROM ... FAIL. (error=0x40B01)
Closing COM3 Any ideas? Attatched are the two files plus a log that i managed to get! |
|
|
|
|
Logged
|
|
|
|
|
turboat
|
|
« Reply #10 on: September 02, 2014, 12:28:38 PM »
|
|
|
Just had a quick look at these in a hex editor, defo isnt a happy read: - the files are twice as long as conventional eeproms, 1024bytes not 512bytes, with the latter 512bytes padded with FFs. This may be an R32 *thing* or it may be a failed read, if you can find a known good R32 eeprom then take a look at that and see. - the first half of the file looks good, but even limiting to the first 512bytes only, it appears the checksum is invalid: $ python 95040tool.py dump2.bin
Debug mode active
Read in 64 16 byte rows - 1024bytes total
Parsing as ECU eeprom
EEPROM Status:
- VIN: WVWZZZ1JZ4D010174 (VW 2004 - Golf and Bora 4, Bratislave, Slovakia)
- SKC: 06050
- Immobiliser: Off
- Checksum: Invalid Checksum
- Size: 1024bytes - 512bytes expected, check this is a eeprom bin
- Cluster Code: BA DD 32 C5 E2 C8 3B
- P0601 DTC: not set
- Immo ID: VWZ7Z0C8204091
- Softcoding ID: 0132 I would try reading it over odb not boot mode, or try using the bootmode params as described in this thread http://nefariousmotorsports.com/forum/index.php?topic=5675.0 |
|
|
|
|
Logged
|
|
|
|
|
k0mpresd
|
|
« Reply #11 on: September 02, 2014, 12:30:25 PM »
|
|
|
that e2p is 1kb in size. not 512 bytes like conventional me7.5. it is padded with ff on the bottom half.
also, a quick look at a data sheet and his e2p chip # would have told you that.
|
|
|
|
|
Logged
|
|
|
|
N1CKY
Jr. Member
Karma: +1/-0
Offline
Posts: 31
|
|
« Reply #12 on: September 02, 2014, 01:09:34 PM »
|
|
|
Just had a quick look at these in a hex editor, defo isnt a happy read: - the files are twice as long as conventional eeproms, 1024bytes not 512bytes, with the latter 512bytes padded with FFs. This may be an R32 *thing* or it may be a failed read, if you can find a known good R32 eeprom then take a look at that and see. - the first half of the file looks good, but even limiting to the first 512bytes only, it appears the checksum is invalid: $ python 95040tool.py dump2.bin
Debug mode active
Read in 64 16 byte rows - 1024bytes total
Parsing as ECU eeprom
EEPROM Status:
- VIN: WVWZZZ1JZ4D010174 (VW 2004 - Golf and Bora 4, Bratislave, Slovakia)
- SKC: 06050
- Immobiliser: Off
- Checksum: Invalid Checksum
- Size: 1024bytes - 512bytes expected, check this is a eeprom bin
- Cluster Code: BA DD 32 C5 E2 C8 3B
- P0601 DTC: not set
- Immo ID: VWZ7Z0C8204091
- Softcoding ID: 0132 I would try reading it over odb not boot mode, or try using the bootmode params as described in this thread http://nefariousmotorsports.com/forum/index.php?topic=5675.0 So can i fix the checksum and ill be good to write back to the chip ? Also any idea why its rarely reading and giving me an error ? I tried it in obd mode with similar result. Thanks a bunch guys |
|
|
|
|
Logged
|
|
|
|
|
k0mpresd
|
|
« Reply #13 on: September 02, 2014, 01:14:45 PM »
|
|
|
that immo off/on or whatever the hell someone was trying to do is completely wrong.
|
|
|
|
|
Logged
|
|
|
|
N1CKY
Jr. Member
Karma: +1/-0
Offline
Posts: 31
|
|
« Reply #14 on: September 02, 2014, 01:28:13 PM »
|
|
|
that immo off/on or whatever the hell someone was trying to do is completely wrong.
Is it fixable ? |
|
|
|
|
Logged
|
|
|
|
|
