summaryrefslogtreecommitdiffstats
path: root/tools/fwpatcher/h100sums.h
diff options
context:
space:
mode:
authorJames Buren <braewoods+rb@braewoods.net>2020-11-16 18:44:45 +0000
committerJames Buren <braewoods+rb@braewoods.net>2020-11-16 19:44:52 +0000
commitadee6a11bf4d1330fed5995a01f8a850b876f428 (patch)
treeb223b98f503105778e0f05429dba462756e2deec /tools/fwpatcher/h100sums.h
parent64ea6442695aee6bc1096672716f12245425ff4c (diff)
downloadrockbox-adee6a11bf4d1330fed5995a01f8a850b876f428.tar.gz
rockbox-adee6a11bf4d1330fed5995a01f8a850b876f428.tar.bz2
rockbox-adee6a11bf4d1330fed5995a01f8a850b876f428.zip
rockbox: fix iriver firmware validation for larger bootloaders
It turns out the code for the firmware size validation was incorrectly using the total length of the firmware file to check if it was too big for the flash rom which caused it to incorrectly flag larger bootloaders as too big even though they would still fit. As it happens this situation can only really arise after mkboot has been run on the decoded firmware image. Because mkboot writes the actual binary size to the ESTFBINR header we will be using that to check if the firmware image is too large for the flash rom. Now because this information is embedded in the decrypted / encrypted region we have to collect it as the region is processed so the validation is also moved to after the data processing loop. Change-Id: I8bfead73812fe4e59f08fbbe8956790604dcb4e2
Diffstat (limited to 'tools/fwpatcher/h100sums.h')
0 files changed, 0 insertions, 0 deletions