Commit Graph

6 Commits (f8d6666e2b44d088dee0cbb58776e5743b6e6382)

Author SHA1 Message Date
Dustin 00eea4da52 fixup! board/qemu: Generate sdcard.img with post-image
Aimee OS/aimee-os/pipeline/head This commit looks good Details
2025-08-21 17:45:06 -05:00
Dustin 39d22f0e0a fixup! board/qemu: Generate sdcard.img with post-image
Aimee OS/aimee-os/pipeline/head There was a failure building this commit Details
2025-08-21 10:06:20 -05:00
Dustin 7c0a899500 board/qemu: Generate sdcard.img with post-image
Aimee OS/aimee-os/pipeline/head There was a failure building this commit Details
In order to test AimeeOS A/B filesystem updates, we need a full disk
image just like the Raspberry Pi variant has.
2025-08-21 07:50:00 -05:00
Dustin fbf22908eb board/rpi3: Enable UART console
U-Boot will not boot without the primary UART console enabled; the Pi
just hangs at the rainbow splash screen.  There are three ways to enable
a UART console, but disabling Bluetooth is usually the best, as the
others have performance implications.  Applications that need Bluetooth
will have to choose one of the other options, depending on their
specific requirements.
2025-08-20 06:57:20 -05:00
Dustin c0f8beb49a board/rpi3: post-image: Create grubenv BEFORE image
We obviously have to create the `grubenv` file before running
`genimage`, or it will not be included in the image.
2025-08-19 08:59:09 -05:00
Dustin 9dae022788 First working revision
At this point, we can generate an SD card image that is composed of an
EFI system partition, a SquashFS root partition (a), a blank root
partition (b), and a data partition.  On the EFI system partition are
the Raspberry Pi firmware and device trees, U-Boot and GRUB.  The
SquashFS filesystem contains the kernel and the whole filesystem tree.

A Raspberry Pi can successfully boot from an SD card containing this
image.  It's not quite usable yet, because there's no writable storage
available, or indeed any way to log in.
2025-08-17 16:01:40 -05:00