Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TEST] initramfs-framework: Do not fail if device unlocked #1130

Closed
wants to merge 6 commits into from

Conversation

alexgg
Copy link
Contributor

@alexgg alexgg commented Jun 3, 2024

For testing purpose, the OS_DEVELOPMENT compilation switch will make the device not crash when booting an unlocked device.

@alexgg alexgg marked this pull request as draft June 3, 2024 10:16
@alexgg alexgg force-pushed the alexgg/no-is-secured-check branch from b9e963a to f5a5e07 Compare June 6, 2024 10:22
@alexgg alexgg force-pushed the alexgg/no-is-secured-check branch from 3199946 to d985502 Compare June 17, 2024 09:27
alexgg added 3 commits June 28, 2024 13:03
…e USB boot

With this change the device will first attempt to boot from USB and then
boot from the NVME/internal eMMC/SD card. This allows to use USB flasher
images as provisioning tools in preference of usbboot.

5: USB 2.0 boot from USB type A socket (CM4) or Type C socket (RPI4)
6: NVME
1: eMMC / SD Card
2: Network boot

We place NVME before eMMC/SDcard as there are reports that NVME is not
working if initialized after.

Also, there is no USB mass storage boot to limit this option to using
physical jumper configuration.

See https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#BOOT_ORDER

Note that trying USB boot first adds a considerable delay to the boot
process as the CM4 has a timeout of 2s (5s if extended via
`program_usb_boot_timeout=1`  per USB port enumeration.

As such, this change is only done to the `raspberrypicm4-ioboard-sb`
that requires USB boot for the secure boot provisioning flow.

Changelog-entry: Modify boot order to prioritize USB boot
Signed-off-by: Alex Gonzalez <[email protected]>
This is useful for the use case of a flasher image ran from external
media, like in the traditional flasher workflow that expects the device
to shutdown after programming.

From https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#POWER_OFF_ON_HALT

Changelog-entry: configure to power off on halt for raspberrypicm4-ioboard-sb
Signed-off-by: Alex Gonzalez <[email protected]>
As CM4 and CM4IO don’t include the external USB 3 controller,
set `otg_mode=1` for better performance as done in Raspberrypi OS.

See https://www.raspberrypi.com/documentation/computers/config_txt.html#otg_mode-raspberry-pi-4-only

Changelog-entry: enable USB 2.0 for CM4
Signed-off-by: Alex Gonzalez <[email protected]>
@alexgg alexgg force-pushed the alexgg/no-is-secured-check branch from d985502 to c88da74 Compare June 28, 2024 11:56
alexgg added 3 commits June 28, 2024 14:50
This allows to build with newer host dockers.

Signed-off-by: Alex Gonzalez <[email protected]>
For testing purpose, the `OS_DEVELOPMENT` compilation switch will make
the device not crash when booting an unlocked device.

Signed-off-by: Alex Gonzalez <[email protected]>
This allows to test with unlocked devices

Signed-off-by: Alex Gonzalez <[email protected]>
@alexgg alexgg force-pushed the alexgg/no-is-secured-check branch from c88da74 to 6edf126 Compare June 28, 2024 12:50
@alexgg
Copy link
Contributor Author

alexgg commented Jul 26, 2024

Project paused - this was just used for development.

@alexgg alexgg closed this Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant