|
vwaudiguy
|
 |
« Reply #495 on: May 31, 2015, 12:12:58 PM »
|
|
|
I just found myself needing to read a 2007 Rabbit ME7.1.1 with a 95160 and ran into this same problem.
Had to remove and read externally.
Can this "mod" be added into the me7 eeprom tool?
Also interested if anyone found a soloution yet for this? There was one post about mid thread where it was mentioned ver1.4 was "5 minute patched" to get it working, but the patched file wasn't shared. |
|
|
|
« Last Edit: May 31, 2015, 12:50:50 PM by vwaudiguy »
|
Logged
|
"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
|
|
|
|
vwaudiguy
|
|
« Reply #496 on: May 31, 2015, 12:52:15 PM »
|
|
|
Once I urgently needed to reprogram eeprom in last HW versions ME7.1.1 ECUs with ST10F275 inside. No apropriate tools are around, me7eeprom soft not operate because of unknown IDCHIP value. Than I made 5 minute patch in 1.40 version of programmer (ArgDub, please sorry) and can do job.
Below is screen log. A3 3.2 DSG 2008 (022906032LA) ECU
D:\ME7 Eeprom Reader\1.40\me7eeprom --bootmode 95160 --CSpin P6.3 -r -p1 eeprom.bin
ME7_EEPROM v1.40
COM: 1, Baud Rate: 10400
Memory type: 95160, size: 2048
Chip Select pin: P6.3
Opening COM1 ... OK
Starting Boot_mode ... uC ID response 0xD5 ... OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Reading IDCHIP ... 0x1143: C167/ST10F OK
Initializing registers ... OK
Sending EEPROM driver ... OK
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x0080
Reading EEPROM ... OK
File saved
Closing COM1
Here is the post |
|
|
|
|
Logged
|
"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
|
|
|
automan001
Full Member
Karma: +47/-0
 Offline
Posts: 153
|
|
« Reply #497 on: June 14, 2015, 12:01:12 PM »
|
|
|
Some of my experience on reading/writing me7.x ECUs
I made many unsuccessfull attempts on lower speeds (9600, 10400) and didn't know that reason was low baudrate.
Example1: ME7.5.10 030 906 032 CE (01-04-10) didn't want to read/write on speeds less than 19200.
After i set -b 19200 and --CSpin 4.7
c:\App\Auto\me7_95040eeprom>ME7EEPROM_1_4.exe --bootmode 95040 --CSpin P4.7 -w -
p 1 -b 19200 W.bin
ME7_EEPROM v1.40
COM: 1, Baud Rate: 19200
Memory type: 95040, size: 512
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
c:\App\Auto\me7_95040eeprom>ME7EEPROM_1_4.exe --bootmode 95040 --CSpin P4.7 -r -
p 1 -b 19200 R.bin
ME7_EEPROM v1.40
COM: 1, Baud Rate: 19200
Memory type: 95040, size: 512
Chip Select pin: P4.7
Opening COM1 ... OK
Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK
Sending Loader + MonitorCore ... MonitorCore sleuccessfully launched
Initializing registers ... OK
Sending EEPROM driver ... OK
Configuring SPI Interface ... OK
Checking EEPROM Status Register ... 0x00F0
Reading EEPROM ... OK
File saved
Closing COM1
On this speed it writes and reads successfully, but raises error on eeprom validation after writing, however when i read what was written - everything is OK, files match.
Example2:
On e-bay I bought a cheap ME7.5 06A906032FK (03-06-20) and wanted to make 06A906032HN from it. Hardware of the ECU was newer but identical, the 032FK ECU costed less than 032 HN. Usually i read/write 032HN without issues on speed 10400. But this ecu didn't want to write until i increased speed up to 57600. I didn't believe that this could be reason. I thought it was some kind of write protection of different CSpin. But after setting higher speed i've successfully written eeprom from 032HN into it
c:\App\Auto\me7_95040eeprom>ME7EEPROM_1_4.exe --bootmode 95040 --CSpin P4.7 -w -
p 1 -b 57600 W.bin
ME7_EEPROM v1.40
COM: 1, Baud Rate: 57600
Memory type: 95040, size: 512
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
c:\App\Auto\me7_95040eeprom>ME7EEPROM_1_4.exe --bootmode 95040 --CSpin P4.7 -r -
p 1 -b 57600 R.bin
ME7_EEPROM v1.40
COM: 1, Baud Rate: 57600
Memory type: 95040, size: 512
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
I still got EEPROM validation error though. But I ignored the error since data written and read are the same, so everything was OK.
Maybe this experience with baud rate setting will help you to resolve similar unknown errors.
|
|
|
|
« Last Edit: June 14, 2015, 12:17:23 PM by automan001 »
|
Logged
|
|
|
|
|
vwaudiguy
|
|
« Reply #498 on: June 14, 2015, 02:12:51 PM »
|
|
|
Thanks for the suggestions. I have a few on hand that I was unable to read, and will give them a try using different baud rates.
|
|
|
|
|
Logged
|
"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
|
|
|
Mechsoldier
Full Member
Karma: +5/-11
Offline
Posts: 106
|
|
« Reply #499 on: July 02, 2015, 07:42:17 PM »
|
|
|
I cannot get this to work. I've been trying for hours and I keep getting an error stating starting boot_mode....fail erro=0x01
I'm using a generic kcan cable. I also tried the apr cheetah cable with no success, and a couple vag commander or vag k can, generic vag tacho cables, etc. Some of them say no echo from cable, so I feel like this cable seems to be working best....I just don't get it.
|
|
|
|
|
Logged
|
|
|
|
Mechsoldier
Full Member
Karma: +5/-11
Offline
Posts: 106
|
|
« Reply #500 on: July 02, 2015, 08:01:42 PM »
|
|
|
And I forgot to mention, I know it's in boot mode because I can read it with galletto after I get the error
|
|
|
|
|
Logged
|
|
|
|
Mechsoldier
Full Member
Karma: +5/-11
Offline
Posts: 106
|
|
« Reply #501 on: July 06, 2015, 07:25:30 AM »
|
|
|
Got it sorted, I ended up just having to use the Blue kkl cable. I tried a real vcds cable, a real vag tacho cable, Chinese vag tacho cable, chines vag k can and vag commander cables, and I got nowhere. so I suggest using the blue 9 dollar obd2 cablr special from Ebay.
|
|
|
|
|
Logged
|
|
|
|
marchewa
Full Member
Karma: +4/-0
Offline
Posts: 53
|
|
« Reply #502 on: July 11, 2015, 01:23:54 PM »
|
|
|
Great tool.
But I can read my ecu (8e0 909 518) only in bootmode so I was using older version. Don't know why, but also galletto can read flash of this ecu only in bootmode.
|
|
|
|
|
Logged
|
|
|
|
|
Jim_Coupe
|
|
« Reply #503 on: July 20, 2015, 03:39:47 AM »
|
|
|
This program only opens and then closes for me on my Win7 PC? Must the ECU be connected when opening program? Or have i missed the manual?
|
|
|
|
|
Logged
|
E85oholic
|
|
|
rupe
Newbie
Karma: +0/-0
Offline
Posts: 3
|
|
« Reply #504 on: July 20, 2015, 04:31:47 AM »
|
|
|
It's a command line program, so either run it in dos or use the front end for windows which somebody kindly made, you should find it linked in this thread somewhere.
|
|
|
|
|
Logged
|
|
|
|
|
Jim_Coupe
|
|
« Reply #505 on: July 20, 2015, 05:20:58 AM »
|
|
|
It's a command line program, so either run it in dos or use the front end for windows which somebody kindly made, you should find it linked in this thread somewhere.
Thanks i´ll have a look on that.  |
|
|
|
|
Logged
|
E85oholic
|
|
|
|
|
|
turboat
|
|
« Reply #507 on: August 23, 2015, 12:05:32 AM »
|
|
|
Suspect not as it doesn't mention kkl, most people use this with a blue kkl lead.
|
|
|
|
|
Logged
|
|
|
|
|
Lost
|
|
« Reply #508 on: September 01, 2015, 03:44:27 AM »
|
|
|
Reading through this thread i need to clarifie something here.
Is it true that ppl use blue china kable too write 95040.bin in bootmode???
|
|
|
|
|
Logged
|
|
|
|
|
Lost
|
|
« Reply #509 on: September 01, 2015, 12:07:56 PM »
|
|
|
Too answer my own question.
Yes!!! As i just bootflashed immo with cheap China blue cable
|
|
|
|
|
Logged
|
|
|
|
|
