Printable View
Ran into something I have never had happen... 16188051 ecm (LT1) using flashhack, after reading the Eside had completed it post a fail due to eside check sum invalid (T side was ok). I have no idea on the history on the ECM, friend bought it off ebay. I was wondering if I flashed a known good bin file into ECM if this might fix it (if the write cal will work). Haven't tried anything yet. I tried my ECM (read fine) just to make sure the cable / PC did go honky on me.
If it's fleabay, who knows?
If it's not mission-critical or anything, I say flash it with a known-good BIN and see what happens. Worst that can happen is it bricks, but if it's already got a bad checksum on the E-Side it's probably already a brick.
you could read it and ignore the bad checksum in flashhack and post it here
then we could compare with the factory cal to see what bits have flipped and whether its likely to affect loading the kernel
but personally id just reflash the thing
Thanks for the reply steveo. Will give it a try next week. love your stuff by the way, been using it for years on my LT1. Thanks for all the work you have done for us LT lovers.
Thanks for the replyNomakeWan, I will see what happens and if I can save this thing.
flashhack at least will let you flash repeatedly until it works as long as power is maintained
A bad checksum caused by erased/changed code would probably result in watchdog/cop resets. The PRU chip will send a system reset (same as toggling the key on and off) if the COP expires. In this case, monitoring the ALDL stream should give a clue to this. Messages would be sent followed by a pause while the system does a cold reset. The ESide will reset the TSide in case where the E PRU COP times out.Quote:
Originally Posted by NomakeWan
A bricked unit can be restored without much trouble. There is no need to replace the chips using bootstrap to reprogram.
-Tom