hello jacob46,
by default uboot doesn’t verify the images, it loads kernel image through file system even though it’s fused device.
since there’s UBoot feature called Verified Boot. you might have to execute tool to create a signed image, by add signatures to FIT (Flat Image Tree).
please refer to below for reference,
[U-Boot] Need help with verified u-boot on Tegra TX2
Verified boot on the Raspberry Pi – CrySyS Blog
so, the steps should be…
- download U-boot source code
- create a signed image.
- compile uboot with FIT image support.
- install the image for boot-up
- interrupt uboot auto boot sequence, use
setenvfor setting the initrd_high and fdt_high to specify the location where initrd and device tree loads into RAM, - check the TX2 boot-up logs, which should have verification for hash values.