EuroXs4
Full Member
Karma: +15/-31
 Offline
Posts: 209
|
 |
« Reply #645 on: December 13, 2016, 04:06:05 PM »
|
|
|
Anyone know why I cant read 95040 on the bench unless i got into bootmode???
This is what I get:
ME7_EEPROM v1.40
COM: 4, Baud Rate: 10400
Opening COM4 ... OK
Initiating communication ... FAIL. (error=0x50101)
Closing COM4
What gives??I can read 95040 though bootmode without issues.However over obd no chance in hell?Ive used both versions of this software.Am I missing something??
|
|
|
|
« Last Edit: December 13, 2016, 04:08:48 PM by EuroXs4 »
|
Logged
|
|
|
|
TijnCU
Hero Member
Karma: +60/-4
Offline
Posts: 690
flying brick
|
|
« Reply #646 on: December 14, 2016, 12:45:49 AM »
|
|
|
Some ecu's have this, I personally have had at least 6 different ecu's that would only read in bootmode. Not a big deal because you need to write in bootmode anyway...
|
|
|
|
|
Logged
|
|
|
|
|
f1torrents
|
|
« Reply #647 on: December 14, 2016, 12:53:50 AM »
|
|
|
Don't quote me on this as I only use this tool in bootmode, but for OBD doesn't it have to have security access?
ie. The cluster and working key attached.
|
|
|
|
|
Logged
|
|
|
|
Zenerdiode
Newbie
Karma: +1/-0
Offline
Posts: 18
|
|
« Reply #648 on: December 14, 2016, 07:14:21 AM »
|
|
|
I've been able to read a 1ML906032A and a 030906032P as a standalone ECU without having a handshake from the immobiliser - both in OBD mode. Obviously to write, you need bootmode.  |
|
|
|
|
Logged
|
|
|
|
EuroXs4
Full Member
Karma: +15/-31
Offline
Posts: 209
|
|
« Reply #649 on: December 16, 2016, 05:38:23 PM »
|
|
|
So I ran into a snag the other day.I was swapping in a used ecu and different injectors into my car.I ran a ground wire from ecu to the side of the dash with a momentary switch.To get it into boot mode when I want to reflash.Worked great for the first 15 minutes.However at the end I believe the ecu was still in bootmode even after I cycled the key.I would assume that this is because i probably need to pull the 12v constant power supply fuse to the ecu to reset??Can anyone confirm this??
|
|
|
|
|
Logged
|
|
|
|
TrevelXP
Newbie
Karma: +0/-0
Offline
Posts: 8
|
|
« Reply #650 on: December 17, 2016, 12:26:24 PM »
|
|
|
So I ran into a snag the other day.I was swapping in a used ecu and different injectors into my car.I ran a ground wire from ecu to the side of the dash with a momentary switch.To get it into boot mode when I want to reflash.Worked great for the first 15 minutes.However at the end I believe the ecu was still in bootmode even after I cycled the key.I would assume that this is because i probably need to pull the 12v constant power supply fuse to the ecu to reset??Can anyone confirm this??
Best way is just to unplug ECU or Battery terminal. Then plug it back in, ECU should boot in normal mode. |
|
|
|
|
Logged
|
|
|
|
EuroXs4
Full Member
Karma: +15/-31
Offline
Posts: 209
|
|
« Reply #651 on: December 17, 2016, 07:07:55 PM »
|
|
|
I was hoping to pull the fuse instead and short the wire to ground so I wouldnt have to remove the ecu to reflash everytime.
|
|
|
|
|
Logged
|
|
|
|
jahkotuning
Newbie
Karma: +0/-0
Offline
Posts: 10
|
|
« Reply #652 on: February 26, 2017, 06:16:05 AM »
|
|
|
Starting boot mode . . . uc identification response = 0X5D. Not supported. (error = 0X01)
Closing COM2
On a Volvo S60 turbo ecu 0261207392 with a CH340 cable, happens on all baud rates and only get that far if i hit enter just after removing the boot pin. If I'm too slow or try again without re-booting I get FAIL ... No response from ECU. (Error 0x07)
|
|
|
|
|
Logged
|
|
|
|
|
k0mpresd
|
|
« Reply #653 on: March 03, 2017, 07:27:37 AM »
|
|
|
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
does anyone have this patched version for accepting 0x1143 IDCHIP? |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #654 on: March 03, 2017, 11:17:52 AM »
|
|
|
It would be great if he provided source code.
This is why I hate it when people don't.
Abandonware.
|
|
|
|
|
Logged
|
|
|
|
jahkotuning
Newbie
Karma: +0/-0
Offline
Posts: 10
|
|
« Reply #655 on: March 07, 2017, 08:31:33 PM »
|
|
|
Got mine working now, proper KKL cable in dumb mode. Used v1.4 and added --bootmode 95080 --CSpin P8.2 to what I was doing before.
This look right?
|
|
|
|
« Last Edit: March 08, 2017, 06:57:56 AM by jahkotuning »
|
Logged
|
|
|
|
EELSUPNSIDEU
Newbie
Karma: +0/-0
Offline
Posts: 9
|
|
« Reply #656 on: April 08, 2017, 09:30:52 PM »
|
|
|
im having issuses writing. everything goes well and says its writes but then when it verifies write is says fail.
|
|
|
|
|
Logged
|
|
|
|
EELSUPNSIDEU
Newbie
Karma: +0/-0
Offline
Posts: 9
|
|
« Reply #657 on: April 08, 2017, 09:52:47 PM »
|
|
|
i cant figure out why this keeps failing verify write
|
|
|
|
|
Logged
|
|
|
|
QuickS4
Full Member
Karma: +6/-6
Offline
Posts: 72
|
|
« Reply #658 on: April 08, 2017, 10:29:15 PM »
|
|
|
i cant figure out why this keeps failing verify write
I had the same problem. For me, it was putting eeprom into boot mode. I had two ecu's one night, both had exactly the same issue. Not sure if it was the particular ecu's or me. Using the GUI was great. But needed to use the newest version. These two ecu's seemed to not enjoy boot mode. Pita for sure. Sent from my Pixel XL using Tapatalk |
|
|
|
|
Logged
|
|
|
|
EELSUPNSIDEU
Newbie
Karma: +0/-0
Offline
Posts: 9
|
|
« Reply #659 on: April 12, 2017, 03:55:29 PM »
|
|
|
I tried the earlier version and it wrote fine. i kept trying to read my flash bin after flashing my eeprom while it was on the bench and i must have missed the information the the ecu really like being in the car while reading/writing. I successfully immo off my 06A906032NK and wrote an 06A906032HS bin file and my car started and ran. I was so ecstatic when it didn't die. So if anyone wants to know since I couldn't get a definitive answer.... the 032HS and the 032NK ECUs are compatible.
|
|
|
|
|
Logged
|
|
|
|
|
