- Code: Select all
...
[19:08:37.389] kernel write flash buffer addr: 000CC000 len: 00000800
[19:08:37.498] kernel write flash buffer addr: 000CC800 len: 00000800
[19:08:37.608] kernel validate flash addr: 000CC000 len: 00001000 crc32: 71f07369
[19:08:37.623] kernel write flash buffer addr: 000CD000 len: 00000800
[19:08:37.717] kernel write flash buffer addr: 000CD800 len: 00000800
[19:08:37.810] kernel validate flash addr: 000CD000 len: 00001000 crc32: 2af11b5f
[19:08:37.826] kernel write flash buffer addr: 000CE000 len: 00000800
[19:08:37.966] kernel write flash buffer addr: 000CE800 len: 00000800
[19:08:40.010] J2534 error [ERR_TIMEOUT].
[19:08:40.010] reading kernel comm stats
[19:08:40.026] kernel write flash buffer addr: 000CE800 len: 00000800
[19:08:40.119] kernel validate flash addr: 000CE000 len: 00001000 crc32: 4846cf4a
[19:08:40.135] failed to validate flash buffer!
[19:08:40.135] failure in flashing block[19:08:40.135] kernel flash disable
[19:08:40.150] interface close
[19:08:40.166] interface close
I re-ran the test-write and it passed, after which I performed an actually reflash, which succeeded.
Now my concern is, would this timeout error have "bricked" the ECU or is it possible to recover from such an error by attempting to reflash again? Therefore, does any error in reflashing always result in an unflashable ECU?
I've flashed my car with my AP around 30-40 times and have never had an error. This was my 6th reflash using ECUFlash. Could this be a beta issue, possibly related to the new USB driver?
I'm using ECUFlash 1.43.3000 on a Dell Mini 9 running Windows 7 Pro, 16GB SSD, 2GB RAM, and Tactrix 2.0 Rev C.
Thanks.