Title: 518AF log v1.9.3.0 on XP Post by: elRey on April 07, 2012, 10:07:32 AM First off, Thank you , Thank you, Thank you.
Thanks for porting to XP! And thanks to this software, saved my 'invalid checksum' ecu. I could boot flash a corrected bin all day long, but without clearing the checksum error it didn't matter. And Galletto gets the changing speed error with this ecu so I was stuck until I looked to see if you added XP support. And you did !!! Thanks Tony! It flashed fine, but I was not able to read full flash. It could not valid mem layout. I'm sure I had the correct mem layout selected (800BB). Quote Validated FTDI device is in dumb mode. Disconnected Connecting... Starting slow init connection. Connecting to address 0x01. Slow init succeeded. Switching to KWP2000 session. 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. 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 that security access is not granted. Memory layout validation failed. Starting to read data block. Calculating flash checksum to determine if reading is necessary for range: 0x00800000 to 0x00810000 Flash checksum matches, reading flash data is unnecessary, but reading anyway. Requesting upload from ECU for address range 0x00800000 to 0x0080FFFF. Request upload from ECU failed, ECU reports security access has not been granted. Reading ECU flash memory failed. Trying to force ECU to recognize read operation is complete. Finished forcing ECU to recognize that failed read operation is complete. Reading ECU flash memory failed. 100% complete. Restoring Windows sleep mode. Disabling Windows sleep mode. Reading ECU flash memory. Negotiating communication timings. Successfully changed to new communication timings. Requesting security access. Security access granted. 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 that security access is not granted. Memory layout validation failed. Starting to read data block. Calculating flash checksum to determine if reading is necessary for range: 0x00800000 to 0x00804000 Flash checksum matches, reading flash data is unnecessary, but reading anyway. Requesting upload from ECU for address range 0x00800000 to 0x00803FFF. Request upload from ECU failed, ECU reports security access has not been granted. Reading ECU flash memory failed. Trying to force ECU to recognize read operation is complete. Finished forcing ECU to recognize that failed read operation is complete. Reading ECU flash memory failed. 100% complete. Restoring Windows sleep mode. Disabling Windows sleep mode. Writing ECU flash memory. Negotiating communication timings. Successfully changed to new communication timings. Requesting security access. Security access granted. 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 that security access is not granted. 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 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. 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. .... 94% complete. Data transfer complete. Requesting data transfer exit. Successfully exited data transfer. Calculating flash checksum to determine if flashing was successful for range: 0x008E0000 to 0x008F0000 Flash checksum matches new data, flashing was successful. Starting to flash data block. Calculating flash checksum to determine if flashing is necessary for range: 0x008F0000 to 0x00900000 Flash checksum matches new data, flashing is unnecessary, but flashing anyway. Requesting flash memory erase for address range 0x008F0000 to 0x008FFFFF. Successfully erased flash memory. Requesting download to ECU for address range 0x008F0000 to 0x008FFFFF. Request download to ECU succeeded. Starting data transfer. 100% complete. Data transfer complete. Requesting data transfer exit. Successfully exited data transfer. Calculating flash checksum to determine if flashing was successful for range: 0x008F0000 to 0x00900000 Flash checksum matches new data, flashing was successful. Disconnecting from ECU to force it to recognize successful completion of flash write. Writing ECU flash memory succeeded. Wrote 19 of 19 sectors in flash memory. Flashing time was 00:03:03. Estimated premium full write time: 00:02:40. Estimated premium fast write time: 00:00:25. Restoring Windows sleep mode. Disconnecting... Disconnected Title: Re: 518AF log v1.9.3.0 on XP Post by: quattro85 on August 22, 2012, 12:01:43 AM Hello elRey,
Did you manage to get Full Flash Read to work? I have exactly same problem while trying to read my ECU. 0x92, System Supplier ECU Hardware Number: 0261208228 0x94, System Supplier ECU Software Number: 1037369311 0x91, Vehicle Manufacturer ECU Hardware Number: 0x0D, 8E0909018A , 0xFF 0x9B, Calibration Date: 8E0909518AL , 0003, 0x03002DBF, 0x0001010A, 0x81FE, 1.8L R4/5VT , G 0x9C, Calibration Equiment Software Number: 0x00004E00 My ECU was been flashed by local tuner. Is this possible to have some kind of read lock applied by him? |