Here's more info, if needed, : The deploy for the .dtb is being done from here : https://git.openembedded.org/openembedded-core/tree/meta/classes/kernel-fitimage.bbclass?h=kirkstone#n755 The class is appending the functionality to kernel_do_deploy
Whereas our linux-ti-staging is not using that function at all. We are using kernel_vendor_dtb_do_deploy from here : https://git.ti.com/cgit/arago-project/meta-ti/tree/meta-ti-bsp/classes/kernel_vendor_dtb.bbclass?h=kirkstone#n776 Regards, Aniket -----Original Message----- From: Chawdhry, Manorit <[email protected]> Sent: Tuesday, May 30, 2023 4:01 PM To: Eatmon, Ryan <[email protected]>; Dmytriyenko, Denys <[email protected]>; [email protected]; Davis, Andrew <[email protected]>; Limaye, Aniket <[email protected]> Subject: Fit image signature Hi Ryan, I was recently trying to enable the fit signature locally on yocto and faced a warning.. WARNING: u-boot-ti-staging-1_2023.04+gitAUTOINC+010afc1fe7-r0 do_deploy: Failure while adding public key to u-boot binary. Verified boot won't be available. I was talking to Aniket about it and he let me know that there is some vendor specific override in the kernel class now and am worried that this vendor specific override might not be compatible with the fit signature that is there in the upstream. Can you let me know if this vendor specific class has the things related to enabling the fit signature booting with uboot? Regards, Manorit
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16620): https://lists.yoctoproject.org/g/meta-ti/message/16620 Mute This Topic: https://lists.yoctoproject.org/mt/99216758/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
