Closed ll-O-ll closed 1 month ago
Cloning the repo doesn't copy the bootcode4.bin file completely. I got a symbolic which is why that command doesn't see the bootcode.
Solution. Download the raw file in the recovery folder and overwrite the symbolic link
Describe the bug
I'm following the steps to secure boot my CM 4 using the example. I couldn't make the step to recover the CM EEPROM
Any ideas?
Steps to reproduce the behaviour
Following steps in secure-boot-example repo up until the point to reset the Compute Module EEPROM
Device(s)
Raspberry Pi CM4
Compute Module IO board.
No response
RPIBOOT logs
No response
Kernel logs
No response
Device UART logs
No response