IMX8qx MEK CPU board goes in a continuous reboot loop after enabling Secure Storage in Trusty

[nishadkamdar]

We have the iMX8QuadXPlus MEK CPU Board.

We followed the below steps to enable Secure Storage TA on this board.

Step 1: Built the Android image for the same using the android_p9.0.0_2.3.4 package.

Step 2: Flashed the trusty image using the following command:

./uuu_imx_android_flash.sh -f imx8qxp -a -e -u trusty-c0

Step 3: The board boots successfully.

Step 4: Entered the fastboot mode using reboot bootloader command on the target

Step 5: Tried to enable the Secure Storage using the following commands

root@XXXX:/android_build/out/target/product/mek_8q# fastboot stage rpmb_key_test.bin
target reported max download size of 419430400 bytes
sending 'rpmb_key_test.bin' (0 KB)...
OKAY [  0.028s]
finished. total time: 0.028s
root@XXXX://android_build/out/target/product/mek_8q# fastboot oem set-rpmb-key
...
OKAY [  0.152s]
finished. total time: 0.152s
root@test-Precision-3630-Tower:/home/nanduser/nishad_2_3_4/android_build/out/target/product/mek_8q#

Step 6: Got the following output :

Starting download of 36bytes

downloading of 36 bytes finished
RPMB key programmed successfully!
RPMB key blob generated!

Step 7: Rebooted the board.

Step 8: After reboot the board executes the uboot and reboots.

Step 9: This happens in a continuous loop.

How do I recover from this ?

Thanks and Regards,

Nishad

[igorpadykov]

Hi nishadkamdar

seems Step 5 may be incomplete, should be

$ fastboot stage rpmb_key.bin
$ fastboot oem set-rpmb-key

as described for example on thread :

https://community.nxp.com/t5/i-MX-Processors/Trusty-RPMB-Key-question/m-p/877366

Best regards
igor

[nishadkamdar]

Hi Igor,

Sorry, but both the commands you mentioned are present in the Step 5 log.

Can you pls recheck?

The default rpmb key in the package is rpmb_key_test.bin

Thanks,

nishad

[nishadkamdar · Accepted solution]

Hello,

The solution to the question here:

https://community.nxp.com/t5/i-MX-Processors/iMX8QP-MEK-Boot-fails-with-Read-public-key-error-after-...

is the solution to this question as well.

Thanks and Regards,

Nishad