Title: Can't read ME7.5 Passat ECU
Post by: MadCow on December 20, 2012, 08:34:44 PM
I picked up a 4B0906018CM ECU at a junkyard, I was able to flash the EEPROM in boot mode and disable the immobilizer but I can't get Nefmoto flasher to read the flash. Trying to read through KWP2000 I get: Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Sending start communication request.
Connected
Disabling Windows sleep mode.
Reading ECU flash memory.
ECU reports programming session preconditions have been met.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Starting diagnostic session.
Disconnecting because no response was received for the Tester Present message.
Disconnected
Reading ECU flash memory failed.
100% complete.
Restoring Windows sleep mode.
While boot mode crashes right after Sending baud detection byte. I can connect to it through vcds no problems too, it seems like Nefmoto flasher just doesn't want to cooperate. I'm using a VAG KKL cable with a FT232R. Is this an issue with my cable/setup or the software itself? I've tried multiple baud rates and fast/slow init with no change.
Title: Re: Can't read ME7.5 Passat ECU
Post by: ddillenger on December 20, 2012, 08:57:57 PM
Attach the log file, not just the parts displayed. That should give a much better picture of what's going on. Open your log file (File, open log file) and attach the section that starts at your most recent flash attempt.
Title: Re: Can't read ME7.5 Passat ECU
Post by: k0mpresd on December 20, 2012, 10:11:53 PM
get a better cable. nefmoto is flakey at best. i flash 018cm´s all the time. :)
Title: Re: Can't read ME7.5 Passat ECU
Post by: MadCow on December 21, 2012, 10:20:22 AM
Didn't realize there was a detailed log file, I cleared it and tried flashing again. 21/Dec/2012 12:11:25.478: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
21/Dec/2012 12:11:25.479: USER: Switching to KWP2000 session.
21/Dec/2012 12:11:25.542: LOG: Opened FTDI device.
21/Dec/2012 12:11:25.543: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A400g8zx Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
21/Dec/2012 12:11:25.543: LOG: FTDI ChipID DLL is loaded, checking chip ID...
21/Dec/2012 12:11:25.550: LOG: FTDI device chip ID: 0x16032FD5
21/Dec/2012 12:11:25.596: USER: Validated FTDI device is in dumb mode.
21/Dec/2012 12:11:25.613: LOG: Starting send receive thread.
21/Dec/2012 12:11:25.614: LOG: Send receive thread now started.
21/Dec/2012 12:11:25.614: USER: Disconnected
21/Dec/2012 12:11:25.644: LOG: Setting communication timings to defaults.
21/Dec/2012 12:11:25.645: LOG: Set timing parameters to defaults.
21/Dec/2012 12:11:25.645: USER: Connecting...
21/Dec/2012 12:11:25.666: LOG: Setting communication timings to defaults.
21/Dec/2012 12:11:25.667: USER: Starting slow init connection.
21/Dec/2012 12:11:28.270: USER: Connecting to address 0x01.
21/Dec/2012 12:11:30.453: USER: Slow init succeeded.
21/Dec/2012 12:11:30.453: LOG: Setting Address: 0x01 KeyByte1: 0x6F KeyByte2: 0x0F
21/Dec/2012 12:11:30.454: USER: Switching to KWP2000 session.
21/Dec/2012 12:11:30.454: USER: Connected
21/Dec/2012 12:11:32.980: LOG: Sent message with service ID TesterPresent
21/Dec/2012 12:11:33.018: LOG: Received message with service ID: TesterPresentPositiveReponse
21/Dec/2012 12:11:34.769: LOG: User Prompt - Title: Confirm Full Read ECU Flash Memory Message: If you are ready to read, confirm the following things:
1) You have loaded a valid memory layout for the ECU.
2) The engine is not running.
Note: Some non-standard flash memory chips may prevent reading the flash memory.
Click OK to confirm, otherwise Cancel. Result: OK
21/Dec/2012 12:11:34.769: USER: Disabling Windows sleep mode.
21/Dec/2012 12:11:34.783: USER: Reading ECU flash memory.
21/Dec/2012 12:11:34.803: LOG: Reading ECU identification option: 0x9C
21/Dec/2012 12:11:34.838: LOG: Sent message with service ID ReadECUIdentification
21/Dec/2012 12:11:34.884: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
21/Dec/2012 12:11:34.885: USER: Failed to start diagnostic session.
21/Dec/2012 12:11:34.885: LOG: Received unhandled message with service ID: ReadECUIdentificationPositiveResponse
21/Dec/2012 12:11:34.885: LOG: Read ECU identification option: 0x9C
21/Dec/2012 12:11:34.885: LOG: Successfully read ECU identification information
21/Dec/2012 12:11:34.886: USER: ECU reports programming session preconditions have been met.
21/Dec/2012 12:11:34.886: USER: Negotiating communication timings.
21/Dec/2012 12:11:34.886: LOG: Reading current communication timings.
21/Dec/2012 12:11:34.947: LOG: Sent message with service ID AccessTimingParameters
21/Dec/2012 12:11:34.994: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
21/Dec/2012 12:11:34.994: LOG: Set timing parameters to new values.
21/Dec/2012 12:11:34.994: LOG: Setting communication timing to defaults.
21/Dec/2012 12:11:35.052: LOG: Sent message with service ID AccessTimingParameters
21/Dec/2012 12:11:35.090: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
21/Dec/2012 12:11:35.090: LOG: Reading current communication timings.
21/Dec/2012 12:11:35.156: LOG: Sent message with service ID AccessTimingParameters
21/Dec/2012 12:11:35.196: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
21/Dec/2012 12:11:35.196: USER: Successfully changed to new communication timings.
21/Dec/2012 12:11:35.196: USER: Requesting security access.
21/Dec/2012 12:11:35.231: LOG: Sent message with service ID SecurityAccess
21/Dec/2012 12:11:35.276: LOG: Received message with service ID: SecurityAccessPositiveResponse
21/Dec/2012 12:11:35.276: LOG: Received security seed, sending security key.
21/Dec/2012 12:11:35.330: LOG: Sent message with service ID SecurityAccess
21/Dec/2012 12:11:35.374: LOG: Received message with service ID: SecurityAccessPositiveResponse
21/Dec/2012 12:11:35.374: USER: Security access granted.
21/Dec/2012 12:11:35.375: LOG: Starting ProgrammingSession diagnostic session with 124800 baud rate.
21/Dec/2012 12:11:35.375: USER: Starting diagnostic session.
21/Dec/2012 12:11:35.410: LOG: Sent message with service ID StartDiagnosticSession
21/Dec/2012 12:11:35.454: LOG: Received message with service ID: NegativeResponse
21/Dec/2012 12:11:35.454: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
21/Dec/2012 12:11:35.494: LOG: Received message with service ID: NegativeResponse
21/Dec/2012 12:11:35.494: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
21/Dec/2012 12:11:35.534: LOG: Received message with service ID: NegativeResponse
21/Dec/2012 12:11:35.534: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
(Repeats a whole bunch of times)
21/Dec/2012 12:11:45.431: LOG: Sent message with service ID TesterPresent
21/Dec/2012 12:11:45.534: LOG: Message received no replies.
21/Dec/2012 12:11:45.534: LOG: Resending message. Send attempts: 2
21/Dec/2012 12:11:45.553: LOG: Sent message with service ID TesterPresent
21/Dec/2012 12:11:45.656: LOG: Message received no replies.
21/Dec/2012 12:11:45.656: LOG: Resending message. Send attempts: 3
21/Dec/2012 12:11:45.675: LOG: Sent message with service ID TesterPresent
21/Dec/2012 12:11:45.777: LOG: Message received no replies.
21/Dec/2012 12:11:45.777: LOG: Failed to send message 3 times, message send failed.
21/Dec/2012 12:11:45.777: USER: Disconnecting because no response was received for the Tester Present message.
21/Dec/2012 12:11:45.777: USER: Disconnected
21/Dec/2012 12:11:45.785: USER: Reading ECU flash memory failed.
21/Dec/2012 12:11:45.799: LOG: Closing FTDI device.
21/Dec/2012 12:11:45.804: LOG: Send receive thread now terminated.
21/Dec/2012 12:11:46.913: LOG: User Prompt - Title: Reading ECU Flash Memory Complete Message: Reading ECU flash memory failed. Result: OK
21/Dec/2012 12:11:46.917: USER: 100% complete.
21/Dec/2012 12:11:46.922: USER: Restoring Windows sleep mode.
|