Hello,
I am using a SOM from boundary, its name is nitrogen8mp. This SOM has an i.MX8 MPlus on it.
I am trying to implement HAB on this SOM. While following the documentation, I see that I need some paramters from mkimage logs while it's building the bootloader.
The problem is that I find empty parameters:
========= OFFSET dump ========= Loader IMAGE: header_image_off 0x0 image_off 0x40 csf_off 0x30a00 spl hab block: 0x91ffc0 0x0 0x30a00 Second Loader IMAGE: sld_header_off 0x0 sld_csf_off 0x0 sld hab block: 0x0 0x0 0x0
The "sld hab block" and "sld_csf_off" should indicate the position of u-boot FIT binary, that contains other binaries as well(TF-A+OPTEE+DTB). But I don't have anything in these logs.
In the same time the rest of the logs, shows that binman tool, will build the bootloader and add the fit-image to the SPL.
Can some one please propose a solution for me ?. I will let the whole file of mkimage logs attached, it contains other offsets and sizes that I can use.
Solved! Go to Solution.
Hello,
I was following https://github.com/u-boot/u-boot/blob/master/doc/imx/habv4/guides/mx8m_spl_secure_boot.txt
But, apparently imx-boot of boundary is built different, so instead I did like them, by following the script https://github.com/boundarydevices/u-boot/blob/boundary-v2022.04/sign_hab_imx8m.sh
I would love if they did the same as NXP, which would gain some time for users.
Thanks Harvey
Best regards,
Mohamed
Hello,
I was following https://github.com/u-boot/u-boot/blob/master/doc/imx/habv4/guides/mx8m_spl_secure_boot.txt
But, apparently imx-boot of boundary is built different, so instead I did like them, by following the script https://github.com/boundarydevices/u-boot/blob/boundary-v2022.04/sign_hab_imx8m.sh
I would love if they did the same as NXP, which would gain some time for users.
Thanks Harvey
Best regards,
Mohamed
Hi,
Which document have you followed? suggest to have a try to raise the issue to Boundary?
Regards
Harvey