Pages: [1] 2
Author Topic: Bricked ME7.5 ECU, won't go bootmode, tried everything  (Read 15032 times)
geos3
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 17


« on: July 05, 2020, 02:57:09 AM »

Hello, newbie here.
Long story short, I flashed with Nefmoto software this ECU about 15 times. Everytime checksum was checked and corrected with ECM Ti. Normaly I would change maps with tuner pro and then check it with ECM. Last time I downloaded Tuner Pro plug in from MTX Electronix, so it should have corrected it I guess. ECM said checksum was fine, but the file was modified and changes not saved. Everytime I saved those changes and then flash. This time I just checked and not saved changes.
Not the worst part. I tried Galetto with two cables. Both have I what looks like fake FTDI chips, but worked fine with VCDS and Nefmoto. I did search and read many topics on this forum, but to no help. Just says "BOOTMODE INACTIVE" Tried with 2 laptops, Win 7 x64 and XP.
Any suggestions? Desolder 95040 on bottom and then try?0101viber-image-2020-07-05-11-51-52" border="0
0102viber-image-2020-07-05-11-51-51" border="0
Logged
geos3
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 17


« Reply #1 on: July 05, 2020, 05:51:49 AM »

Sorry for the mess on pictures. Can anybody please comment on setup. Is everything connected right?
Logged
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12270


WWW
« Reply #2 on: July 05, 2020, 09:41:40 AM »

No idea.

What have you tried for bootmode?

Why not use ME7Sum to make sure your csums are correct?
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
geos3
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 17


« Reply #3 on: July 05, 2020, 12:07:54 PM »

I was lazy checking two times, and learned lesson the hard way.

me7check v1.12 (c) mki, 06/2004-05/2012
Checking file c:\000\T.bin (size=1048576)
Reading Version Strings...
-> Bootrom Version = 05.12
-> EPK = 40/1/ME7.5/5/4018.20//24B/Dst01o/140801//
-> Contents of ECUID data table:
   - '0261207751'         (SSECUHN)
   - '1037362999'         (SSECUSN)
   - '8N0906018BH '       (VAG part number)
   - '0001'               (VAG sw number)
   - '1.8L R4/5VT     '   (engine id)
-> Contents of ECUID data table:
   - 'HW_MAN004'

Page checksum failure(s) found
Data area checksum failure(s) found
-> Found 6 errors!!!   *******************************
So checksum was wrong, and I need to go to bootmode now. Seems that it is rare for ECU to fry-brick itself for good. But for me it is a little nightmare. Is it possible that I must use galetto cable only? No FDTI chip mod
Logged
adam-
Hero Member
*****

Karma: +124/-33
Offline Offline

Posts: 2179


« Reply #4 on: July 05, 2020, 12:14:18 PM »

Power Pin 121.
Logged
geos3
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 17


« Reply #5 on: July 05, 2020, 12:18:50 PM »

Power Pin 121.
Engine control relay. Ok, will try that. Thanks for fast reply  Smiley
Logged
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12270


WWW
« Reply #6 on: July 05, 2020, 01:00:30 PM »

Why are you not using ME7Sum?
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12270


WWW
« Reply #7 on: July 05, 2020, 01:01:33 PM »

Is it possible that I must use galetto cable only? No FDTI chip mod


If you are using the galletto tool you have to use a galletto cable or hexedit the tool.
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
BlackT
Hero Member
*****

Karma: +79/-40
Offline Offline

Posts: 1425



« Reply #8 on: July 05, 2020, 04:04:46 PM »

Power Pin 121.
Noo, powering pin 121 von't let ECU to get in boot mode.
Boot mode is done without powering 121 pin.

To OP, can you read eeprom in boot mode?
Logged
geos3
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 17


« Reply #9 on: July 05, 2020, 08:28:31 PM »

If you are using the galletto tool you have to use a galletto cable or hexedit the tool.
I did edit the cable with mprog3.5 in case of plain OBD cable. I also hex edit software in case of VCDS clone. Both of them try to connect, but Galetto sowtware says BOOTMODE INACTIVE.
me7-eeprom-1.40:
"... FAIL error =0x21007 "
Looks like OBD can't access boot mode. Is galetto cable somehow different hardware wise? I made it work with these cables. If not modded, sowtware would write "OPENING PORT IMPOSSIBLE"
Logged
geos3
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 17


« Reply #10 on: July 05, 2020, 08:53:47 PM »

Does anyone know what is power consumption of this ecu when on bench? On this setup, it is 0.285A @ 13.5V. Is this normal?
Also , chip circled red, heats a little (about 55C). Main chip Infineon heats about 48C)
viber-image-2020-07-06-05-31-080202" border="0
Logged
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12270


WWW
« Reply #11 on: July 05, 2020, 10:02:45 PM »

describe how you are trying to get to boot mode
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
geos3
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 17


« Reply #12 on: July 05, 2020, 10:46:51 PM »

describe how you are trying to get to boot mode
I connected cable as on pictures, that is ECU side: ground at pins (1,2), + is an pins (3,21,62), kline (43)
on cable side ground  (4,5), + (16), k line (7)
While powering on, ground pin 24 at mass - and after 5 seconds remove that.
Funny thing, I can see it reacts whan I ground 24, seeing powersupply adds 0,001Amp or so. Also, I see on some youtube clip that ecu from 2001 draws 0,19Amp which is less. I also remember that first time I tried it also showed 0,19 for sec or so, and then went up to current level of 0,29Amp. Maybe some component failed, but there are to clues on board like overheating or burn traces
Logged
BlackT
Hero Member
*****

Karma: +79/-40
Offline Offline

Posts: 1425



« Reply #13 on: July 06, 2020, 12:25:08 AM »

I have about 0.2amp in normal mode, and 0.17 in boot mode. 12.00V
The main MCU and chip you point are heating as you described.
HINT: I don't put power to pin 21, that is pin get 12V tru the relay coil, I don't see any ponit to feed 12V directly to that pin.
I done many ME7 ECUs of all kind (only I never had a ME 7.1.1 on bench) and never have need to power that pin.
When I do boot mode, I only power pin 3 and pin 62,
When I flash with nefmoto i put aditional 12 V to pin 121
« Last Edit: July 06, 2020, 12:35:50 AM by BlackT » Logged
geos3
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 17


« Reply #14 on: July 06, 2020, 12:49:58 AM »

Yes, it seems that 0,17-0,19 is normal draw. That is what I saw first time I powered it. Then is shoot up to 0,28 and stayed there. It seems that ECU is still alive but something is in the way. Really strange not to be able to enter boot mode, or connecting to ecu in right way.
Can you tell me if I change ECU, do I have to resolde 95040 chip which as I understood, contains IMMO data for ECU to pair with cluster IMMO
Logged
Pages: [1] 2
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.023 seconds with 17 queries. (Pretty URLs adds 0.001s, 0q)