Orange Pi 5 Plus TPM2.0 Overlay

[cofrandp]

Hello,

I've been using https://joshua-riek.github.io/ubuntu-rockchip-download/boards/orangepi-5-plus.html with a custom kernel that I built to activate my TPM2.0 device and it works.

Now I'm asked to use an UEFI compatible image with my Orange Pi 5 Plus. So what I did is more or less the same thing that in here 

 

But instead of the legacy kernel I used the 6.1.115-rockchip-vendor-rk35xx kernel and my device booted, I got an HDMI output, etc. And then I updated it to my custom kernel (6.1.0-1027-rockchip) that has the necessary configurations to allow TPM over SPI.

 

 

Now I'm trying to activate my TPM2.0 as I did before. To do that I added my compiled *.dtbo (rk3588-spi0-tpm-cs1.dtbo) to /boot/dtb/rockchip/overlay and activated it with armbian-config.

After reboot this is my  /boot/armbianEnv.txt

 

orangepi@uefi-arm64:~$ cat /boot/armbianEnv.txt
verbosity=1
bootlogo=true
console=both
extraargs=cma=256M
overlay_prefix=rk3588
fdtfile=rockchip/rk3588-orangepi-5-plus.dtb
rootdev=UUID=3e555b58-fdf4-4e2f-a3af-a8ecfd8034b6
rootfstype=ext4
overlays=spi0-tpm-cs1
param_spidev_spi_bus=0

 

However I still can't see my tpm under /dev/. 

 

I don't know what I'm missing, I'm quite new to this sorry

 

Thank you for your time  

 

 

[Werner]

You should check uboot logs if the dtbo is loaded correctly. You can get those using a debug serial console. If you don't know what that is or how to connect: https://debug.armbian.de

 

[royk]

Did you also install the dtb that belongs to that kernel version?
You could check if the dtbo is compatible with your dtb with:
fdtoverlay -v -i /boot/dtb/current.dtb -o /tmp/test.dtb your-overlay.dtbo

 

It would be better to compile the dts with armbian-add-overlay your-overlay.dts so it will automatically install it to /boot/overlay-user and added to your armbianEnv.txt. In this way it also won't get overwritten when you update the dtb. And of course like Werner said, check the debug serial console, you'll see much more detailed information.

And check if the symlinks are correctly linked to your kernel version.
ls -l /boot