Open GoogleCodeExporter opened 9 years ago
As its name implies, crcalc is only supposed to update the CRC field. While it
could be modified to update the size field in TRX and other headers, I would
argue that it should *not* do this automatically because the header may only
pertain to a portion of the firmware image and not the entire image. If crcalc
erroneously updates the size field in the header, you could end up with a brick.
I'd consider adding a command line option to crcalc to tell it what the header
size field should be, but this should not be the default action (the FMK
scripts specifically attempt to keep the original firmware sizes the same in
order to prevent possibly bricking the target device).
Original comment by heffne...@gmail.com
on 7 Aug 2013 at 3:30
Original issue reported on code.google.com by
kjh1311...@gmail.com
on 29 Jul 2013 at 5:08