ratherb1
Full Member
Karma: +5/-5
 Offline
Posts: 115
|
 |
« on: November 04, 2013, 10:19:13 AM »
|
|
|
first time out i try to flash and it said some about "ecu reports security blah blah" waiting for user to reconnect, i reconnect then it said something else.....i got nervous and cancelled.... does it say what i did wrong? is there supposed to be some prompts that come up during flashing?
this is a 2001 a6 tip t box flashing an L box tune
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting fast init connection.
Connecting to address 0x01.
Fast init sent, sending start communication request.
Switching to KWP2000 session.
Connected
Disabling Windows sleep mode.
Writing 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 is not supported.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Disconnecting because no response was received for the Tester Present message.
Disconnected
Writing ECU flash memory failed.
100% complete.
Restoring Windows sleep mode.
Switching to KWP2000 session.
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting fast init connection.
Connecting to address 0x01.
Fast init sent, sending start communication request.
Switching to KWP2000 session.
Connected
Disabling Windows sleep mode.
Writing 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 is not supported.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Disconnecting because no response was received for the Tester Present message.
Disconnected
Waiting for user to reconnect to ECU before continuing...
Waiting for user to reconnect to ECU before continuing...
Switching to KWP2000 session.
Validated FTDI device is in dumb mode.
Disconnected
Waiting for user to reconnect to ECU before continuing...
Connecting...
Starting fast init connection.
Connecting to address 0x01.
Fast init sent, sending start communication request.
Start communication request did not receive any response.
Disconnected
Waiting for user to reconnect to ECU before continuing...
Connecting...
Starting fast init connection.
Connecting to address 0x01.
Fast init sent, sending start communication request.
Start communication request did not receive any response.
Disconnected
Waiting for user to reconnect to ECU before continuing...
Connecting...
Starting fast init connection.
Connecting to address 0x01.
Fast init sent, sending start communication request.
Start communication request did not receive any response.
Disconnected
Waiting for user to reconnect to ECU before continuing...
Validated FTDI device is in dumb mode.
Disconnected
Waiting for user to reconnect to ECU before continuing...
Connecting...
Starting fast init connection.
Connecting to address 0x01.
Fast init sent, sending start communication request.
Start communication request did not receive any response.
Disconnected
Waiting for user to reconnect to ECU before continuing...
Connecting...
Starting fast init connection.
Connecting to address 0x01.
Fast init sent, sending start communication request.
Start communication request did not receive any response.
Disconnected
Waiting for user to reconnect to ECU before continuing...
Connecting...
Starting fast init connection.
Connecting to address 0x01.
Fast init sent, sending start communication request.
Start communication request did not receive any response.
Disconnected
Waiting for user to reconnect to ECU before continuing...
Cancelling current operation.
Writing ECU flash memory failed.
100% complete.
Restoring Windows sleep mode.
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting fast init connection.
Connecting to address 0x01.
Fast init sent, sending start communication request.
Switching to KWP2000 session.
Connected
Disconnecting because no response was received for the Tester Present message.
Disconnected
|
|
|
|
« Last Edit: November 04, 2013, 10:21:32 AM by ratherb1 »
|
Logged
|
-ROMIE
|
|
|
ratherb1
Full Member
Karma: +5/-5
Offline
Posts: 115
|
|
« Reply #1 on: November 04, 2013, 10:31:07 AM »
|
|
|
the sencond try here is the log
04/Nov/2013 12:05:50.126: LOG: Opened FTDI device.
04/Nov/2013 12:05:50.128: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A400g2Nt Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
04/Nov/2013 12:05:50.129: LOG: FTDI ChipID DLL is loaded, checking chip ID...
04/Nov/2013 12:05:50.137: LOG: FTDI device chip ID: 0x9A7C2FD5
04/Nov/2013 12:05:50.194: USER: Validated FTDI device is in dumb mode.
04/Nov/2013 12:05:50.230: LOG: Starting send receive thread.
04/Nov/2013 12:05:50.233: LOG: Send receive thread now started.
04/Nov/2013 12:05:50.243: USER: Disconnected
04/Nov/2013 12:05:50.316: LOG: Setting communication timings to defaults.
04/Nov/2013 12:05:50.318: USER: Connecting...
04/Nov/2013 12:05:50.396: LOG: Setting communication timings to defaults.
04/Nov/2013 12:05:50.398: USER: Starting fast init connection.
04/Nov/2013 12:05:50.399: USER: Connecting to address 0x01.
04/Nov/2013 12:05:53.133: USER: Fast init sent, sending start communication request.
04/Nov/2013 12:05:53.175: LOG: Received message with service ID: StartCommunicationPositiveResponse
04/Nov/2013 12:05:53.178: LOG: Setting Address: 0x01 KeyByte1: 0x6F KeyByte2: 0x0F
04/Nov/2013 12:05:53.179: USER: Switching to KWP2000 session.
04/Nov/2013 12:05:53.181: USER: Connected
04/Nov/2013 12:05:55.654: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:05:55.687: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:05:58.175: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:05:58.211: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:00.695: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:00.735: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:03.216: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:03.259: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:05.737: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:05.774: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:08.258: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:08.298: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:10.780: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:10.821: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:13.304: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:13.348: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:15.824: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:15.861: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:18.344: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:18.386: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:20.865: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:20.899: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:23.386: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:23.423: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:25.922: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:25.960: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:28.444: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:28.482: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:30.966: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:31.008: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:33.487: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:33.521: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:36.007: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:36.045: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:38.527: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:38.569: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:41.048: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:41.085: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:43.569: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:43.610: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:46.091: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:46.132: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:48.615: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:48.656: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:51.136: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:51.172: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:53.657: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:53.695: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:56.178: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:56.220: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:06:58.700: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:06:58.743: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:07:01.220: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:07:01.257: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:07:03.080: LOG: Could not construct valid message from received data: MessageContainsNoData
04/Nov/2013 12:07:03.081: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x00
04/Nov/2013 12:07:03.098: LOG: Could not construct valid message from received data: MessageContainsNoData
04/Nov/2013 12:07:03.099: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x00
04/Nov/2013 12:07:05.106: LOG: Double checking receive buffer for embedded messages before flushing receive buffer due to P1 ECU response inter byte time out.
04/Nov/2013 12:07:05.108: LOG: Flushing 2 bytes from receive buffer due to P1 ECU response inter byte time out.
04/Nov/2013 12:07:05.129: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:07:05.171: LOG: Received message with service ID: TesterPresentPositiveReponse
04/Nov/2013 12:07:08.019: LOG: Double checking receive buffer for embedded messages before flushing receive buffer due to P1 ECU response inter byte time out.
04/Nov/2013 12:07:08.022: LOG: Flushing 1 bytes from receive buffer due to P1 ECU response inter byte time out.
04/Nov/2013 12:07:08.044: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:07:10.045: LOG: Message received no replies.
04/Nov/2013 12:07:10.047: LOG: Failed to read echo within time limit. Clearing remaining expected echo bytes.
04/Nov/2013 12:07:10.048: LOG: Resending message. Send attempts: 2
04/Nov/2013 12:07:10.070: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:07:12.073: LOG: Message received no replies.
04/Nov/2013 12:07:12.075: LOG: Failed to read echo within time limit. Clearing remaining expected echo bytes.
04/Nov/2013 12:07:12.077: LOG: Resending message. Send attempts: 3
04/Nov/2013 12:07:12.097: LOG: Sent message with service ID TesterPresent
04/Nov/2013 12:07:14.100: LOG: Message received no replies.
04/Nov/2013 12:07:14.101: LOG: Failed to read echo within time limit. Clearing remaining expected echo bytes.
04/Nov/2013 12:07:14.103: LOG: Failed to send message 3 times, message send failed.
04/Nov/2013 12:07:14.104: USER: Disconnecting because no response was received for the Tester Present message.
04/Nov/2013 12:07:14.106: USER: Disconnected
04/Nov/2013 12:07:14.155: LOG: Closing FTDI device.
04/Nov/2013 12:07:14.158: LOG: Send receive thread now terminated.
|
|
|
|
|
Logged
|
-ROMIE
|
|
|
ratherb1
Full Member
Karma: +5/-5
Offline
Posts: 115
|
|
« Reply #2 on: November 05, 2013, 05:48:30 AM »
|
|
|
Should I just keep reconnecting ?
|
|
|
|
|
Logged
|
-ROMIE
|
|
|
oldcarguy85
Full Member
Karma: +15/-1
Offline
Posts: 247
|
|
« Reply #3 on: November 05, 2013, 07:15:51 AM »
|
|
|
try removing the cluster fuse. Not sure what fuses exist on your car, but on my GTI there are two cluster fuses. You should remove the fuse that keeps the clock and odometer working, but disables the gauges themselves.
|
|
|
|
|
Logged
|
|
|
|
ratherb1
Full Member
Karma: +5/-5
Offline
Posts: 115
|
|
« Reply #4 on: November 05, 2013, 12:04:30 PM »
|
|
|
Pulled fuse instrument cluster fuse , tried again and I get the same "start communication did not get any response" ...... Frustrating
Also says validating ftdi is in dumb mode disconecting
I tried fast init , slow init , different baud rates
|
|
|
|
« Last Edit: November 05, 2013, 12:16:47 PM by ratherb1 »
|
Logged
|
-ROMIE
|
|
|
|
ddillenger
|
|
« Reply #5 on: November 05, 2013, 01:21:54 PM »
|
|
|
build a bench harness, defeat the immobilizer, and enjoy consistent flashes.
Pulling the cluster fuse is a bad idea, the immobilizer won't authenticate.
|
|
|
|
|
Logged
|
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 experience!
Email/Google chat:
DDillenger84(at)gmail(dot)com
Email>PM
|
|
|
ratherb1
Full Member
Karma: +5/-5
Offline
Posts: 115
|
|
« Reply #6 on: November 05, 2013, 02:01:49 PM »
|
|
|
Ugh why me ....every step I take towards flashing my car ......BAM road block .........I was under the impression that writing over my a6 ecu with an s4 file would disable the immo ( I thought I read somewhere or was told) .......
|
|
|
|
|
Logged
|
-ROMIE
|
|
|
|
ddillenger
|
|
« Reply #7 on: November 05, 2013, 02:08:44 PM »
|
|
|
Yes, once the file is on the ecu the immobilizer is disabled. Until then, it's another story. If you want, run a dedicated k-line.
I've always had luck flashing with a low baud, but not on all cars.
|
|
|
|
|
Logged
|
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 experience!
Email/Google chat:
DDillenger84(at)gmail(dot)com
Email>PM
|
|
|
ratherb1
Full Member
Karma: +5/-5
Offline
Posts: 115
|
|
« Reply #8 on: November 07, 2013, 05:21:48 AM »
|
|
|
I'm going to try to flash immo off file ..
|
|
|
|
|
Logged
|
-ROMIE
|
|
|
|
