tree 6835b4dcdd9ef0dcb8fc3e416fc7a11901dad614
parent 8a47982ed8d40595a83b82b2298753873e597708
author Alexandru Gagniuc <mr.nuke.me@gmail.com> 1631734381 -0500
committer Tom Rini <trini@konsulko.com> 1633438215 -0400

test/py: Check hashes produced by mkimage against known values

Target code and mkimage share the same hashing infrastructure. If one
is wrong, it's very likely that both are wrong in the same way. Thus
testing won't catch hash regressions. This already happened in
commit 92055e138f28 ("image: Drop if/elseif hash selection in
calculate_hash()"). None of the tests caught that CRC32 was broken.

Instead of testing hash_calculate() against itself, create a FIT with
containing a kernel with pre-calculated hashes. Then check the hashes
produced against the known good hashes.

Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>