Thanks for the tips Adrian, I will look into that fitimage.bbclass. I was also thinking about the dependency between u-boot and linux kernel. It seems to be required since uboot-sign.bbclass "re-signs" the fitImage (and puts the public key in the u-boot dtb with the same command) and then does a verification to check that the key works. But is the re-signing really required? As far as I could tell trying to navigate the uboot-sign.bbclass the re-signed image is never used except for doing the verification. If one would skip the verification step, I think it would suffice to to put the public key into the u-boot dtb and thus be able drop the dependency on the kernel recipe? Doing the verification is of course a good idea to make sure you do not end up with a non-bootable fitImage, but it could work as a temporary work-around.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#64429): https://lists.yoctoproject.org/g/yocto/message/64429 Mute This Topic: https://lists.yoctoproject.org/mt/110031442/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
