omap image builder: early_chroot issues

General Discussion
1

Hey all, I’m trying to service some custom image builder scripts that my club maintains. I think we’re using a legacy configuration format, but that’s not really the point.

My custom script relies on an early_chroot script that copies our device tree binaries into tempdir/tmp

cp ../../device_trees/*.dtb $tempdir/tmp

I noticed that maybe at some point the omap image builder stopped supporting the early_chroot script feature, but now I’m unsure of the right way to copy these dtb’s to the target. I could obviously add an absolute path to the dtbs in my config, but that seems hacky. What should I do?

oresat-dev.conf (4.8 KB)

2

and back…

Sorry, things get removed when they aren’t used. :wink:

Regards,

1 Like
3

Oh, what, thank you!

I am wondering though; is this the only way? Are we using the tools in an unintended manner? Our club supports ~6 different am335x boards and uses BBBs for testing.

4

There’s nothing stopping you from doing it the “target/chroot/*.sh” files:

For example like octavo: omap-image-builder/target/chroot/octavo-buster.sh at master · RobertCNelson/omap-image-builder · GitHub

Regards,

1 Like