Hello Shiva, Andrew
On Wed, May 13, 2026 at 06:36:40PM +0530, Shiva Tripathi wrote: > It's not expected for all K3-platforms to build OP-TEE with RPMB > support, some platforms lack eMMC entirely. fTPM is an optional > configuration for users who need measured boot, disk encryption, or > similar TPM related use-cases. > > The Yocto SDK we release for K3 platforms includes the fTPM TA embedded > in the OP-TEE, not sure if the same is true in your case. > > RPMB provisioning is needed for full functionality, but even without it > you shouldn't see these errors. Maybe the fTPM TA is missing from your > OP-TEE build, or something similar is causing loader error. Any comment on this? We are just integrating current meta-ti master with latest master U-Boot, as I wrote a few days ago. There is nothing special going on on our side, and your recent changes are introducing this unexpected behavior. On Wed, May 13, 2026 at 08:49:31AM -0500, Andrew Davis wrote: > This makes me think we are at the stage in boot where EFI variables > are trying to be persisted to some media, and when trying to use > the fTPM for this it fails (as would be expected without RPMB). > So this should be harmless, but why there is such a large error > printout we need to investigate and try to make it less verbose. Any chance TI can help on this? Francesco
