Pages: [1] 2 3 ... 6
Author Topic: Boot mode not possible on ME7.5 (Infineon CPU)?  (Read 37427 times)
Nottingham
Full Member
***

Karma: +12/-1
Offline Offline

Posts: 204


« on: February 26, 2012, 10:34:25 AM »

Frankly I am getting quite desperate here...

I have a 06A906032RP (0261208521) ECU from a Ibiza Cupra, which I cannot get into the boot mode.
I have already tried everything I can imagine; different versions of Galletto program, different FTDI drivers, three different computers, resistors with different values (0ohm - 100k ohm), etc. Yet neither Galletto (boot mode inactive) or Nefmoto can connect in boot mode  Angry Nefmoto flasher connects in normal mode thou...

Someone else here in Nefmoto had exactly the same problems with this specific ECU.

I cannot see anything else being different compared to other ME7.5 ECUs I have seen, besides the CPU.
In this ECU it is made by Infineon (B00017) instead of Siemens.

So far it seems this ECU is impenetrable.
It cannot be read (RequestUpload rejected) or flashed(?) since the memory layout cannot be verified.

Any ideas?

Logged
professor
Sr. Member
****

Karma: +23/-0
Offline Offline

Posts: 408



« Reply #1 on: February 26, 2012, 01:13:38 PM »

Why you wanna put the ECU in boot mode? After flash failure?

I guess you ground the right boot pin.
Logged

Seat Ibiza MK4 Cupra 1.8t 20V, stg3.
"Those 1.8T 20V machines are really tough" ©
Nottingham
Full Member
***

Karma: +12/-1
Offline Offline

Posts: 204


« Reply #2 on: February 26, 2012, 04:10:06 PM »

I have tried all the possible places (alternatives) for the boot pin, I tracked them with a multimeter.
Logged
Nottingham
Full Member
***

Karma: +12/-1
Offline Offline

Posts: 204


« Reply #3 on: February 27, 2012, 12:43:44 AM »

It seems the ECU is in boot mode.
Nefmoto flasher cannot connect in normal mode:

Code:
27.helmi.2012 09:20:01.524: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.2.3
27.helmi.2012 09:20:04.649: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
27.helmi.2012 09:20:04.674: LOG: Opened FTDI device.
27.helmi.2012 09:20:04.674: LOG: FTDI device info - Description: VAG K+CAN Serial Number: A6007dAe Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
27.helmi.2012 09:20:04.674: LOG: FTDI ChipID DLL is loaded, checking chip ID...
27.helmi.2012 09:20:04.677: LOG: FTDI device chip ID: 0xC80FE7F9
27.helmi.2012 09:20:04.704: USER: Validated FTDI device is in dumb mode.
27.helmi.2012 09:20:04.707: LOG: Starting send receive thread.
27.helmi.2012 09:20:04.711: LOG: Send receive thread now started.
27.helmi.2012 09:20:04.712: USER: Disconnected
27.helmi.2012 09:20:04.737: LOG: Setting communication timings to defaults.
27.helmi.2012 09:20:04.738: LOG: Set timing parameters to defaults.
27.helmi.2012 09:20:04.738: USER: Connecting...
27.helmi.2012 09:20:04.752: LOG: Setting communication timings to defaults.
27.helmi.2012 09:20:04.754: USER: Starting slow init connection.
27.helmi.2012 09:20:07.354: USER: Connecting to address 0x01.
27.helmi.2012 09:20:10.161: LOG: Failed to read sync byte, guessing baud rate is actually 9600.
27.helmi.2012 09:20:10.203: LOG: Not enough key bytes, read: 0
27.helmi.2012 09:20:10.211: USER: Slow init failed.
27.helmi.2012 09:20:10.211: USER: Disconnected
27.helmi.2012 09:20:10.227: LOG: Setting communication timings to defaults.
27.helmi.2012 09:20:10.227: USER: Connecting...
27.helmi.2012 09:20:10.238: LOG: Setting communication timings to defaults.
27.helmi.2012 09:20:10.238: USER: Starting slow init connection.
27.helmi.2012 09:20:12.838: USER: Connecting to address 0x01.
27.helmi.2012 09:20:15.641: LOG: Failed to read sync byte, guessing baud rate is actually 9600.
27.helmi.2012 09:20:15.683: LOG: Not enough key bytes, read: 0
27.helmi.2012 09:20:15.690: USER: Slow init failed.
27.helmi.2012 09:20:15.691: USER: Disconnected
27.helmi.2012 09:20:15.701: LOG: Setting communication timings to defaults.
27.helmi.2012 09:20:15.702: USER: Connecting...
27.helmi.2012 09:20:15.712: LOG: Setting communication timings to defaults.
27.helmi.2012 09:20:15.713: USER: Starting slow init connection.
27.helmi.2012 09:20:18.313: USER: Connecting to address 0x01.
27.helmi.2012 09:20:21.115: LOG: Failed to read sync byte, guessing baud rate is actually 9600.
27.helmi.2012 09:20:21.157: LOG: Not enough key bytes, read: 0
27.helmi.2012 09:20:21.165: USER: Slow init failed.
27.helmi.2012 09:20:21.165: USER: Disconnected
27.helmi.2012 09:20:21.176: LOG: Setting communication timings to defaults.
27.helmi.2012 09:20:21.179: LOG: Closing FTDI device.
27.helmi.2012 09:20:21.188: LOG: Send receive thread now terminated.
27.helmi.2012 09:20:28.946: LOG: Closing NefMoto VW Audi ME7 Flasher Logger 1.9.2.3

But neither in boot mode....

Code:
27.helmi.2012 09:18:49.384: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.2.3
27.helmi.2012 09:19:02.128: LOG: Opened FTDI device.
27.helmi.2012 09:19:02.128: LOG: FTDI device info - Description: VAG K+CAN Serial Number: A6007dAe Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
27.helmi.2012 09:19:02.128: LOG: FTDI ChipID DLL is loaded, checking chip ID...
27.helmi.2012 09:19:02.131: LOG: FTDI device chip ID: 0xC80FE7F9
27.helmi.2012 09:19:02.148: LOG: Starting send receive thread.
27.helmi.2012 09:19:02.149: LOG: Send receive thread now started.
27.helmi.2012 09:19:02.150: USER: Disconnected
27.helmi.2012 09:19:02.161: USER: Connecting...
27.helmi.2012 09:19:02.185: USER: Starting bootstrap loader upload.
27.helmi.2012 09:19:02.189: USER: Sent bootstrap init zero byte.
27.helmi.2012 09:19:05.193: USER: Sent bootstrap init zero byte.
27.helmi.2012 09:19:08.196: USER: Sent bootstrap init zero byte.
27.helmi.2012 09:19:11.196: USER: Bootstrap loader upload failed. Failed to receive device ID response for init zero byte.
27.helmi.2012 09:19:11.196: USER: Disconnected
27.helmi.2012 09:19:11.204: USER: Connecting...
27.helmi.2012 09:19:11.211: USER: Starting bootstrap loader upload.
27.helmi.2012 09:19:11.214: USER: Sent bootstrap init zero byte.
27.helmi.2012 09:19:14.217: USER: Sent bootstrap init zero byte.
27.helmi.2012 09:19:17.220: USER: Sent bootstrap init zero byte.
27.helmi.2012 09:19:20.220: USER: Bootstrap loader upload failed. Failed to receive device ID response for init zero byte.
27.helmi.2012 09:19:20.220: USER: Disconnected
27.helmi.2012 09:19:20.228: USER: Connecting...
27.helmi.2012 09:19:20.235: USER: Starting bootstrap loader upload.
27.helmi.2012 09:19:20.238: USER: Sent bootstrap init zero byte.
27.helmi.2012 09:19:23.241: USER: Sent bootstrap init zero byte.
27.helmi.2012 09:19:26.245: USER: Sent bootstrap init zero byte.
27.helmi.2012 09:19:28.246: USER: Bootstrap loader upload failed. Failed to receive device ID response for init zero byte.
27.helmi.2012 09:19:28.246: USER: Disconnected
27.helmi.2012 09:19:28.256: LOG: Closing FTDI device.
27.helmi.2012 09:19:28.265: LOG: Send receive thread now terminated.
27.helmi.2012 09:19:58.304: LOG: Closing NefMoto VW Audi ME7 Flasher Logger 1.9.2.3

Without the boot mode Nefmoto flasher connects fine in normal mode.
Logged
professor
Sr. Member
****

Karma: +23/-0
Offline Offline

Posts: 408



« Reply #4 on: February 27, 2012, 01:20:44 AM »

I am asking the same, why did you want to put the ECU in boot mode? After flash failure? Or something else?

Also the fact that memory layout can not be verified perhaps shows that 29F800BB is corrupted.

BTW i get the same nefmoto boot mode messages.
Logged

Seat Ibiza MK4 Cupra 1.8t 20V, stg3.
"Those 1.8T 20V machines are really tough" ©
Nottingham
Full Member
***

Karma: +12/-1
Offline Offline

Posts: 204


« Reply #5 on: February 27, 2012, 01:28:46 AM »

The car probably has a expired aftermarket trial I want to get rid of.
Atleast I want to know what is it.

The ECU is otherwise working fine.
Logged
pvl
Sr. Member
****

Karma: +31/-0
Offline Offline

Posts: 350


« Reply #6 on: February 27, 2012, 02:13:50 AM »

There's nothing like a crypted flashromsocket soldered into the ecu, right ? plain obd2-programmed stuff ?

Picture of internals please.
Logged
Nottingham
Full Member
***

Karma: +12/-1
Offline Offline

Posts: 204


« Reply #7 on: February 27, 2012, 02:36:17 AM »

Just closed the casing, gave up eventually...
The ECU has never been opened before, no scratches anywhere and the seal string was intact.

Tried Minimon too, it cannot connect either.
Logged
Nottingham
Full Member
***

Karma: +12/-1
Offline Offline

Posts: 204


« Reply #8 on: February 27, 2012, 03:14:00 AM »

Pictures as attachment.
Logged
pvl
Sr. Member
****

Karma: +31/-0
Offline Offline

Posts: 350


« Reply #9 on: February 27, 2012, 03:38:55 AM »

Red : bootpin-pad
Blue : jumperwire

place or solder jumperwire with one side on the pad, or flashrompin.

temporarily ground the other side of the blue wire to the edge, like shown, while powering-on
the ecu. After 1 sec, release the jumperwire so it does not make contact anymore with ground.

fire up galetto software, choose bootmode 1MB chip / amd 800 and it should be possible to get a ecu-id.

I use the 1260 version. Never had ANY problem with bootmode. But it's not really needed. These can be
done with Kwp2000 on the bench or even better with MPPS on the bench or in the car via obd to rewrite.

I think the issue lays with powering-on and feeding all correct pins with power. I made myselfe a bench-
harness with switch to simulate ignition-key-switch. Works a treat.

Did you test your interface on other ecu's ? Is the interface o.k. ?

Logged
Nottingham
Full Member
***

Karma: +12/-1
Offline Offline

Posts: 204


« Reply #10 on: February 27, 2012, 03:51:54 AM »

Just triple checking: Pin 62 (12V) should be live (connected to 12V) before the bootpin is shorted to ground, and while the BP shorted the ECU is powered up by feeding 12V to the ignition (pin 3)?
Logged
pvl
Sr. Member
****

Karma: +31/-0
Offline Offline

Posts: 350


« Reply #11 on: February 27, 2012, 04:51:37 AM »

Reading back your posted logfile of nefmotoflasher :

FTDI device info - Description: VAG K+CAN Serial Number: A6007dAe Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0


HELLO... which USB-dongles does nefmoto support ?  Roll Eyes

NOT that dashboard-tool Wink 

Don't you have a cheap usb-KKL-dongle laying around ? Or a mate ?  Oh.. it won't work on the bench due to the immo.
Get a real tool, like MPPS V12 for this. A wise investment Wink

Regarding the chicken-interface (english translation for italian 'galletto') , the pinout for giving correct power to the ecu:

http://nefariousmotorsports.com/forum/index.php?topic=1541.msg14808#msg14808

I thought i didn't connect pin 21, as this is not needed, and never needed it anyway Wink

Pin 3 is defo switched 12v-ignitionkey. And that must be switchable, when appyling the temp-bridge-wire for bootmode-activation.

If you hook it up, like the picture from the thread, you are good to go. Also for vagcom-diagnosis (HINT !!!)

When this is not possible, with this pinout (vagcom-diagnosis on the bench) your ecu has big problems. I feed 12v directly from a
NEW carbattery and a charger feeding the battery. Most stable and good for flashing&testing ecu's.

You do have the galletto 1250 or 1260 obd2 dongle don't you ? As that K+CAN won't work with galletto-software...  Wink

Cheers,

PvL
Logged
Nottingham
Full Member
***

Karma: +12/-1
Offline Offline

Posts: 204


« Reply #12 on: February 27, 2012, 04:57:07 AM »

Thanks for making it fool proof, but the VAG K+CAN clone cable works fine with Nefmoto and other software that require a dumb interface Wink

And I do have a Galletto 1260 too, naturally.

In normal mode Nefmoto can connect and read the ECU information, however it cannot do anything else as Immo is enabled.

In boot mode, still neither Nefmoto or Galletto can connect.

I used the surrounding foil as a ground point like you suggested, everything however remains the same.
And I am switching the ignition signal so it should not be the issue.
Logged
pvl
Sr. Member
****

Karma: +31/-0
Offline Offline

Posts: 350


« Reply #13 on: February 27, 2012, 05:13:00 AM »

Hi,

Yes, just ruling-out any mistakes Wink  They are easily made with this stuff. Tho i had the luck i had instant success after doing homework...

Keep that pin 3  not powered, but the pin 62 is essential. thats the 'cleanup/backup power' .

It can be very well that you have a corrupted EEprom (the little 8pin 95040) on the BACK of the ecu, in the middle)) And therefore have
issues/difficulties getting into bootmode.

Is it possible to use your K+can software and do a dump of it ?  I had once a UK-ecu with a revo-trial on it. I guess that was thrown on ebay,
because it had similar issues like you just summed-up in the thread. I firstly reprogrammed the 95040 and then had no issues with Galletto
to enter bootmode. The eeprom was filled with Revo as text when trying to read the eeprom via vag-K-commander v1.4. Really funny to see.

So, hook-up power as sayed, bridge the bootpin to ground (and keep it bridged), witch-on simulating ignition (pin 3) undo the temp-bootpin-bridge
and fire-up galletto.

I prefer WIN-XP-SP3 NON virtual-pc machines for this. they ALWAYS work. Others : you can run into serious compatibility-issues, and keep on searching
the cause untill you grow a big beard in the meantime..... and found out what it was.... 

let's see if it now works Smiley

Logged
Nottingham
Full Member
***

Karma: +12/-1
Offline Offline

Posts: 204


« Reply #14 on: February 27, 2012, 06:00:44 AM »

Nope, still nothing.

Maybe it is possible to disable the boot mode by modifying the 32k uP code inside the CR167.
Revo (and most likely APR too) can atleast read the memory without even opening the ECU.
Maybe they can write it too.

Someone should debug their flashing programs and see what they do.
I don´t think the Revoread (Flash, 32k uP reader) is even protected.
Logged
Pages: [1] 2 3 ... 6
  Print  
 
Jump to:  

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