NefMoto

Hi guys, I need some help sorting out my ST10 ME7.1.1 40Mhz type 2, off an R32  mk5 golf.  As a hobby, I want to remap my car, so I purchased an exact match of my ECU from a wrecker.  On the bench, in normal mode it communicates via K line very well with my clone VCDS. It only partially works with a galletto 1260 clone, stalling at 60%.  It didn't at all work with a china kess v2 (didnt try it with CAN, just K).

My main problem is boot mode. I want to back up the flash. After a whole week of trying everything I found on forums I don't know what the problem is but I can't get bootmode to communicate with the galletto clone, or kess v2 clone or ME7eeprom.exe using either the galletto or vcds cables (Me7eeprom connects to computer  VCP com port ok but can't connect to ecu). In bootmode the only communication is with vcds. VCDS connects but has blank or asterixes where normally the ecu info would appear. ( In normal boot  mode VCDS works perfectly) The only way i was able to get it into what i think is this  bootmode was by grounding the flash pin at boot for some seconds. Resistors to ground with or without using a switch for pin 3 to 12v simply booted in normal mode. I tried all methods on the net I could find for this type 2 st10 40Mhz.
So, my question is, how do I know if the china junk is the problem or the ecu has been professionally remapped and is protected or if its me getting it into some weird mode but not the real bootmode? Ive got an oscilloscope but can't afford real tools just for one small hobby, and im not going to remove the flash as I'm not that brave! Btw, I removed and copied the 95160  eeprom  and noticed nothing with the characters revo, giac etc, but I'm no expert.
I can waste more money and get a MPPS clone but is that going :'( to help?
Please give me some ideas!
Cheers

me7eeprom will not read with a galeto cable. It will read with a basic FTDI cable. I juggle 2 cables when prepping stuff for this reason.

me7.1.1 has to have the 000 resistor modified

attached is a post with the resistor marked in attached images

http://nefariousmotorsports.com/forum/index.php?topic=6383.0

Hi Auriaka,

Thanks for the advice, I'll check the board on Monday and report back! I came across a photo, with a 000 resistor that needed removal, but the board was not like mine.
Cheers.

My board looks different, but I removed the 000 resistor that appeared very close to the one in the picture in the link.
The ecu doesn't work with that removed. No comms with vcds without pin 24 grounded and no galletto when grounded.
I replaced it with a 1.8k resistor and the ecu works again with normal boot, but no luck in getting into bootmode. It still gets into some mode where communication with vcds is possible but no info is exchaged. No luck with galletto. I tried grounding pin 24 from intervals of 0 to 10 seconds when I apply power to all three +ve wires but it simply goes into that strange mode.
Real bootmode shouldn't connect to vcds with the kwp2000 as far as I understand? Whats going on here?

vcds wont work in bootmode at all. Thats successful

But it finds the controller and the green and reds lights flash. If I disconnect the Kline it comes up with an error that the engine module is not found. Is that normal for bootmode or should VCDS not connect at all and give an error?

VCDS cannot talk to an ECU in bootmode. Not sure what you're trying to do.

I'm trying to detect if I have the ecu in bootmode or not. I only have clone galletto and vcds.  I have never tried galletto so I don't know if it works but it keeps saying that the ecu is not in bootmode.

I'm hoping that VCDS wont connect so I can say that I have it in bootmode and its the galletto that isnt working.

What is happening instead is that VCDS does indeed connect and communicates but has no data to display. So what mode is the ecu in? Bootmode or normal mode with no access to  internal data? Does the bootmode have any kpw2000 capability at all because the mode I seem to get it in does according to VCDS although blank data is sent back to VCDS.

Whitch pins you have connected on ECU? How do you try to do boot mode?

Pins 3,21,62 positive 13.8V
Pin 2 0V
Pin43 K-line

Switch power with pin 24 of the flash at 0V, disconnect after an instant, then if no good, switch off and keep the pin at 0V for 1 second, if no good repeat 2 seconds etc. Up to 10s. after that I kept it permanently at 0V.
I always makes it go into a dumb mode, not bootmode.

 I think I'm not in boot mode at all. I hooked up the ocilloscope to the K Line and monitored signals.  Using Galletto in the audi 7.1.1 bootmode selection, a negative pulse about 80us is sent to the ECU and nothing comes back. Then, with me7eeprom.exe usiing the vcds cable in dumb mode a 500us negative pulse is sent and again no response from the ecu.
The ecu responds only the KWP 'wakeup' protocol pulses, which are much wider. So grounding pin 24 is not doing what it is supposed to do.

I wonder if the  P0L.4 pin of the ST10 is actually taken low enough when pin 24 of the 29F800 is grounded on this silly board.

Ok, I managed to get it into bootmode each and every time i tried (about 20 times).
Using the oscilloscope I discovered that pin 105 of ST10 (P0L.5) was kept at 0V while the it was being reset (when power is  switched on). This prevents the ECU from ever going into bootmode. I removed the 6.8K resistor near that pin. This allows the pin to get the positive voltage it needs. Also, instead of shorting the pad connected to pin 104 to ground (same as grounding pin 24 of the 29F800 but more elegant) I used a 8.3k resistor (4.7k and 10k also worked), which allows the pin to keep doing its job after the booting process. The resistor can be left there or removed after 10 seconds. The 000 resistor removed in my photo above was put back - dont remove it!

Galletto takes less than 3 minutes to read or write the 1M flash.
Boots normal when pin 24 is not grounded by resistor.

ECU is 022906032KG , if anyone in the future searches this post...

Thank you for the update. It is extremely helpful when people follow up and provide solutions.

Also, thanks for confirming you can use a pulldown on P0L.4 and it will continue to function properly. I had been meaning to try it but never did.

For people installing a switch for bootmode, this can be extremely helpful since it means a momentary isn't needed.

Awesome and detailed info, thank you very much :o

Hi guys,
Just to let you know that the ecu is back in the R32 and I am able to flash it in bootmode instead of kess or mpps. Galletto only takes 3 minutes!
 I added to the firewall a waterproof  switch that grounds, via a cable, the boot pin (with the 8k resistor). I also added a socket to feed a  12v source to the ecu pin 21. In essence, by disconnecting the battery and feeding the ecu  12v through two removed fuses in the fuse box  and powering galletto separately, bootmode comes up. So far I uploaded 6 crc checked maps in two days with no probs at all. I use vcds to log parameters since me7logger doesnt like 7.1.1 and use dragy gps, but  have plenty to learn to squeeze a few extra horses from the motor.

Thanks for the info. I am dealing with this problem now...I was working on it late last night (mistake), and I think I might of bricked it. It has no communication now. It could have been a funky ecm/ecu thanks eBay seller! I was trying the remove the 000 resistor thing, which didn't work, then I tried to resolder it back and maybe screwed something up.

I'm kinda visual, does this graphic (Image) summarize what you did? And I found this email in a Damos Dump. It talks about (2) Bootloader (and included)

Opps I sent before I was done typing. Here they are. It was translated from German.

https://docs.google.com/document/d/1bAyY5SHG0wliR4qt6LKVt5Vpq3nv-H_H/edit?usp=sharing&ouid=100639855418505537002&rtpof=true&sd=true

I believe so. Leave the zero ohm resistors alone on this board. Just remove the 6.8k and  ground the pad which goes to pin104 using a resistor (8.3 k works and is high enough to be kept grounded during galletto etc, etc), for bootmode. Never ground directly, don't risk it. Unground the 8.3k and reboot for normal operation

Thanks, I have (2) ecu's, and one is no longer communicating  >:(. I will give it a try!

I hope this will help someone unpack the bootmode, and reading the eeprom problems with the ME7.1.1's I did translate some as best as I could.

ST10 ME7.1.1 40Mhz and others

The email, the Quick Start Guide ST10 Boot Strap Loading (BSL) 2.1, and the powerpoint talks about problems making the change from 32mhz to 40mhz among other changes with URRAM "The "startup times" are now also having a negative impact on these projects". The Quick Start Guide ST10 Boot Strap Loading (BSL) 2.1 document seems to have a workaround to get it into bootmode item #8, and a diagram at the bottom. From what I gather they are shorting the CAN high and Low to activated bootmode via K-Line. The problem seems to be that raster is too fast, and it's causing a infinite loop.

Problem Description :
- EEPROM will not be read
- Communication is lost on the first clear command (infinite loop while)

https://drive.google.com/file/d/1TRbLDZe53LUWISimdcJcpOcf8AcN5_Ip/view?usp=sharing

I started a new topic at:

http://nefariousmotorsports.com/forum/index.php?topic=21179.0title=

My bad the schematic I was using is a ME7.1.1 C4 from a VR6. I need a C3. I looked at C2 but is different.

Take some valium mate! You're gonna blow up the next one too. There is a document or two online about st10 bootstrap. In one it tells you that some specific pins need to be high when attempting bootmode. All you need to do is to see if any resistors are grounding any of those pins with a multimeter, and remove them.Ìn mine the 6.8k was culprit.  Only then you use a resistor to ground the usual pin for bootmode.

Yes, I agree with you...last night I got the Tequila out  8) now all is well. I got the bad ecu working again, and I decided to pull the EEPROM, and read it!

Ps do you have a picture of the resistor location? Many thanks.

Upload a photo of your board. Top view, good focus. The board area around st10 pins #100 and up.

FYI I fixed (3) ecu's that where bad:

1. Not communicating after soldering that 000 resistor back on, so I replace with a 000 resistor of off a parts board, and re-soldered it, and the surrounding connections which fixed that problem.

2. Couldn't get into boot mode which was the pad connection to the trace (under the soldered boot wire) re-attached to pin #24 on Eprom.

3. Bad EEPROM someone tried to reflash to a manual, and it was a mess, downloaded original and flashed it.

Here is the original ECU that I couldn't get into boot (see) Picture, and it still won't go! I tried all times 3-10 seconds, with resistors 1kohm 4k ohm, 6.8K ohm, and straight to ground.

Thanks man! 

Looks like you have the other version, so my instructions don't count.Mine is for the one in me7.1.1 (3).jpg Have a look at the attachment, if you tried the 000 resistor and grounding the pin in the picture then there is a problem. Do make sure the 000 resistor you remove is EXACTLY in the same position as in the diagram!

Cool thanks.

Finally found "THE PROBLEM" partially working Blue KKL (CH341), Just for the hell of it!. I tried another "Blue" Cable (with a fake FTDI chip) Works on every thing so far.

Thanks again for the help!

i peeked into this thread the other week and  ??? didnt get the point of it.
is there any new information on here or is this all about wrong cables and existing manuals how to desolder which part

It's about the inability to learn from other's mistakes and inability to read instructions.
But I guess that's how some people are wired.