SteveKen
Newbie
Karma: +1/-1
 Offline
Posts: 20
|
 |
« on: August 19, 2011, 07:49:23 AM »
|
|
|
In an effort to experiment with different soft codes on my Audi RS6 ECU (Me7.1.1) I semi-bricked it.
Background: I'm a DIY'er using the cheap KWP2000+ interface and free vagme7 software (which doesn't require boot mode). I've had success with this hardware in the past on a previous S6 conversion project.
Anyway, I tried to flash the RS6 ECU with a stock A6 2.7T flash. The flash went through but when I powered it up in the car to VAG-COM it, the ECU module wasn't able to be detected.
Vagme7 can't detect the ECU and the NefMoto program (borrowed a friend's Win7 laptop) didn't see it either.
I'm thinking that the difference between Me7.1 (2.7T) versus Me7.1.1 (RS6) is the killing factor, or the fact that I had Me7.1.1 selected on the vagme7 flasher software when I uploaded it. Or lastly, it's just a bad flash.
I've never had any success bootstrapping the Me7.1.1 ECU either. All the techniques described of bootstrapping on the internet just don't work. Also is there a jumper "000" on the ECU that needs to be de-soldered for boot strapping? Either way, it doesn't work for me.
Aside from extracting the chip and plugging it into my willem programmer, I'm not sure what to do.
|
|
|
|
|
Logged
|
|
|
|
infinkc
Full Member
Karma: +6/-1
Offline
Posts: 94
|
|
« Reply #1 on: August 19, 2011, 08:33:13 AM »
|
|
|
know anyone local to you with a mpps cable, that might get it going. If not i think you will need to pull that eeprom.
|
|
|
|
|
Logged
|
|
|
|
|
Rick
|
|
« Reply #2 on: August 19, 2011, 10:00:04 AM »
|
|
|
Disconnect battery for a while, then reconnect and see if there is VAGCOM comms.
|
|
|
|
|
Logged
|
|
|
|
SteveKen
Newbie
Karma: +1/-1
Offline
Posts: 20
|
|
« Reply #3 on: August 19, 2011, 10:06:48 AM »
|
|
|
Disconnect battery for a while, then reconnect and see if there is VAGCOM comms.
No luck with this. I can see my other ECU with VAGCOM and swap in the other ECU and nothing. |
|
|
|
|
Logged
|
|
|
|
a200tq
Jr. Member
Karma: +2/-1
Offline
Posts: 45
|
|
« Reply #4 on: August 28, 2011, 01:26:17 PM »
|
|
|
This is just 5 minutes with bootmode, and all will be ok. I have 2 manuals for bootmode, but this manuals in russian language, so, i dont think this will be interesting to you.
|
|
|
|
|
Logged
|
|
|
|
|
julex
|
|
« Reply #5 on: September 02, 2011, 07:47:18 AM »
|
|
|
bootmode + galletto is the only savior here unless you can afford eeprom programmer with clip on connector and flash directly.
|
|
|
|
|
Logged
|
|
|
|
Tony@NefMoto
Administrator
Hero Member
Karma: +132/-4
Offline
Posts: 1389
2001.5 Audi S4 Stage 3
|
|
« Reply #6 on: September 15, 2011, 02:17:46 PM »
|
|
|
You need boot mode to recover ECUs that don't boot up.
Maybe if you describe how you are tying to enter boot mode, and post some pictures of what pins you are connecting we can tell you what to do differently.
|
|
|
|
|
Logged
|
|
|
|
SteveKen
Newbie
Karma: +1/-1
Offline
Posts: 20
|
|
« Reply #7 on: July 17, 2012, 09:26:01 AM »
|
|
|
I'm reviving this as I seemed to have locked up one of my spare RS6 ECUs this time.
ECU is an Me7.1.1 from a 2003 RS6
I've since bought an eBay Galletto cable and am still unable to get the stupid thing in boot mode.
Here's the procedure I'm using:
Bench cable using:
13.3V battery (30) power to pin 62 & 21
13.3V switched (15) power to pin 3 to simulate the ignition
ground to pins 1 & 2
K Line to pin 43
Turn on Galletto Software
Turn on battery power
ground boot pin
Turn on switched (15) power
Try to read ECU or connect
Can't connect.
I can't connect in boot mode with the NefMoto software either.
I've also tried this with and without the SMD "000" jumper on the back side of the ECU board.
Last time this happened I had to send the ECU out to have it de-soldered and flashed.
Am I doing something wrong here?
|
|
|
|
|
Logged
|
|
|
|
|
RaraK
|
|
« Reply #8 on: July 17, 2012, 09:40:25 AM »
|
|
|
which processor is it?
|
|
|
|
|
Logged
|
|
|
|
SteveKen
Newbie
Karma: +1/-1
Offline
Posts: 20
|
|
« Reply #9 on: July 17, 2012, 09:54:45 AM »
|
|
|
which processor is it?
Here's a picture of the eeprom and processor does this help?  |
|
|
|
|
Logged
|
|
|
|
|
gremlin
|
|
« Reply #10 on: July 17, 2012, 07:33:16 PM »
|
|
|
Turn on Galletto Software
Turn on battery power
ground boot pin
Turn on switched (15) power
Try to read ECU or connect
Can't connect.
Wrong way... Connect ALL power pins (3, 21, 62) on ECU together. Ground and K-line pins as before. Start software. Select ME7.x.x 29F800BB bootmode Press READ key. Select file for saving. Wait until message "...connect boot pin...bla-bla-bla..." appears (or somthing like that) Don't press [OK] at this moment!!! Connect boot wire to boot point on PCB. Switch ECU power ON. Disconnect boot wire. Now press [OK] in previous message window. Reading process will start... |
|
|
|
|
Logged
|
|
|
|
SteveKen
Newbie
Karma: +1/-1
Offline
Posts: 20
|
|
« Reply #11 on: July 17, 2012, 08:05:41 PM »
|
|
|
Wrong way...
Connect ALL power pins (3, 21, 62) on ECU together.
Ground and K-line pins as before.
Start software.
Select ME7.x.x 29F800BB bootmode
Press READ key.
Select file for saving.
Wait until message "...connect boot pin...bla-bla-bla..." appears (or somthing like that)
Don't press [OK] at this moment!!!
Connect boot wire to boot point on PCB.
Switch ECU power ON.
Disconnect boot wire.
Now press [OK] in previous message window.
Reading process will start...
Thanks for this. I will try again.on the bench tomorrow. Since I can't get the Galletto to connect to my good ecu with the nefmoto program, I'm thinking that I might have a driver conflict. I'm using the same laptop that I'm running VCDS on as well as my kwp2k+ flashtool. I deleted all the drivers and did another eobd2 driver install but still couldn't connect. Tomorrow I'll try it on a computer that never had anything related installed. Any other thoughts? |
|
|
|
|
Logged
|
|
|
|
SteveKen
Newbie
Karma: +1/-1
Offline
Posts: 20
|
|
« Reply #12 on: July 18, 2012, 10:31:35 AM »
|
|
|
Wrong way...
Connect ALL power pins (3, 21, 62) on ECU together.
Ground and K-line pins as before.
Start software.
Select ME7.x.x 29F800BB bootmode
Press READ key.
Select file for saving.
Wait until message "...connect boot pin...bla-bla-bla..." appears (or somthing like that)
Don't press [OK] at this moment!!!
Connect boot wire to boot point on PCB.
Switch ECU power ON.
Disconnect boot wire.
Now press [OK] in previous message window.
Reading process will start...
This did not work. Any other thoughts? Maybe a bad cable? |
|
|
|
|
Logged
|
|
|
|
a200tq
Jr. Member
Karma: +2/-1
Offline
Posts: 45
|
|
« Reply #13 on: July 18, 2012, 11:21:22 AM »
|
|
|
This did not work. Any other thoughts? Maybe a bad cable?
You can try to separate + source. Motronic pin 62 and galletto +pin together right to positive source, and motronic 3 pin and 21 pin through the switch on +source (ign. key on simulate). Look at the wire diagramm-in me711 pin 3 AND pin 21 (not 62!!) a powered up when ignition is on. |
|
|
|
|
Logged
|
|
|
|
SteveKen
Newbie
Karma: +1/-1
Offline
Posts: 20
|
|
« Reply #14 on: July 18, 2012, 11:35:12 AM »
|
|
|
You can try to separate + source. Motronic pin 62 and galletto +pin together right to positive source, and motronic 3 pin and 21 pin through the switch on +source (ign. key on simulate). Look at the wire diagramm-in me711 pin 3 AND pin 21 (not 62!!) a powered up when ignition is on.
I'm guessing that this isn't the issue either since I was unable to get it to work while in the car as well. No go on the bench and same for in the car. The only other option I can think of is the seiral numbers in the software and the chip do not match up. I would think that the NefMoto software woudl be able to connect at least. Instead I get: "Failed to read test echo from FTDI device" |
|
|
|
|
Logged
|
|
|
|
|
