Draft
Conversation
Removes unused gpu label from oresat-base.dtsi Changes Makefile to reflect change in BeagleBoard-DeviceTrees structure Adds BeagleBoard-DeviceTrees as a submodule
`20-wired.network` isn't being used by `networkd` to configure the usb0 interface, so I broke the configuration into multiple files that should achieve the same thing. Forked beagle board imager to include python build tool upgrades in chroot scripts for compatibility with newer packaging workflow.
At some time in the past, the early_chroot script feature in the omap image builder was removed. RCN graciously added the feature back in for us ([link](https://forum.beagleboard.org/t/omap-image-builder-early-chroot-issues/43529)). Following this I reviewed the omap image builder and added improvements to our chroot scripts to improve safety and make use of script variables provided by the omap image builder.
After rootfs, bootloader, and device trees have been built `post-build.sh` and `genimage.cfg` are used to create a bootable image that can be flashed to boot media. `post-build.sh` - Loads build configuration - Unpacks the rootfs - Installs the kernel, initial device tree, `initrd`, setup `extlinux` - Creates an image using `genimage.cfg` The result is an image, `sdcard.img`, found in the `$PWD/images` directory `genimage.cfg` - Creates two partions - boot, a bootable FatFs which contains the bootloader and boot artifacts - root, the Linux filesystem
`build_images.sh` now calls out to `post_build.sh` to generate an image.
`systemd-resolved` is no longer a default package for Debian.
To build run ```text sudo make dev ``` This will compile all the oresat device tree files, and u-boot. Afterwards, it will bootstrap and build the image, which is placed in image_builder/images. As currently configured, the usb0 interface has a static ip address at 192.168.7.20. It supports sshfs and *should* support mDNS with avahi. Device tree overlays can be applied by modifying /extlinux/extlinux.conf located in the boot partition. The overlays need to be located in the boot partition.
I temporarily used a minimally patched version of the omap image builder, but this is no longer needed. Further, it is causing inconsistencies in the build process.
CullenSharp
force-pushed
the
experimental-debian-13-img-builder
branch
from
7a0699e to
d877e36
Compare
I was experiencing pinmux conflicts with the BBB and PB device trees, so I switched to am335x-bone. This is a very minimal device tree.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
For more information on the development process, read this PR #54.
To build run
This will compile all the oresat device tree files, and u-boot.
Afterwards, it will bootstrap and build the image, which is placed in
image_builder/images.
As currently configured, the usb0 interface has a static ip address at
192.168.7.20. It supports sshfs and should support mDNS with avahi.
Device tree overlays can be applied by modifying /extlinux/extlinux.conf
located in the boot partition. The overlays need to be located in the
boot partition.
Commits
build_images.shandpost_build.sh