Problems with Angstrom demo

Hi all,

I've been wrestling with trying to get the latest Angstrom working
with my Beagle but for some reason they don't seems to like each
other. I've followed the elinux BeagleBoardBeginners by the letter (I
guess I've messed something up but that's my feeling at least) and all
I get from the Beagle is:

OMAP3 beagleboard.org # boot
reading uImage

0 bytes read
Wrong Image Format for bootm command
ERROR: can't get kernel image!

I've managed to install Debian so I know I've got a healthy board.
Here's what things look like:

The files I got was:
http://www.angstrom-distribution.org/demo/beagleboard/MLO
http://www.angstrom-distribution.org/demo/beagleboard/u-boot.bin
http://www.angstrom-distribution.org/demo/beagleboard/uImage-2.6.28-r12-beagleboard.bin
http://www.angstrom-distribution.org/demo/beagleboard/Angstrom-Beagleboard-demo-image-glibc-ipk-2009.X-test-20090203-beagleboard.rootfs.tar.bz2

I copied the three first over to a fresh (I've done it several time
with different uImage but formated each time to make sure MLO gets
there first) fat32 partition. The files look fine:
md5sum /mnt/*
6ae111d0b3bad7673697187a8e3ee4b6 /mnt/mlo
5f4ed3a8d5a368d3d7eee25f87f29404 /mnt/u-boot.bin
a194bede96436d6ee17168ad9a29fefc /mnt/uImage

Matches the md5sums from the site. I then untar the files from the
demo image directly to the second partition like it says in the wiki.
Next step being boot I've tried with:
OMAP3 beagleboard.org # printenv
bootcmd=mmcinit; fatload mmc 0:1 0x80300000 uImage; bootm 0x80300000
bootargs=console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2
rootwait rootfstype=ext3 video=omapfb:vram:2M,vram:4M,mode:640x480@60

and
OMAP3 beagleboard.org # setenv bootargs 'console=ttyS2,115200n8
root=/dev/mmcblk0p2 rw rootwait'
OMAP3 beagleboard.org # setenv bootcmd 'mmcinit;fatload mmc 0 80300000
uImage;bootm 80300000'

But all I get is the "Wrong Image Format for bootm command".

I'm pretty sure I'm the one screwing something up along the way as I
haven't found anyone with similar problems, can someone please tell me
where that mistake is done?

/Jon

isn't that supposed to be '0x0x82000000'?

regards,

Koen

Hi,

Tried it just now but it gives me the same result:
OMAP3 beagleboard.org # setenv bootcmd 'mmcinit; fatload mmc 0:1
0x82000000 uImage; bootm 0x82000000'
OMAP3 beagleboard.org # boot
reading uImage

0 bytes read
Wrong Image Format for bootm command
ERROR: can't get kernel image!

Also tried it with my debian SD card and it works with both addresses:
reading uImage

2163908 bytes read
## Booting kernel from Legacy Image at 80300000 ...
   Image Name: Linux
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 2163844 Bytes = 2.1 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

and

reading uImage

2163908 bytes read
## Booting kernel from Legacy Image at 82000000 ...
   Image Name: Linux
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 2163844 Bytes = 2.1 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

I've tried angstrom with three different SD cards now, and I've tried
downloading it all again but I still get the same error.

Could my U-Boot version on the board be too old? "U-Boot 1.3.3 (Jul 10
2008 - 16:33:09)", if so how do I upgrade it?

I'm really at a loss here

/Jon

Matches the md5sums from the site. I then untar the files from the
demo image directly to the second partition like it says in the wiki.
Next step being boot I've tried with:
OMAP3 beagleboard.org # printenv
bootcmd=mmcinit; fatload mmc 0:1 0x80300000 uImage; bootm 0x80300000

isn't that supposed to be '0x0x82000000'?

regards,

Koen

Hi,

Tried it just now but it gives me the same result:
OMAP3 beagleboard.org # setenv bootcmd 'mmcinit; fatload mmc 0:1
0x82000000 uImage; bootm 0x82000000'
OMAP3 beagleboard.org # boot
reading uImage

0 bytes read

You haven't read the file for some reason,

Wrong Image Format for bootm command
ERROR: can't get kernel image!

Therefore this fails, as there is no kernel in the location you mentioned.

Also tried it with my debian SD card and it works with both addresses:
reading uImage

What is there in your debian SD card ? is it the same uImage or
different one. I am not sure if you have copied the uImage properly on
to SD card. Try reading any other file, like,
mmcinit
fatload mmc 0 0x80300000 u-boot.bin
go 0x80300000

This should boot u-boot, it should confirm that file copy is going on properly.

Also try
fatls mmc 0

It should list the files on MMC

2163908 bytes read
## Booting kernel from Legacy Image at 80300000 ...
  Image Name: Linux
  Image Type: ARM Linux Kernel Image (uncompressed)
  Data Size: 2163844 Bytes = 2.1 MB
  Load Address: 80008000
  Entry Point: 80008000
  Verifying Checksum ... OK
  Loading Kernel Image ... OK
OK

and

reading uImage

2163908 bytes read
## Booting kernel from Legacy Image at 82000000 ...
  Image Name: Linux
  Image Type: ARM Linux Kernel Image (uncompressed)
  Data Size: 2163844 Bytes = 2.1 MB
  Load Address: 80008000
  Entry Point: 80008000
  Verifying Checksum ... OK
  Loading Kernel Image ... OK
OK

I've tried angstrom with three different SD cards now, and I've tried
downloading it all again but I still get the same error.

Could my U-Boot version on the board be too old? "U-Boot 1.3.3 (Jul 10
2008 - 16:33:09)", if so how do I upgrade it?

this u-boot might not work for Angstrom but that is different problem,
in your case it is still in preliminary stage and it should have
worked till booting the kernel image.

Any ways, you can refer to
Google Code Archive - Long-term storage for Google Code Project Hosting. to
upgrade to latest u-boot. It is simple, just copy the binaries on
MMC/SD card and power on the board while you keep the USER Key
pressed. It should boot the new u-boot.

Regards,
Khasim

U-boot 1.3.3 doesn't work with Angstrom. You need to upgrade. But
the easiest way to get a new U-Boot is to upgrade the X-Loader in the
on-board Nand to 1.4.2. Then the X-Loader will automatically use the
U-Boot that is on the MMC card.

Look at Section III here for instructions:
http://code.google.com/p/beagleboard/wiki/HowToGetAngstromRunning

Good luck.

Best regards,
Geof

Sorry for top posting but I'm trying to reply to both Geof and Khasim
without adding too much traffic.

Thanks all for the replies.

After Khasim's email I tried copying the files from my debian card fat
partition to my hdd, then formating the first partition on one of the
angstrom cards, and then copying the files on there:
6ae111d0b3bad7673697187a8e3ee4b6 mlo
5f4ed3a8d5a368d3d7eee25f87f29404 u-boot.bin
291d2205d7dda53eec07ca21ce7c7a2b uImage

This uImage is one I made following the elinux wiki page
BeagleBoardDebian ie 'mkimage -A arm -O linux -T kernel -C none -a
0x80008000 -e 0x80008000 -n "Linux" -d ./temp/boot/vmlinuz-*
/mnt/uImage'. With those files my beagle booted Angstrom without any
problems, first setting up the packages taking a little time but as
expected.

I was able to login and also got mplayer to play a movie (audio fails
but I that's another problem). Mouse, keyboard and external hdd
working fine.

With this at least semi-success (only audio lacking) I'm wondering
about the U-boot, this one seems to be an old one I had laying about
(strings says "U-Boot 1.3.4-rc2 (Aug 18 2008 - 19:03:08)") :
md5sum u-boot.bin
5f4ed3a8d5a368d3d7eee25f87f29404 u-boot.bin

So it seems me getting debian to work was just me being a bit lazy and
not deleting this old file?

I'll try to upgrade the U-boot, one thing that confuses me a bit is
the different instructions on the page you mailed and
http://elinux.org/BeagleBoardDebian#Upgrading_u-boot_.282.6.27.27s_and_later.29
it's the exact same procedure except your page wants x-load.bin.ift
while elinux says u-boot.bin.

Should I do both or just the x-load? Will I still be able to run
debian after that?

Thanks
/Jon

There are two (at least) things in the NAND normally: X-loader and U-
boot.

The sequence of events is: OMAP chip looks for X-Loader in Nand and
boots that. X-loader in Nand looks for U-boot and boots that. U-boot
looks for uImage and boots that.

So your X-loader (1.4.1) doesn't look on the mmc card and always uses
the u-boot in NAND. You could upgrade the U-boot in NAND and solve
the problem. But...

With X-loader 1.4.1 (what ships with BB), if you don't use the "User
Button" at power on, then it ignores the u-boot that is on the mmc
card.

With X-loader 1.4.2 (the latest), it checks the mmc card, and if there
is a valid u-boot there, then it uses the one on the mmc.

So the simplest upgrade is to just upgrade the X-loader in NAND. Then
you can use the u-boot on the MMC. So I don't normally upgrade the U-
boot in NAND. But I don't think it would hurt.

Best regards,
Geof

Just wanted to confirm that everything works fine now. Audio started
working after upgrading the x-loader, my pico projector is showing
movies on my wall, and I'm one much happier beagle owner :slight_smile:

Thanks for the clarification and the help

/Jon

Koen Kooi 写道:

Hi all,

I've been wrestling with trying to get the latest Angstrom working
with my Beagle but for some reason they don't seems to like each
other. I've followed the elinux BeagleBoardBeginners by the letter (I
guess I've messed something up but that's my feeling at least) and all
I get from the Beagle is:

OMAP3 beagleboard.org # boot
reading uImage

0 bytes read
Wrong Image Format for bootm command
ERROR: can't get kernel image!

I've managed to install Debian so I know I've got a healthy board.
Here's what things look like:

The files I got was:
http://www.angstrom-distribution.org/demo/beagleboard/MLO
http://www.angstrom-distribution.org/demo/beagleboard/u-boot.bin
http://www.angstrom-distribution.org/demo/beagleboard/uImage-2.6.28-r12-beagleboard.bin

http://www.angstrom-distribution.org/demo/beagleboard/Angstrom-Beagleboard-demo-image-glibc-ipk-2009.X-test-20090203-beagleboard.rootfs.tar.bz2

I copied the three first over to a fresh (I've done it several time
with different uImage but formated each time to make sure MLO gets
there first) fat32 partition. The files look fine:
md5sum /mnt/*
6ae111d0b3bad7673697187a8e3ee4b6 /mnt/mlo
5f4ed3a8d5a368d3d7eee25f87f29404 /mnt/u-boot.bin
a194bede96436d6ee17168ad9a29fefc /mnt/uImage

Matches the md5sums from the site. I then untar the files from the
demo image directly to the second partition like it says in the wiki.
Next step being boot I've tried with:
OMAP3 beagleboard.org # printenv
bootcmd=mmcinit; fatload mmc 0:1 0x80300000 uImage; bootm 0x80300000

isn't that supposed to be '0x0x82000000'?

regards,

Koen

Hi,

This is my u-boot script:

setenv ownkernel_bootargs setenv bootargs 'console=ttyS2,115200n8 ramdisk_size=8192 root=/dev/ram0 rw rootfstype=ext2 initrd=0x81600000,8M nohz=off video=omapfb:vram:2M,vram:4M,mode:720p60'
setenv ownkernel_bootcmd mmcinit\; fatload mmc 0 0x80000000 uImage\; fatload mmc 0 0x81600000 rd-ext2.bin\; bootm 0x80000000
setenv boot_ownkernel run ownkernel_bootargs\; run ownkernel_bootcmd

setenv android_bootargs setenv bootargs 'console=ttyS2,115200n8 noinitrd root=/dev/mmcblk0p2 rw rootwait init=/init video=omapfb:mode:1280x720@50 rootfstype=ext3 rw nohz=off'
setenv android_bootcmd mmcinit\; fatload mmc 0 0x80300000 uImage\; bootm 0x80300000
setenv boot_android run android_bootargs\; run android_bootcmd

setenv angstrom_bootargs setenv bootargs 'console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait initrd=0x81600000,8M nohz=0ff video=omapfb:vram:2M,vram:4M,mode:720p60'
setenv angstrom_bootcmd mmcinit\; fatload mmc 0 0x80200000 uImage\; bootm 0x80200000
setenv boot_angstrom run angstrom_bootargs\; run angstrom_bootcmd

setenv bootcmd run boot_android

regards,

George.Qiao