-
Notifications
You must be signed in to change notification settings - Fork 8
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
Edit /boot/firmware/config.txt after provisioning #111
Comments
In the non-secure boot mode, it's simply read from the VFAT as part of the boot sequence - but when you migrate to secure-boot, you're instead embedding it in the Pre-Boot Authentication image. You essentially have two paths forward:
Note also that (2) will not survive an upgrade of the provisioner - and we're planning to drop 2.0 within the next few weeks with a range of improvements and changes. |
OK, thank you, is step 1 possible from the provisioned device or just the provisioner? It would be amazing for testing (and future proofing) if it is possible to edit the overlays on a provisioned device. Still, I want to create a golden image for my project. Would the config files update if I:
Sorry for the basic questions. |
It is indeed possible - just replace the boot.img & boot.sig with your updated copies. Provided you sign them with the same signing key, this should work well.
No - you'd need to update the pre-boot authentication image for overlays, and this would be a separate input to sb-provisioner. To do so, make your modifications in pi-gen-micro, and build a new initramfs there, and then replace the following file with your newly minted cryptroot: rpi-sb-provisioner/debian/install Line 25 in d377e82
|
I have created an image with I am a bit lost on how to build a new initramfs with this image. Are there steps within the sb-provisioner scripts that I could follow? |
@reflexcameras I must apologise, because I think I've sent you down a wrong path. Inspecting the code once more, I can confirm we only use the initramfs from the pi-gen-micro output, and this would not include config.txt. Instead, it should be as straightforward as modifying your These changes will then be fully captured in the boot.img. I had forgotten that the cryptroot is kept as a subitem in the boot.img - alongside the config.txt, cmdline.txt and traditional boot flow configuration items. See
|
No worries, thanks for confirming. Now that I have changed and reflashed the gold master image, it is working! Thanks again, |
I would like to swap cameras on a provisioned device. I cannot find config.txt in the usual directory /boot/firmware/config.txt. Is there a way to edit this file after provisioning to change the overlays?
The text was updated successfully, but these errors were encountered: