BeagleBoard demo image - Release r0

Would anyone be willing try out a new BeagleBoard image that I’ve created?

The next revision of the BeagleBoard image contains the following new additions:

  • Kernel 3.0.3 with a lot of fixes and with LCD support

  • gstreamer-ti and ti-dmai stack

  • U-boot with fixes for hub power

  • Fixes to U-boot environment variables for LCD

  • systemd for very fast boot (thanks to Koen)

  • gnome desktop

  • pulseaudio

  • alsa

  • midori

  • gedit

  • gstreamer plugins

Other features included:

  • Ability to be Auto-flashed to NAND by holding the userbutton when u-boot loads

  • Ability to be rebuilt easily in SD card format

You can get this image in 2 simple ways:

  1. Direct Download

http://www.beagleboard.org/~joelf/images/beagleboard-demo/Angstrom-beagleboard-gnome-image-eglibc-ipk-v2011.08-core-beagleboard-r0.img.gz

  1. Rebuild from scratch

You can rebuild the image by following instructions at: http://www.angstrom-distribution.org/building-angstrom

With the following differences:

  1. Replace URLS in sources/layers.txt with ones similar to:

meta-angstrom,git://github.com/joelagnel/meta-angstrom.git,master,HEAD

meta-openembedded,git://github.com/joelagnel/meta-openembedded.git,master,HEAD

meta-texasinstruments,git://github.com/joelagnel/meta-texasinstruments.git,master,HEAD

openembedded-core,git://github.com/joelagnel/oe-core.git,HEAD

  1. Build filesystem using Embedded by running the command:

bitbake beagleboard-validation-gnome-image

No need of any additional scripts, the resulting .img.gz will be available in the deploy/ directory!

I will like to start from “r0” and will keep bumping the Revs as and when new additions are made.

I will also maintain a CHANGELOG [1] made available at with changes introduced in each image

I am ready to hand walk anyone interested in trying this image, so please feel free to pound me with any questions by email or IRC, thanks.

Looking forward to your feedback on anything in terms of functionality you’d like to see included (I already have an older list) and other suggestions.

Regards,

Joel

[1] http://www.beagleboard.org/~joelf/images/beagleboard-demo/CHANGELOG

Side note:

I am working on an updated patchset with feedback from the OE-core community, so maintainers please don’t consider my patches to be in the final form in my git tree(s).

My XMa stops at "Uncompressing Linux… done, booting the kernel. "

I followed your directions exactly using your image.

Any ideas?

Thanks,
Mark

Texas Instruments X-Loader 1.5.0 (Apr 11 2011 - 09:47:05)
Beagle xM
Reading boot sector
Loading u-boot.bin from mmc

U-Boot 2011.03 (Apr 20 2011 - 07:19:53)

OMAP3630/3730-GP ES2.0, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 0 MiB
MMC: OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment

In: serial
Out: serial
Err: serial
Beagle xM Rev A
No EEPROM on expansion board
Die ID #66a200011ff00000015739eb0b02302a
Hit any key to stop autoboot: 0
reading boot.scr

356 bytes read
Running bootscript from mmc …

Executing script at 82000000

reading uImage

3605220 bytes read
reading uInitrd

6566686 bytes read

Booting kernel from Legacy Image at 80000000 …

Image Name: Linux
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3605156 Bytes = 3.4 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum … OK

Loading init Ramdisk from Legacy Image at 81600000 …

Image Name: Ubuntu Initrd
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6566622 Bytes = 6.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum … OK
Loading Kernel Image … OK
OK

Starting kernel …

Uncompressing Linux… done, booting the kernel.

oops, wait. wrong mmc. :expressionless:

sorry, ignore this. I’ll boot the correct mmc :slight_smile:

For subsequent images can you please do this once:

cd /some/path
git clone git://git.angstrom-distribution.org/testlab && cd testlab && checkout origin/yocto -b joel-builds

cd /your/OE/dir
echo 'TESTLABLOG = "remote"' >> conf/local.conf
echo 'TESTLABREMOTEDIR = "/some/path/testlab"' >> conf/local.conf

And then for each build go into /some/path/testlab and save the output of 'git show' into the download location. It should look something like this: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/testlab/commit/?h=yocto&id=501da9a5e7626f39bd9c294f6cea13c9ef0cbe05

That will show what changed between builds. Bonus points for uploading the joel-builds branch to some public git so people can browse the list of changes anytime.

regards,

Koen

I’ve downloaded the image and am eager to give it a try. I have a Rev C2 board and am using Ubuntu 11.4. Would appreciate micro guidance.

Thanks.

Mark.

I've downloaded the image and am eager to give it a try. I have a Rev C2
board and am using Ubuntu 11.4. Would appreciate micro guidance.

For a bit of hand-holding, I'd recommend you check out the IRC channel
at http://beagleboard.org/chat. For writing the image to your SD
card, you'd need to do something like:
$ wget http://www.beagleboard.org/~joelf/images/beagleboard-demo/Angstrom-beagleboard-gnome-image-eglibc-ipk-v2011.08-core-beagleboard-r0.img.gz
$ sudo sh -c "zcat Angstrom*r0.img.gz > /dev/sdb"

Eject the card when complete, insert into your BeagleBoard-xM and boot.

If you are using a BeagleBoard (not -xM), you might choose to hold the
USER button down on boot to reflash your board with a new bootloader
and a file system image. Upon completion, remove power, remove SD
card and then boot without the SD card.

Thanks Jason. Just a FAT 32 formatted SD is good to go, correct?

Mark.

I've downloaded the image and am eager to give it a try. I have a Rev C2
board and am using Ubuntu 11.4. Would appreciate micro guidance.

For a bit of hand-holding, I'd recommend you check out the IRC channel
at http://beagleboard.org/chat. For writing the image to your SD
card, you'd need to do something like:
$ wget http://www.beagleboard.org/~joelf/images/beagleboard-demo/Angstrom-beagleboard-gnome-image-eglibc-ipk-v2011.08-core-beagleboard-r0.img.gz
$ sudo sh -c "zcat Angstrom*r0.img.gz> /dev/sdb"

Eject the card when complete, insert into your BeagleBoard-xM and boot.

If you are using a BeagleBoard (not -xM), you might choose to hold the
USER button down on boot to reflash your board with a new bootloader
and a file system image. Upon completion, remove power, remove SD
card and then boot without the SD card.

Not much joy on a rev C3 board - just hangs, as below:

Texas Instruments X-Loader 1.4.4ss (Jan 29 2011 - 10:54:03)
Beagle Rev C1/C2/C3
Reading boot sector
Loading u-boot.bin from mmc

U-Boot 2011.06-dirty (Aug 29 2011 - 10:38:55)

OMAP3530-GP ES3.0, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 256 MiB
NAND: 256 MiB
MMC: OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Beagle Rev C1/C2/C3
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Unrecognized expansion board: 0
Die ID #4042000300000000040323090d017001
Net: Net Initialization Skipped
No ethernet found.
Hit any key to stop autoboot: 0
SD/MMC found on device 0
reading uEnv.txt

606 bytes read
Importing environment from mmc ...
Running uenvcmd ...
Setting bus to 1
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Error writing the chip.
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Error writing the chip.
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Error writing the chip.
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Error writing the chip.
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Error writing the chip.
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Error writing the chip.
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Error writing the chip.
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Error writing the chip.
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Error writing the chip.
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Error writing the chip.
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Error writing the chip.
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Error writing the chip.
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Error writing the chip.
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Error writing the chip.
Setting bus to 0
Loading file "/boot/uImage" from mmc device 0:2 (xxa2)
3363668 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
    Image Name: Angstrom/3.0.3/beagleboard
    Image Type: ARM Linux Kernel Image (uncompressed)
    Data Size: 3363604 Bytes = 3.2 MiB
    Load Address: 80008000
    Entry Point: 80008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OKOK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Note: I tried holding the user button while booting and it made no difference.

That's a stale x-loader, you should be seeing 1.5.x

Sounds exciting. In the spirit of automation and as a request, could
you import this functionality from OE-classic? I remember seeing
testlab files being generated with it and it would be nice to include.

Thanks,
Joel

There might have been an issue with missing patches or wrong version
of the x-load or u-boot that are in my OE build. I will check this
out, thanks for bringing this to attention! will keep you posted.

Regards,
Joel

To be sure, you can always include the x-loader (MLO) in the image.

I'm not having much luck getting this to work on my xM Rev B board. All I see at the serial port is the number 60 and then it hangs. This is the image downloaded from the above instructions. On my Ubuntu machine I do see a boot and rootfs partition and the boot contains U-BOOT.BIN, UENV.TXT and USER.TXT.
Is there something I'm missing? I know the board is OK as I have had both an Angstrom and Ubuntu build that works just fine.

Thanks
Mark B.

Can you copy out and delete all files in the FAT32 partition of the
image and copy in MLO _first_ and then U-boot.bin and UENV.TXT.

This is a bug in the image scripts, I need to copy MLO first in my
scripts as it seems some have problems with it.

thanks,

Joel

It overwrites the partition table and everything, so it doesn't matter
how it is formatted at the start.

I think it does need to be 4GiB.

The issues were with formatting of FAT as FAT32, and not copying MLO
first as I should have. I have corrected both these, building an image
finally and running final tests.

r1 is on the way!...

thanks,
Joel

Would anyone be willing try out a new BeagleBoard image that I've created?

The next revision of the BeagleBoard image contains the following new additions:
- Kernel 3.0.3 with a lot of fixes and with LCD support
- gstreamer-ti and ti-dmai stack
- U-boot with fixes for hub power
- Fixes to U-boot environment variables for LCD
- systemd for very fast boot (thanks to Koen)
- gnome desktop
- pulseaudio
- alsa
- midori
- gedit
- gstreamer plugins

Other features included:
- Ability to be Auto-flashed to NAND by holding the userbutton when u-boot loads
- Ability to be rebuilt easily in SD card format

You can get this image in 2 simple ways:

1. Direct Download
http://www.beagleboard.org/~joelf/images/beagleboard-demo/Angstrom-beagleboard-gnome-image-eglibc-ipk-v2011.08-core-beagleboard-r0.img.gz

2. Rebuild from scratch
You can rebuild the image by following instructions at: http://www.angstrom-distribution.org/building-angstrom

With the following differences:

1. Replace URLS in sources/layers.txt with ones similar to:
meta-angstrom,git://github.com/joelagnel/meta-angstrom.git,master,HEAD
meta-openembedded,git://github.com/joelagnel/meta-openembedded.git,master,HEAD
meta-texasinstruments,git://github.com/joelagnel/meta-texasinstruments.git,master,HEAD
openembedded-core,git://github.com/joelagnel/oe-core.git,HEAD

2. Build filesystem using Embedded by running the command:
bitbake beagleboard-validation-gnome-image

No need of any additional scripts, the resulting .img.gz will be available in the deploy/ directory!

I will like to start from "r0" and will keep bumping the Revs as and when new additions are made.
I will also maintain a CHANGELOG [1] made available at with changes introduced in each image

For subsequent images can you please do this once:

cd /some/path
git clone git://git.angstrom-distribution.org/testlab && cd testlab && checkout origin/yocto -b joel-builds

cd /your/OE/dir
echo 'TESTLABLOG = "remote"' >> conf/local.conf
echo 'TESTLABREMOTEDIR = "/some/path/testlab"' >> conf/local.conf

And then for each build go into /some/path/testlab and save the output of 'git show' into the download location. It should look something like this: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/testlab/commit/?h=yocto&id=501da9a5e7626f39bd9c294f6cea13c9ef0cbe05

That will show what changed between builds. Bonus points for uploading the joel-builds branch to some public git so people can browse the list of changes anytime.

Sounds exciting. In the spirit of automation and as a request, could
you import this functionality from OE-classic?

Import into what? It's already in meta-oe:

commit 68c15845d087df0a6f66c58a9fd80548a9bb3a59
Author: Koen Kooi <koen@dominion.thruhere.net>

    testlab, blacklist bbclass: import from meta-angstrom
    
    These are good for general use since other distros (SHR, SlugOS) are copying them into their layers nowadays. Let's stop this duplication by moving them here.
    
    Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>

Maybe what I meant is adding code that automates generating the
testlab 'diff' that shows what changed. It is just 2 commands but
still :slight_smile: I could add that myself too.

thanks,
Joel

Thanks.