debian: test images (2014-02-05)

GoogleGroups
1

Another week, more fixes, do you sense we are getting closer to release???

First, for tracking please report all bugs to:
http://bugs.elinux.org/projects/debian-image-releases

Kernel:
3.8.13-bone39 -> 3.8.13-bone40
* fix /var/log filling up: (disabled CONFIG_USB_GADGET_DEBUG)
* added CBB-Serial cape

Changes:
New bb.org mirror repo at beagle.s3.amazonaws.com/debian
xinput_calibrator fixes from Louis
/etc/init.d/capemgr improvemnts (now lists multiple overlay with a
comma seperator)
libsoc upgraded to 0.6

Camera people (3.1MP and RadiumBoards):
What userspace programs are we missing? gstreamer? OpenCV plugins?

I really want to include a default shell script that'll take a picture
and allow end users to validate the 3.1/Radium capes work.

https://github.com/RobertCNelson/boot-scripts/tree/master/device/bone/capes

Does your "cape" work?

Does your wifi adapter work? Are we missing it's firmware?

http://elinux.org/Beagleboard:Updating_The_Software

http://rcn-ee.net/deb/testing/2014-02-05/

fd562123c837561154d3d4601ffcdc3b
./BBB-eMMC-flasher-debian-7.3-2014-02-05-2gb.img.xz
8753b1ebcd116c522e84b8855ea9bc67 ./bone-debian-7.3-2014-02-05-2gb.img.xz
d34306cc87c6b0d12385b870e1d9b9a5 ./debian-7.3-lxde-armhf-2014-02-05.tar.xz

An eMMC "flasher" which can be installed to any 2GB or greater microSD
card. [BBB-eMMC-flasher-debian-7.3-2014-02-05-2gb.img.xz]

http://rcn-ee.net/deb/testing/2014-02-05/BBB-eMMC-flasher-debian-7.3-2014-02-05-2gb.img.xz

It takes about 10-15 Minutes to dd microSD (2GB), 15 minutes to flash
eMMC (look for full 4 LED's)

2GB standalone image that can be flashed to any 2GB or greater.
[bone-debian-7.3-2014-02-05-2gb.img.xz]

http://rcn-ee.net/deb/testing/2014-02-05/bone-debian-7.3-2014-02-05-2gb.img.xz

It takes about 10-15 Minutes to dd microSD (2GB)

To resize once booted:
* cd /opt/scripts/
* git pull
* ./tools/grow_partition.sh
* sudo reboot

Finally one of my classic "setup_sdcard.sh".
[debian-7.3-lxde-armhf-2014-02-05.tar.xz]

http://rcn-ee.net/deb/testing/2014-02-05/debian-7.3-lxde-armhf-2014-02-05.tar.xz

Note for users who use my classic "setup_sdcard.sh" script, here is
the magic options to get the beaglebone project files + systemd.

sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot bone
--beagleboard.org-production --enable-systemd

To "rebuild"
git clone git://github.com/beagleboard/image-builder.git
cd image-builder
git checkout bb.org-v2014-02-05 -b tmp
touch release
./beagleboard.org_image.sh

Regards,

2

I have a couple of things I’m working on with the image-builder:

  • Cape support: I need a way to get dtbo loaded at boot, preferably without custom kernel (e.g. via initrd or by putting the .dtbo’s in mmcblp0p1)
  • Custom image: Building a customized version of the beagleboard.org image

For the latter, at your suggestion, I forked the repo and created my own myimage_image.sh by copying beagleboard.org_image.sh. However, you’ve been busy … too busy and I’m way behind on merging in your changes!

It looks like you’re working to a more extensible scheme for customizations, I see the machinekit configuration now has a directory with custom scripts in it, along with the machinekit() function in releases.sh.

This looks pretty interesting, it would be kind of cool to be able to do:

./image_builder.sh “myimage”

And have it raid the ./myimage" directory to get the configuration, package lists etc. for the “myimage” build.

How far off is this? I’d love to help test this out.

Thanks!

-W.

3

I have a couple of things I'm working on with the image-builder:

* Cape support: I need a way to get dtbo loaded at boot, preferably
without custom kernel (e.g. via initrd or by putting the .dtbo's in
mmcblp0p1)

Add it to: /etc/default/capemgr

This should work with external capes, not already compiled into the kernel.

This is the init script:
https://github.com/RobertCNelson/omap-image-builder/blob/master/target/init_scripts/capemgr-debian.sh

Essentially it's doing:

echo ${overlay} > ${capemgr}

* Custom image: Building a customized version of the beagleboard.org image

For the latter, at your suggestion, I forked the repo and created my own
myimage_image.sh by copying beagleboard.org_image.sh. However, you've
been busy ... *too* busy and I'm way behind on merging in your changes!

It looks like you're working to a more extensible scheme for
customizations, I see the machinekit configuration now has a directory with
custom scripts in it, along with the machinekit() function in releases.sh.

This looks pretty interesting, it would be kind of cool to be able to do:

./image_builder.sh "myimage"

And have it raid the ./myimage" directory to get the configuration,
package lists etc. for the "myimage" build.

How far off is this? I'd love to help test this out.

I don't have any personal plans to do that yet. If you look closely, all
the frontend scripts do is create a ".project" file and call
./RootStock-NG.sh... If you want to make something universal generic, go
ahead.. All generic options should end up in the main chroot call with
"enable" options passed thru .project and anything target specific should
end up under target/

Regards,

4

There’s still a fair bit of stuff that goes on for the prep of the core & flasher images as well the chroot script(s) that would otherwise need to be cloned or customized. I like the way you have the NNN.* scripts in machinekit/scripts, right now it just runs them in order, but a “config.myimage” script could specify a list of these chroot actions. For example, I don’t need any of the X11 stuff, nor any of the bonescript/nodejs, but I do want system_patches(), unsecure_root() etc. and I also have a custom .deb to install the userside app for the cape (and a few other minor bits & pieces).

It looks like the machinekit stuff is close! but it’s not clear how it’s invoked (I do see the function in releases.sh and the config.machinekit) … is there a separate script (or branch) to run a machinekit build?

Thanks!

5

I run the MachineKit builds and added the chroot script hooks. I am
also behind on merging Robert's latest changes...I've been waiting for
things to settle down a bit and I have some other changes I've been
working on (for LinuxCNC, not the build scripts).

I haven't tried Robert's absolute latest, but the last time I merged his
changes, I was still able to build a custom (MachineKit) image by using
an appropriate config file (copy config.machinekit to config) and
running ./rcn-ee_image.sh.

6

* Custom image: Building a customized version of the beagleboard.org
image

I don't have any personal plans to do that yet. If you look closely,
all

the frontend scripts do is create a ".project" file and call
./RootStock-NG.sh... If you want to make something universal generic,
go
ahead.. All generic options should end up in the main chroot call with
"enable" options passed thru .project and anything target specific
should
end up under target/

There's still a fair bit of stuff that goes on for the prep of the core
&
flasher images as well the chroot script(s) that would otherwise need
to be
cloned or customized. I like the way you have the NNN.* scripts in
machinekit/scripts, right now it just runs them in order, but a
"config.myimage" script could specify a list of these chroot actions.
For
example, I don't need any of the X11 stuff, nor any of the
bonescript/nodejs, but I do want system_patches(), unsecure_root() etc.
and
I also have a custom .deb to install the userside app for the cape (and
a
few other minor bits & pieces).

It looks like the machinekit stuff is close! but it's not clear how
it's
invoked (I do see the function in releases.sh and the
config.machinekit)
... is there a separate script (or branch) to run a machinekit build?

I run the MachineKit builds and added the chroot script hooks. I am
also behind on merging Robert's latest changes...I've been waiting for
things to settle down a bit and I have some other changes I've been
working on (for LinuxCNC, not the build scripts).

I haven't tried Robert's absolute latest, but the last time I merged his
changes, I was still able to build a custom (MachineKit) image by using
an appropriate config file (copy config.machinekit to config) and
running ./rcn-ee_image.sh.

This is the approach I use because it is very difficult to track the
changes between your rep and Robert¹s repo. It seems you are both applying
the same patches, but at different times and in a different order, and you
both use different tagging. Once again, I simple apply your patches to
Robert¹s repo so that I¹m always current with Robert¹s latest changes. I
also host my own kernel images so I update releases.sh to reflect my URL.

Regards,
John

7

It can be a bit confusing. The diffs are a mix of changes to the build
scripts I made to support custom images, and general updates to the
actual MachineKit build (like adding or removing a package). Lately I
haven't had to do much work on the scripts, so my changes have mostly
been tweaks that just affect MachineKit, which Robert pulls periodically.

Now that Robert is building Debian images with a GUI, I'll likely switch
to using that as a base. I generally want to stay as close as possible
to the "official" release image and build scripts. There is enough
confusion out there already! :slight_smile:

8

Robert:
gedit is missing. Unfortunately it needs an additional 223M to install.

–Mark

9

That would probably be why it is missing.