BeagleBoard demo image - Release r2

Fernandes_Joel_A · September 3, 2011, 2:58am

Hi!

Based on your feedback,
Here's the next version of the BeagleBoard demo image with a lot of problems fixed:

Including:
- Filesystem size, format entire partition, this resolves the gnome errors (Thanks Jason for reporting!)
- Switched to ext3
- Use latest MLO and copy it first into the boot partition (Thanks Mark Barton for reporting)
- Format boot partition with same size as mentioned in the partition table to keep bootrom happy (Thanks Vladimir!)

This image has been tested on -xM Rev C but should work on all boards.

You can get this image in 2 simple ways:

1. Direct Download [1]
Once downloaded, please read the setup instructions in the README [2] on how to write the image to your SDCard

2. Rebuild from scratch
Rebuild instructions can be found in the README [2]

Check out the testlab output to see what new packages have been added since the last revision [3] and CHANGELOG [4]. Right now testlab output is quite big because I'm generating it for the first time.

I will try to include a complete a compete package list and not just the diffs from the next revision.

Let me know how it goes, thanks!

-- Joel

[1] http://www.beagleboard.org/~joelf/images/beagleboard-demo/Angstrom-beagleboard-gnome-image-eglibc-ipk-v2011.09-core-beagleboard-r2.img.gz
[2] http://www.beagleboard.org/~joelf/images/beagleboard-demo/README
[3] http://www.beagleboard.org/~joelf/images/beagleboard-demo/testlab/testlab-r2
[4] http://www.beagleboard.org/~joelf/images/beagleboard-demo/CHANGELOG

Joel_A_Fernandes · September 3, 2011, 7:19pm

[This email didn't make it to the beagle list for some reason so I'm
resending it, thanks]

Hi!

Based on your feedback,
Here's the next version of the BeagleBoard demo image with a lot of
problems fixed:

Including:
- Filesystem size, format entire partition, this resolves the gnome
errors (Thanks Jason for reporting!)
- Switched to ext3
- Use latest MLO and copy it first into the boot partition (Thanks
Mark Barton for reporting)
- Format boot partition with same size as mentioned in the partition
table to keep bootrom happy (Thanks Vladimir!)

This image has been tested on -xM Rev C but should work on all boards.

You can get this image in 2 simple ways:

1. Direct Download [1]
Once downloaded, please read the setup instructions in the README [2]
on how to write the image to your SDCard

2. Rebuild from scratch
Rebuild instructions can be found in the README [2]

Check out the testlab output to see what new packages have been added
since the last revision [3] and CHANGELOG [4]. Right now testlab
output is quite big because I'm generating it for the first time.

I will try to include a complete a compete package list and not just
the diffs from the next revision.

Let me know how it goes, thanks!

-- Joel

[1] http://www.beagleboard.org/~joelf/images/beagleboard-demo/Angstrom-beagleboard-gnome-image-eglibc-ipk-v2011.09-core-beagleboard-r2.img.gz
[2] http://www.beagleboard.org/~joelf/images/beagleboard-demo/README
[3] http://www.beagleboard.org/~joelf/images/beagleboard-demo/testlab/testlab-r2
[4] http://www.beagleboard.org/~joelf/images/beagleboard-demo/CHANGELOG

jkridner · September 3, 2011, 9:11pm

[This email didn't make it to the beagle list for some reason so I'm
resending it, thanks]

Hi!

Based on your feedback,
Here's the next version of the BeagleBoard demo image with a lot of
problems fixed:

Including:
- Filesystem size, format entire partition, this resolves the gnome
errors (Thanks Jason for reporting!)

I verified this. Thanks.

- Switched to ext3
- Use latest MLO and copy it first into the boot partition (Thanks
Mark Barton for reporting)
- Format boot partition with same size as mentioned in the partition
table to keep bootrom happy (Thanks Vladimir!)

This image has been tested on -xM Rev C but should work on all boards.

You can get this image in 2 simple ways:

1. Direct Download [1]
Once downloaded, please read the setup instructions in the README [2]
on how to write the image to your SDCard

2. Rebuild from scratch
Rebuild instructions can be found in the README [2]

Check out the testlab output to see what new packages have been added
since the last revision [3] and CHANGELOG [4]. Right now testlab
output is quite big because I'm generating it for the first time.

I will try to include a complete a compete package list and not just
the diffs from the next revision.

Let me know how it goes, thanks!

I've noticed that the startup services don't end with carriage returns
(only newlines) in my minicom view, so it results some funny
indentations.

My biggest issue with this image is that the kernel still does not
work with the BeagleBoardToys ULCD-lite. I think we may have
different definitions of working. Mine includes having all of the
pixels showing up on the screen without wrapping around and using the
LCD driver, ie. defaultdisplay=lcd. Currently, using the LCD driver
causes no display to be enabled.

Automounting of /dev/mmcblk0p1 doesn't seem to be working. Do we need
a udev rule for it?

There are many different warnings that show up in the boot process.

The immediate packages I miss the most are synergy and vnc. Next on
my list would be a native C toolchain.

Now that EDID patches have been submitted to linux-omap, it should be
on our backlog to try integrating them.

Mark_Lee · September 3, 2011, 10:10pm

I do sudo zcat Angstrom-beagleboard-gnome-image-eglibc-ipk-v2011.09-core-beagleboard-r2.img.gz | dd of=/dev/mmcblk0 bs=10
and get Permission denied
Is this something to do with mmc?

Mark.

jkridner · September 4, 2011, 12:45am

in the command line below, dd isn’t running as root. try replacing sudo with sudo sh -c " and another " at the end.

Mark_Lee · September 4, 2011, 4:15am

I extracted sd.img from the archive and did ‘sudo dd if=sd.img of=/dev/sdb’

The result was:

2097160+0 records in
2097160+0 records out
1073745920 bytes (1.1 GB) copied, 613.687 s, 1.7 MB/s

Off for the next few days before I can see if it’s OK.

Mark.

VISHAL_SONI1 · September 4, 2011, 12:51pm

Hi

Does it work for BB-Xm -A3 ?

Following files are thr in my first partition

MLO latest
u-boot.bin
uImage
ramdisk.gz
ramfs.img
user.scr

whereas in second partion, i put the latest angstrom image.

i ran x11vnc command and it is showing that “command not found”, whereas i hv seen this command in latest angstrom image.

Am I doing anything wrong ?
Pls guide .

Regards
vishal

Joel_A_Fernandes · September 4, 2011, 4:25pm

Hey, Wait a minute? Did you follow the instructions in the README?

Thanks,
Joel

Joel_A_Fernandes · September 4, 2011, 4:25pm

Sounds good!

thanks
Joel

Mark_Lee · September 13, 2011, 7:59pm

OK, so I’ve finally inserted the SD and booted the BB Rev C2 connected to an HDMI monitor. All I see is an orange screen. Am I missing a step like pressing/releasing the reset or user button?

Mark.

Joel_A_Fernandes · September 13, 2011, 10:54pm

Hi Mark,

Can you paste your serial console output?

Joel

Mark_Lee · September 14, 2011, 1:59pm

So far this is what I have:

Welcome to minicom 2.5

OPTIONS: I18n
Compiled on Feb 5 2011, 06:31:35.
Port /dev/ttyUSB0

Press CTRL-A Z for help on special keys

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 … OK
OK

Starting kernel …

Uncompressing Linux… done, booting the kernel.

Mark.

Mark_Lee · September 14, 2011, 4:15pm

On holding user button while pressing reset:

Texas Instruments X-Loader 1.5.1 (Aug 26 2011 - 21:46:42)
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 #6f4a00030000000004013f790600b006
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 … OK
OK

Starting kernel …

Uncompressing Linux… done, booting the kernel.

Mark.

piranha32 · September 17, 2011, 4:42am

Joel,

I've just boot the R2 on my board and I'd like to share a few comments
from the first run:

1. before loading the kernel, u-boot complains a lot about problems
with i2c bus 1. Is this normal? I have Trainerboard attached to my xM:
------- cut here -------
Texas Instruments X-Loader 1.5.1 (Aug 26 2011 - 21:46:42)
Beagle xM
Reading boot sector
Loading u-boot.bin from mmc

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

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

In: serial
Out: serial
Err: serial
Beagle xM Rev A
Recognized Tincantools Trainer board (rev 0 0)
Die ID #65f200001bf00000015739ea07019027
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
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
Setting bus to 0
Loading file "/boot/uImage" from mmc device 0:2 (xxa2)
3363388 bytes read
------- cut here -------

2. startup scripts do not set the time from rtc:
------- cut here -------
new-host-6 login: root
Last login: Thu Jan 1 01:00:31 BST 1970 on ttyO2
root@new-host-6:~# date
Thu Jan 1 01:04:01 BST 1970
root@new-host-6:~# hwclock
Sat Sep 17 00:31:03 2011 0.000000 seconds
------- cut here -------

3. second i2c bus is not detected:
------- cut here -------
root@new-host-6:~# ls -l /dev/i2c-*
crw------- 1 root root 89, 1 Jan 1 01:00 /dev/i2c-1
crw------- 1 root root 89, 3 Jan 1 01:00 /dev/i2c-3
------- cut here -------

4. This request probably is for Koen, but would it be possible to add
driver for rt2870 chipset?
------- cut here -------
root@new-host-6:~# opkg search .\*2870.\*
root@new-host-6:~# uname -a
Linux new-host-6 3.0.4+ #1 Thu Sep 1 17:16:44 CEST 2011 armv7l GNU/Linux
------- cut here -------

regards,
j.

jkridner · September 18, 2011, 12:18am

Joel,

I've just boot the R2 on my board and I'd like to share a few comments
from the first run:

1. before loading the kernel, u-boot complains a lot about problems
with i2c bus 1. Is this normal? I have Trainerboard attached to my xM:
------- cut here -------
Texas Instruments X-Loader 1.5.1 (Aug 26 2011 - 21:46:42)
Beagle xM
Reading boot sector
Loading u-boot.bin from mmc

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

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

In: serial
Out: serial
Err: serial
Beagle xM Rev A
Recognized Tincantools Trainer board (rev 0 0)
Die ID #65f200001bf00000015739ea07019027
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
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
Setting bus to 0
Loading file "/boot/uImage" from mmc device 0:2 (xxa2)
3363388 bytes read
------- cut here -------

Interesting. I wonder what is going on with that I2C bus. Those
commands really don't belong in the boot-up script, so that is
something to clean-up, but it is interesting that the bus isn't
responding.

2. startup scripts do not set the time from rtc:
------- cut here -------
new-host-6 login: root
Last login: Thu Jan 1 01:00:31 BST 1970 on ttyO2
root@new-host-6:~# date
Thu Jan 1 01:04:01 BST 1970
root@new-host-6:~# hwclock
Sat Sep 17 00:31:03 2011 0.000000 seconds
------- cut here -------

Seems like a good thing to add to me.

3. second i2c bus is not detected:
------- cut here -------
root@new-host-6:~# ls -l /dev/i2c-*
crw------- 1 root root 89, 1 Jan 1 01:00 /dev/i2c-1
crw------- 1 root root 89, 3 Jan 1 01:00 /dev/i2c-3
------- cut here -------

I wonder if this is related to #1.

4. This request probably is for Koen, but would it be possible to add
driver for rt2870 chipset?
------- cut here -------
root@new-host-6:~# opkg search .\*2870.\*
root@new-host-6:~# uname -a
Linux new-host-6 3.0.4+ #1 Thu Sep 1 17:16:44 CEST 2011 armv7l GNU/Linux
------- cut here -------

I just built the kernel and I'm seeing this module wasn't built,
despite being build for the 2.6.39 version according to
http://www.angstrom-distributions.org/repo. I'll take a look as I'm
trying to do some kernel updates.

jkridner · September 18, 2011, 12:49am

Joel,

Can you start doing regular rebuilds as the repositories are updated?
Perhaps you can somehow use the existing build servers?

Also, can you include all the specific tags for the repositories such
that things can be rebuilt? With your current layers.txt approach,
not only do you fork people from upstream work, you don't let them
know which particular commit id works. If you want to provide a
layers.txt, include the exact commit ids in that file.

Lastly, can you follow-up on the upstream requests? I know this is a
part-time task for you, but a bit of on-going output is required here.
Automation can be your best friend.

Regards,
Jason

piranha32 · September 18, 2011, 1:15am

Interesting. I wonder what is going on with that I2C bus. Those
commands really don't belong in the boot-up script, so that is
something to clean-up, but it is interesting that the bus isn't
responding.

Looks like the errors can be generated by the following lines in uEnv.txt:
lcd1=i2c mw 40 00 00; i2c mw 40 04 80; i2c mw 40 0d 05; i2c mw 40 0d
15; i2c mw 40 0c 25; mw 49056090 10000000
lcd2=i2c mw 40 04 30; i2c mw 40 0c 21; i2c mw 40 04 80; i2c mw 40 04
70; i2c mw 40 04 60
lcd3=i2c mw 40 04 50; i2c mw 40 04 40; i2c mw 40 04 30; i2c mw 40 04 20

What are these commands supposed to do?

4. This request probably is for Koen, but would it be possible to add
driver for rt2870 chipset?
------- cut here -------
root@new-host-6:~# opkg search .\*2870.\*
root@new-host-6:~# uname -a
Linux new-host-6 3.0.4+ #1 Thu Sep 1 17:16:44 CEST 2011 armv7l GNU/Linux
------- cut here -------

I just built the kernel and I'm seeing this module wasn't built,
despite being build for the 2.6.39 version according to
http://www.angstrom-distributions.org/repo. I'll take a look as I'm
trying to do some kernel updates.

Thanks.

One more question, about spi: I can see spi devices in /sys, but there
are no device nodes in /dev. Aren't they supposed to be created
automatically? Or is it a matter of pin muxing?

j.

Joel_A_Fernandes · September 18, 2011, 1:17am

Hi,

Sorry for the late reply.

Joel,

I've just boot the R2 on my board and I'd like to share a few comments
from the first run:

1. before loading the kernel, u-boot complains a lot about problems
with i2c bus 1. Is this normal? I have Trainerboard attached to my xM:
------- cut here -------
Texas Instruments X-Loader 1.5.1 (Aug 26 2011 - 21:46:42)
Beagle xM
Reading boot sector
Loading u-boot.bin from mmc

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

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

In: serial
Out: serial
Err: serial
Beagle xM Rev A
Recognized Tincantools Trainer board (rev 0 0)
Die ID #65f200001bf00000015739ea07019027
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
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
I2C read: I/O error
Error writing the chip.
Setting bus to 0
Loading file "/boot/uImage" from mmc device 0:2 (xxa2)
3363388 bytes read
------- cut here -------

These commands are for LCD. Connecting any other device but the ULCD
panel to the expansion causes these errors. Ideally we'd want to check
if defaultdisplay=lcd and then execute the commands if true. Can you
comment out the i2c commands in the the uEnv.txt on your SD Card?

2. startup scripts do not set the time from rtc:
------- cut here -------
new-host-6 login: root
Last login: Thu Jan 1 01:00:31 BST 1970 on ttyO2
root@new-host-6:~# date
Thu Jan 1 01:04:01 BST 1970
root@new-host-6:~# hwclock
Sat Sep 17 00:31:03 2011 0.000000 seconds
------- cut here -------

Sure will look into this

3. second i2c bus is not detected:
------- cut here -------
root@new-host-6:~# ls -l /dev/i2c-*
crw------- 1 root root 89, 1 Jan 1 01:00 /dev/i2c-1
crw------- 1 root root 89, 3 Jan 1 01:00 /dev/i2c-3
------- cut here -------

No idea why! Devices connected to i2c2 on the expansion such as LCD
panel and camera are working fine. I am not sure but aren't these
device nodes created after a device successfully acquires the bus?

Thanks,
Joel

Joel_A_Fernandes · September 18, 2011, 1:25am

Hi Jason,

Joel,

Can you start doing regular rebuilds as the repositories are updated?
Perhaps you can somehow use the existing build servers?

Ideally we'll want to run through testing, and after adding any
features requested. Are you ok with pushing images just build-tested
from updated repositories (regularly)?

Also, can you include all the specific tags for the repositories such
that things can be rebuilt? With your current layers.txt approach,
not only do you fork people from upstream work, you don't let them
know which particular commit id works. If you want to provide a
layers.txt, include the exact commit ids in that file.

I'd rather dump this information into /etc/angstrom-version , unless
its already doing so. Much cleaner no?

Lastly, can you follow-up on the upstream requests? I know this is a
part-time task for you, but a bit of on-going output is required here.
Automation can be your best friend.

Sure.

Thanks,
Joel

Joel_A_Fernandes · September 18, 2011, 1:46am

Ok I take that back, the camera I'm using cannot acquire the bus:

[ 3.497161] isp_register_subdev_group: Unable to get I2C adapter 2
for device mt9v113

and as for the lcd panel, the i2c commands are issued in U-boot. I
suspect this to be a problem possibly with the i2c driver in the 3.0
kernel we're using. Jason, your ULCD patches are based on the same 3.0
kernel right? and touch screen driver is able to communicate over i2c
right?

Thanks,
Joel