muvarov / meta-ts

MIT License
1 stars 1 forks source link

How to fix "Card did not repond to voltage select! : -110 Unable to OP-TEE session (err=-5)" #1

Open TaihuLight opened 2 years ago

TaihuLight commented 2 years ago

https://github.com/OP-TEE/optee_os/issues/4197#issuecomment-1068684940

I follow the instructions show in this repo, which is the same as meta-trustedsubstrate, to build OP-TEE 3.14 for Rock pi 4B.

(1) Build ts-firmware-rockpi4b-20220315070903.rootfs.wic.gz from the source meta-trustedsubstrate for Rock PI 4B
(2) Prepare SD with # zcat ts-firmware-rockpi4b-20220315070903.rootfs.wic.gz > /dev/sdc, where /dev/sdc is my SD card. Download the 'green' image ledge-iot-lava-ledge-qemuarm64-20220310014243.rootfs.wic.gz.
(3) Plug both USB stick and SD card into the board. Power it on and trap it in the U-boot command line <Hit any key before or when the monitor show Hit any key to stop autoboot: 0>. Also, you should not connect the board to internet. (4) Add kernel board specific kernel parameters and EFI boot order. efidebug boot add -b 1 BootLedge usb 0:1 efi/boot/bootaa64.efi -i usb 0:1 ledge-initramfs.rootfs.cpio.gz -s 'console=ttyS2,1500000 console=tty0 root=UUID=6091b3a4-ce08-3020-93a6-f755a22ef03b rootwait panic=60'

When I run the above EFI debug option, It shows the following errors

Card did not repond to voltage select! : -110
Unable to OP-TEE session (err=-5)
mm_communicate failed!
Error: Cannot initalize UEFI sub-system, r=3

My problem is (1) How to fix the above err? (2) Could I use the official images from Rock Pi 4, for example Ubuntu 20.04 server ? Because the rootfs image from ledge without key tools (make, apt, etc.), I hard to install other tools into the ledge OS. @muvarov

muvarov commented 2 years ago

@TaihuLight official sources are here: https://git.codelinaro.org/linaro/dependable-boot/meta-ts . We did not do official releases so I can not point you to already tested code. Code in the repo has to work but might be some issues related to the latest changes. First error might be because your board does not have eMMC card which is used to UEFI variable to store. In that case you can try to recompile optee os with REE_FS instead of RPMB storage. You should be able to boot Ubuntu, but I did not try that. It might be you need to comment out certificates tar ball in yaml file to turn off secure boot.

muvarov commented 2 years ago

@TaihuLight I updated in my gh repo. Actually you can send patches to our mailing list.