95040 EEPROM memory dump successful?

Pages: [1]

« previous next »

Author

Topic: 95040 EEPROM memory dump successful? (Read 1157 times)

WannabeCupra

Newbie

Karma: +0/-0
Offline

Offline

Posts: 21

	95040 EEPROM memory dump successful? « on: September 24, 2024, 01:15:26 AM »

I got myself a used ECU to convert my APP 1.8t Leon to Wideband.
Just trying to get things to work and disable Immo, I was able to read the 95040 memory and dump it to a file yesterday.

Before I proceed to turn off immo I wanted to ask whether the dump was complete and successful? I read a few things that sometimes the file can be incomplete, and I want to be sure not to brick the ECU.

If the dump is not okay to flash back on the EEPROM I would continue with the ECU Pin I got from the dump.

ECU is:
06A 906 032 HQ
0 261 207 442

out of a 10/2002 A3 1.8t AUQ


	Logged

WannabeCupra

Newbie

Karma: +0/-0
Offline

Offline

Posts: 21

	Re: 95040 EEPROM memory dump successful? « Reply #1 on: September 24, 2024, 01:20:34 AM »

Sry for double post, just edited the file to turn immo off.
Attached it to the post, would love some feedback if I did it correctly

Thanks!


	Logged

WannabeCupra

Newbie

Karma: +0/-0
Offline

Offline

Posts: 21

	Re: 95040 EEPROM memory dump successful? « Reply #2 on: September 24, 2024, 11:09:36 AM »

Okay, I checked with different 95040 mem dumps from different members and am confident the original memory dump is fine.
So I proceeded and flashed my self-made immo-off bin.

Flash was successful, so I would assume I can now read the flash with the ECU in bench mode?

I get this error though:

Code:

Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: °6A906032HQ 1.8L R4/5VT     G   0002
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Connected
Reading ECU flash memory.
ECU reports programming session preconditions have been met.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
ECU reports that security access request was rejected.
Starting diagnostic session.
Disconnecting because no response was received for the Tester Present message.
Disconnected
Reading ECU flash memory failed.
100% complete.

Is that expected? I think Ill try to install the ECU back in the car next if I cant get it to work...

EDIT:
Got it to read the flash in bench mode by also powering Pin 121 of the ECU (http://nefariousmotorsports.com/forum/index.php?topic=6324.0)


« Last Edit: September 24, 2024, 11:26:17 AM by WannabeCupra »	Logged

Pages: [1]

« previous next »

Jump to:

Navigation

Personal Tools

November 22, 2024, 08:36:01 PM

Welcome, Guest. Please login or register.
Did you miss your activation email?

Navigation

Personal Tools

Search