Hi,
Here is the step by step procedure.
Google Code Archive - Long-term storage for Google Code Project Hosting.
Read it and do exactly what it says. That will result in a bootable SD card.
You can't follow the instructions exactly, because they are
inconsistent. For Rev C4 board owners there's a note saying:
'NOTE: If the board is a Rev C4, use the files located here
http://www.angstrom-distribution.org/demo/beagleboard/ instead of the
ones listed above.'
but on the recommended page several files are missing ( u-boot for
flash, ramdisk image, reset.scr and 'Regular script file')
Are they obsolete? Shall the C3 files be used instead? Are they
provided by other hidden repositories on the internet? Google doesn't
know about any "ramdisk_revc_v4.gz" file.
On the other hand on angstrom-distribution.org/demo/beagleboard/ there
are some extra files not known on BeagleboardRevC3Validation page and
sadly without any documentation about how to handle them:
Angstrom-Beagleboard-demo-image....rootfs.tar.bz2,
config-2.6.32-r70...beagleboard.config,
modules.tgz
...
Are any of them needed? All? Some?
It would be much easier understandable to give the user a list, which
files to copy where from for Rev C4 boards as done for C3.
Finally, what was working for me:
In my normal PC:
Formating the SD-card with the provided mkcard.txt script
Downloading the following files from http://www.angstrom-distribution.org/demo/beagleboard/
to a local directory and copying (in this order) to the SD card's
partition1:
MLO
u-boot.bin
uImage (You have to keep the name! Renaming to uImage.bin resulted in
'uImage not found' error)
x-load.bin.ift
Powering on the beagleboard with SD card plugged in and pressing USER
button this did succeed in loading the kernel, but was ending up in a
kernel panic because of missing init.
So copying
Angstrom-Beagleboard-demo-image-glibc-ipk-2010.3-
beagleboard.rootfs.tar.bz2
to SD's partition2 and unpacking there
# tar -xjvf Angstrom-Beagleboard-demo-image-glibc-ipk-2010.3-
beagleboard.rootfs.tar.bz2
provided the missing init and resulted in a usable Angstrom
installation.
After extracting the tar.bz2 can be removed.
minicom console still moans for some missing files :
<snip>
Hit any key to stop autoboot: 0
mmc1 is available
The user button is currently PRESSED.
reading user.scr
** Unable to read "user.scr" from mmc 1:1 **
reading uImage
3194800 bytes read
reading ramdisk.gz
** Unable to read "ramdisk.gz" from mmc 1:1 **
Booting from mmc ...
## Booting kernel from Legacy Image at 80200000 ...
Image Name: Angstrom/2.6.32/beagleboard
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3194736 Bytes = 3 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
<snip>
Where can we get user.scr and ramdisk.gz?
(mkinitrd is not known)
My 2 cents
Rainer