Hi, Suppose I would like to utilize the possibility of combining the OPTEE, EKD2 StandaloneMM, and U-BOOT efivars and RPMB drivers to store my env variables securely in RPMB of eMMC device. However I would still like to be able to use the boot script to call the bootm command to boot my non-uefi kernel image stored in fitImage. One of the efi variables could e.g. act as a rootfs selection (would be used as a value for root= passed as a kernel cmdline in A/B scenario) or could e.g indicate which configuration from fit image should be used. In other words - I would like to use the efi variables and the fact that they are stored on RPMB but not use the rest of UEFI implementation in u-boot. The problem is that, apparently there is no easy way to get the value of efi variable from boot script other than printing it and somehow parsing (I'm not sure if this is even possible without some nasty workarounds). Does it even make sense? If not, then I would be grateful for even a short explanation why, and perhaps showing an alternative way.
Best regards Patryk