omap-image-builder question

natxo_nn · June 5, 2023, 10:36pm

Hello

I want to make a custom debian image, so i

https://github.com/RobertCNelson/omap-image-builder.git
cd omap-image-builder
./RootStock-NG.sh -c bb.org-debian-bullseye-minimal-v5.10-ti-armhf

And later

cd tools
sudo ./setup_sdcard.sh --img-2gb am335x-debian-11.7-minimal-armhf-2023-06  --dtb beaglebone --distro-bootloader --enable-cape-universal --enable-uboot-disable-pru --enable-bypass-bootup-scripts

But i get

0+0 records in
0+0 records out
0 bytes copied, 0,000104699 s, 0,0 kB/s
-----------------------------
U-Boot Overlays Enabled...

That don’t seems ok and also no img is created, obviously i’m doing something wrong… any clue?

Regards

silver2row · June 5, 2023, 11:00pm

One thing that jumps out in the ./setup_sdcard.sh script is the first argument, i.e. --img-2gb.

I say this only b/c most of the images are larger than 2GB.

Seth

P.S. Now, I am sure the owner of the repo will definitely prove me wrong in more ways than one. I will be watching to see how this transpires. I am interested in omap-image-builder.git too.

RobertCNelson · June 5, 2023, 11:04pm

natxo_nn:

cd tools
sudo ./setup_sdcard.sh --img-2gb am335x-debian-11.7-minimal-armhf-2023-06  --dtb beaglebone --distro-bootloader --enable-cape-universal --enable-uboot-disable-pru --enable-bypass-bootup-scripts

Don’t use the ‘setup_sdcard.sh’ under tools, use the “packaged” archived version under deploy…

Edit, background, it’s looking for all the relative project files from when you ran RootStock-NG.sh…

Regards,

natxo_nn · June 5, 2023, 11:11pm

Thanks, its working!

I get the 2gb param from here, i asume is because its a minimal image no desktop

github.com

RobertCNelson/omap-image-builder/blob/faf136e0cc35c0b7fd27ee97995593f175c53b13/publish/rcn-ee_bb.org-stable.sh#L255


      
          
          
###UBUNTU BIONIC: ros-iot
          rootfs="${ubuntu_bionic_ros_iot}" ; blend="bionic-ros-iot" ; extract_base_rootfs
          
          
options="--img-6gb am57xx-\${rootfs}  ${am57xx_v54ti}"  ; generate_img
          options="--img-6gb bone-\${rootfs}    ${am335x_v54ti}"  ; generate_img
          
          
###debian bullseye minimal
          rootfs="${debian_bullseye_minimal}" ; blend="bullseye-minimal" ; extract_base_rootfs
          
          
options="--img-2gb am335x-\${rootfs}  ${am335x_v510ti}"  ; generate_img
          options="--img-2gb am57xx-\${rootfs}  ${am57xx_v510ti}"  ; generate_img
          
          
###debian bullseye iot
          rootfs="${debian_bullseye_iot}" ; blend="bullseye-iot" ; extract_base_rootfs
          
          
options="--img-4gb am335x-\${rootfs}  ${am335x_v510ti}"  ; generate_img
          options="--img-4gb am57xx-\${rootfs}  ${am57xx_v510ti}"  ; generate_img
          
          
###debian bullseye xfce
          rootfs="${debian_bullseye_xfce}" ; blend="bullseye-xfce" ; extract_base_rootfs

natxo_nn · June 6, 2023, 8:37am

Im curious about those names in configs. there seems to be:

bb.org-debian-*******
eewiki_minfs_********
octavo-debian *******
octavo-debian ******

What those means and why there is that classification? Also is there something like a “stable or master or whatever is called” config/kernel version.

Thanks

RobertCNelson · June 6, 2023, 1:57pm

bb.org → beagleboard.org images
eewiki → generic rootfs builds i use for day job: Linux Guides - Electronic Component and Engineering Solution Forum - TechForum │ Digi-Key
ocatvo → test builds for https://octavosystems.com/

For “stable” branches, right now that’s v4.19.x-ti (buster) and 5.10.x-ti (bullseye)… probably going to target 6.1.x-ti for (bookworm for the end of june…)

Regards,