Hello. Not sure what I changed, seemingly for no reason my RPI5 stopped booting. I had a secure boot flow working and I didn't write the key to the OTP yet. Here's my content of my sdcard. Right now for testing I have only one fat16 partition of 255mb, nothing more.
pieeprom and recovery files are created by running the following while being in the usbboot/secure-boot-recovery5 dirboot.img and boot.sig are created by running the followingmake-boot dir containsboot_src contais this, which is what gets copied to the sdcard (a, b, key.bin.txt are the kernel uImage and the OTP key to be written later)
With such a prepared card when I start RPI at first I have a green LED, which suggests to me that recovery.bin runs and it wrote the eeprom image, because the filename changes to RECOVERY.000, however, after that I only have red light and 3 orange flashes. Looking at the list of LED flash codes : https://www.raspberrypi.com/documentati ... lash-codes
I am unsure what am I actually seeing. To me it seems like one long flash and 2 short ones, which does not appear in this table. Please help.
PS. There's nothing pritned on the UART. I used to see a full log of the bootrom, now nothing is printed.
PS2: Original unsigned pieeprom images make the pi work, so at least I know the hardware is not bricked, but it seems like my signed eeprom image doesn't want to launch boot.img. Very strange because I had this setup working for days... how come ??
Code:
-rwxr-xr-x 1 root root 2,0M 08-21 12:11 boot.img-rwxr-xr-x 1 root root 602 08-21 12:11 boot.sig-rwxr-xr-x 1 root root 65 08-21 12:11 key.bin.txt-rwxr-xr-x 1 root root 80 08-21 12:11 pieeprom.sig-rwxr-xr-x 1 root root 2,0M 08-21 12:11 pieeprom.upd-rwxr-xr-x 1 root root 100K 08-21 12:11 RECOVERY.000Code:
../tools/update-pieeprom.sh -f -k "${KEY_FILE}"cp pieeprom.sig ../../boot_src/pieeprom.sigcp pieeprom.bin ../../boot_src/pieeprom.updcp recovery.original.bin ../../boot_src/recovery.binCode:
./usbboot/tools/make-boot-image -d make-boot/ -o boot_src/boot.img./usbboot/tools/rpi-eeprom-digest -k secret-keys/rpi5-secure-boot/private.pem -i boot_src/boot.img -o boot_src/boot.sigCode:
-rw-r--r-- 1 oxi oxi 99K 08-21 11:05 bcm2712-rpi-5-b.dtb-rw-r--r-- 1 oxi oxi 52K 08-14 20:29 bootcode.bin-rw-r--r-- 1 oxi oxi 95 08-21 10:45 cmdline.txt-rw-r--r-- 1 oxi oxi 2,5K 08-14 20:29 config.txt-rw-r--r-- 1 oxi oxi 581K 08-21 11:05 kernel_2712.img // <-- this is U-Bootdrwx------ 1 oxi oxi 1,8K 08-14 20:29 overlaysCode:
drwxr-xr-x 1 oxi oxi 18 08-16 18:53 adrwxr-xr-x 1 oxi oxi 18 08-16 18:53 b-rw-r--r-- 1 oxi oxi 2,0M 08-21 12:11 boot.img-rw-r--r-- 1 root root 602 08-21 12:11 boot.sig-rw-r--r-- 1 oxi oxi 65 08-21 10:48 key.bin.txt-rw-r--r-- 1 oxi oxi 80 08-21 12:10 pieeprom.sig-rw-r--r-- 1 oxi oxi 2,0M 08-21 12:10 pieeprom.upd-rw-r--r-- 1 oxi oxi 100K 08-21 12:10 recovery.binI am unsure what am I actually seeing. To me it seems like one long flash and 2 short ones, which does not appear in this table. Please help.
PS. There's nothing pritned on the UART. I used to see a full log of the bootrom, now nothing is printed.
PS2: Original unsigned pieeprom images make the pi work, so at least I know the hardware is not bricked, but it seems like my signed eeprom image doesn't want to launch boot.img. Very strange because I had this setup working for days... how come ??
Statistics: Posted by pseregiet — Wed Aug 21, 2024 10:25 am