I am trying to get an image that has a signed boot partition (boot.img and .sig) to work on a CM4, with the normal bootloader, as i read that this one should also support secure boot images. When trying to start this image i get the boot screen where the pi tries the different boot options, but it isn't able to load the image.
Then i read in another post here on the forum that you could test the system by placing a config.txt in the boot partitions root, next to the boot.img and .sig, which should then contain 'boot_ramdisk=1"
I have tried this, but then i get a black screen and nothing happens after that. Is there any way to debug why this happens, and also, is this the correct way to test a secure boot image?
Bootloader version is:
2024/07/30 14:02:35
version 5f18ffb61682740ed1751ba59952843d7521314f (release)
timestamp 1722344555
update-time 1732876979
capabilities 0x0000007f
Then i read in another post here on the forum that you could test the system by placing a config.txt in the boot partitions root, next to the boot.img and .sig, which should then contain 'boot_ramdisk=1"
I have tried this, but then i get a black screen and nothing happens after that. Is there any way to debug why this happens, and also, is this the correct way to test a secure boot image?
Bootloader version is:
2024/07/30 14:02:35
version 5f18ffb61682740ed1751ba59952843d7521314f (release)
timestamp 1722344555
update-time 1732876979
capabilities 0x0000007f
Statistics: Posted by nachte — Fri Nov 29, 2024 2:18 pm
