michael66899
Newbie
Karma: +2/-0
 Offline
Posts: 15
|
 |
« on: November 17, 2013, 03:46:07 PM »
|
|
|
So I've flashed my personal cars probably 100 times and have always had good success, never bricked an ECU. Yesterday I went to flash an updated file on one of the cars and it's taking FOREVER and then the flash failed only a couple percent in. This has happened to me before but I tried again and it worked fine. So I tried again and after taking forever once again the flash failed about 8% in if I recall, the log file is below. I noticed the ECU light is no longer illuminated so I'm assuming its bricked but I thought I wouldn't be able to connect via NEF if it was bricked? Let me know what you guys think.
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.
Timing negotiation failed. Communication timings are unchanged.
Requesting security access.
ECU reports that security access is not supported.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Validating flash memory starts at 0x00800000 and ends at 0x00900000.
Validation failed, ECU reports RequestUpload service is not supported. RequestUpload may have been disabled by aftermarket engine software.
Memory layout validation failed.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00800000 to 0x00804000
Flash checksum does not match new data, flashing is necessary.
Requesting flash memory erase for address range 0x00800000 to 0x00803FFF.
Successfully erased flash memory.
Requesting download to ECU for address range 0x00800000 to 0x00803FFF.
Request download to ECU failed, ECU reports routine not complete or service in progress.
A previous flash programming attempt was not completed. Transfering invalid data to force the previous incomplete operation to fail.
Starting data transfer.
Data transfer complete.
Requesting data transfer exit.
Failed to exit data transfer.
Finished causing previous flash programming attempt to fail. Retrying flash programming.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00800000 to 0x00804000
Flash checksum does not match new data, flashing is necessary.
Requesting flash memory erase for address range 0x00800000 to 0x00803FFF.
Successfully erased flash memory.
Requesting download to ECU for address range 0x00800000 to 0x00803FFF.
Request download to ECU succeeded.
Starting data transfer.
1% complete.
Data transfer complete.
Requesting data transfer exit.
Successfully exited data transfer.
Calculating flash checksum to determine if flashing was successful for range: 0x00800000 to 0x00804000
Flash checksum matches new data, flashing was successful.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00804000 to 0x00806000
Flash checksum matches new data, flashing is unnecessary, but flashing anyway.
Requesting flash memory erase for address range 0x00804000 to 0x00805FFF.
Successfully erased flash memory.
Requesting download to ECU for address range 0x00804000 to 0x00805FFF.
Request download to ECU succeeded.
Starting data transfer.
2% complete.
Data transfer failed.
Requesting data transfer exit.
Failed to exit data transfer.
Failed to properly exit flash transfer. Transfering invalid data to force flashing to fail.
Starting data transfer.
Data transfer failed.
Requesting data transfer exit.
Failed to exit data transfer.
Writing ECU flash memory failed.
100% complete.
Restoring Windows sleep mode.
Requesting data transfer exit.
Failed to exit data transfer.
Disconnecting because no response was received for the Tester Present message.
Disconnected
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.
Timing negotiation failed. Communication timings are unchanged.
Requesting security access.
ECU reports that security access is not supported.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Validating flash memory starts at 0x00800000 and ends at 0x00900000.
Memory layout is valid.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00800000 to 0x00804000
Flash checksum matches new data, flashing is unnecessary, but flashing anyway.
Requesting flash memory erase for address range 0x00800000 to 0x00803FFF.
Successfully erased flash memory.
Requesting download to ECU for address range 0x00800000 to 0x00803FFF.
Request download to ECU succeeded.
|
|
|
|
« Last Edit: November 17, 2013, 03:54:45 PM by michael66899 »
|
Logged
|
|
|
|
michael66899
Newbie
Karma: +2/-0
Offline
Posts: 15
|
|
« Reply #1 on: November 17, 2013, 03:47:25 PM »
|
|
|
the rest...
Starting data transfer.
1% complete.
Data transfer complete.
Requesting data transfer exit.
Successfully exited data transfer.
Calculating flash checksum to determine if flashing was successful for range: 0x00800000 to 0x00804000
Flash checksum matches new data, flashing was successful.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00804000 to 0x00806000
Flash checksum matches new data, flashing is unnecessary, but flashing anyway.
Requesting flash memory erase for address range 0x00804000 to 0x00805FFF.
Successfully erased flash memory.
Requesting download to ECU for address range 0x00804000 to 0x00805FFF.
Request download to ECU succeeded.
Starting data transfer.
2% complete.
Data transfer complete.
Requesting data transfer exit.
Successfully exited data transfer.
Calculating flash checksum to determine if flashing was successful for range: 0x00804000 to 0x00806000
Flash checksum matches new data, flashing was successful.
Calculating checksum for first memory range to determine which erase mode the ECU is using.
ECU appears to be in erase sector mode, continuing the flash process.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00806000 to 0x00808000
Flash checksum matches new data, flashing is unnecessary, but flashing anyway.
Requesting flash memory erase for address range 0x00806000 to 0x00807FFF.
Successfully erased flash memory.
Requesting download to ECU for address range 0x00806000 to 0x00807FFF.
Request download to ECU succeeded.
Starting data transfer.
3% complete.
Data transfer complete.
Requesting data transfer exit.
Successfully exited data transfer.
Calculating flash checksum to determine if flashing was successful for range: 0x00806000 to 0x00808000
Flash checksum matches new data, flashing was successful.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00808000 to 0x00810000
Flash checksum does not match new data, flashing is necessary.
Requesting flash memory erase for address range 0x00808000 to 0x0080FFFF.
Successfully erased flash memory.
Requesting download to ECU for address range 0x00808000 to 0x0080FFFF.
Request download to ECU succeeded.
Starting data transfer.
4% complete.
5% complete.
6% complete.
Data transfer complete.
Requesting data transfer exit.
Successfully exited data transfer.
Calculating flash checksum to determine if flashing was successful for range: 0x00808000 to 0x00810000
Flash checksum matches new data, flashing was successful.
Starting to flash data block.
Calculating flash checksum to determine if flashing is necessary for range: 0x00810000 to 0x00820000
Flash checksum does not match new data, flashing is necessary.
Requesting flash memory erase for address range 0x00810000 to 0x0081FFFF.
Successfully erased flash memory.
Requesting download to ECU for address range 0x00810000 to 0x0081FFFF.
Request download to ECU succeeded.
Starting data transfer.
7% complete.
8% complete.
9% complete.
10% complete.
11% complete.
Too many consecutive unsolicited messages from ECU, disconnecting.
Disconnecting...
Disconnected
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...
Validated FTDI device is in dumb mode.
Disconnected
Waiting for user to reconnect to ECU before continuing...
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: THIS-IS-THE-RAM-PROGRAM-
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Connected
Negotiating communication timings.
Requesting security access.
Timing negotiation failed. Communication timings are unchanged.
Starting diagnostic session.
Received unknown message during security negotiation. Security negotiation failed.
Writing ECU flash memory failed.
100% complete.
Restoring Windows sleep mode.
Failed to start diagnostic session.
Received negative message response with code: ServiceNotSupported
Disconnecting because no response was received for the Tester Present message.
Disconnected
|
|
|
|
« Last Edit: November 17, 2013, 03:57:46 PM by michael66899 »
|
Logged
|
|
|
|
|
ddillenger
|
|
« Reply #2 on: November 17, 2013, 03:57:53 PM »
|
|
|
If you don't turn off the key, you can continue to connect and retry flashing. Try lowering the baud rate.
Once you turn that key off, it's game.
|
|
|
|
|
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
|
|
|
|
savages4
|
|
« Reply #3 on: November 17, 2013, 04:17:58 PM »
|
|
|
Most likely the ECU has a chip in it from APR or giac...
|
|
|
|
|
Logged
|
|
|
|
michael66899
Newbie
Karma: +2/-0
Offline
Posts: 15
|
|
« Reply #4 on: November 17, 2013, 04:23:43 PM »
|
|
|
If you don't turn off the key, you can continue to connect and retry flashing. Try lowering the baud rate.
Once you turn that key off, it's game.
Key has been removed.. Also this ECU was originally bone stock and currently has a file that I flashed previously.. Guess I need to order a Galletto cable, no other options I'm assuming? |
|
|
|
|
Logged
|
|
|
|
|
savages4
|
|
« Reply #5 on: November 17, 2013, 09:33:24 PM »
|
|
|
Try disconnecting the battery cables and touching them together for like 30 seconds. Then reconnect and try flashing it at the lowest Baud rate.
|
|
|
|
|
Logged
|
|
|
|
automan001
Full Member
Karma: +47/-0
Offline
Posts: 153
|
|
« Reply #6 on: November 17, 2013, 11:53:51 PM »
|
|
|
Bricked ECU won't answer until you put it into boot mode.
|
|
|
|
|
Logged
|
|
|
|
michael66899
Newbie
Karma: +2/-0
Offline
Posts: 15
|
|
« Reply #7 on: November 18, 2013, 01:32:46 PM »
|
|
|
Bricked ECU won't answer until you put it into boot mode.
Ya that's what I thought as well, makes me think there's still hope I can reflash it. I think one of my underlying issues is the old Vag-Com cable I'm flashing with, recently I had some issues with it while logging where I would have missing data so I went ahead and ordered up a new cable to see if that helps. |
|
|
|
|
Logged
|
|
|
|
|
