I had a rev B7 board earlier on which i installed Angstrom linux and
was able to boot without any problem.. i even got the latest u-boot
from git and was able to install it.
now i have got a new BeagleBoard XM rev B but when i follow the same
procedure
to boot angstrom as i followed for rev B7 it wont boot at all
i dont even get anything on the serial terminal..
but when i use the sd card which came with the beagle it boots into
the serial terminal and i get the angstrom login prompt.
i saw the contents of the SD card which came with the beagleboard XM..
it contains ramdisk.gz , usr.scr in additional to the files which are
required for booting i.e MLO , u-boot.bin , uImage..
as the booting is very slow due to ramdisk i dont want to use that..
does anyone know the procedure to boot Angstom linux or what files are
required..i dont want to use ramdisk..I want to use the traditional
way i.e just with MLO , u-boot.bin and uImage on first partition and
rootfs on second parition
I am a new BeagleBoard user myself but I hope my reply helps you. This
is what I did to create a bootable microSD card for Angstrom.
Step 1 - Buy at least a 4GB microSD card.
Step 2 - Open a terminal under Linux, and use gparted to create two
partitions (I mention gparted but its purely up to you if you wanna
use another tool to get the job done). One partition is FAT32 (at
least 100Mb) and set flags to boot, lba with label boot. Second
partition is ext3 which is the remaining space used to hold the
operating system. You label the second ext3 partition angstrom. Please
note that in order for gparted to do this, it unmounts the partitions
on the card so when the process is completed exit gparted and remount
the partitions. Once the partitions are mount, you should get two
icons showing up on your desktop under Linux. One should be boot and
second icon is angstrom.
Step 3 - Now that you have constructed a skeletal microSD card which
has a bootable FAT32 partition you need to copy the bootlader into the
first partition. You need to copy the files in the correct order.
Step 4 - Go to Narcissus and generate a build which should have the
necessary files (Beagleboard bootlader files are essential). Myself I
prefer generating a very simple build and then add the features I want
through opkg.
Step 5 - Once you have the compressed snapshot downloaded, expand it
into a folder of your choosing. Inside that folder, there should be a
folder labelled boot which contains the necessary files for your
bootable FAT32 partition which you have labelled boot. As mentioned
please copy the files in the correct order.
Step 6 - Now the last step is to expand the compressed snapshot into
your ext3 partition. Once that's done, you're pretty much there. I
would recommend you sync to make sure everything is OK and once you're
sure that the card is ready to remove, safely eject the card and
you're pretty much ready to go.
As fas as checking activity through serial, I use putty to get the job
done. I've been using both the serial port on my motherboard and a
couple of usb to serial interfaces. In case of using a USB serial
adapter, make sure you've got the right serial port in your serial
terminal software and that its showing up properly i.e drivers are
correctly installed.
thanks for the input but i know the standard procedure and it is
working without any problem
on BeagleBoard REV B7 but i wanted the same for BeagleBoard xM REV B
i copyed the user.scr which came with the BeagleBoard xM and got the
display working
but now my kernel stops in between saying
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
block(1,0)
i opened the user.scr file and came to the conclusion that
the problem is with the root which is specified in the file
the user.scr file is as below
mmc init
setenv dvimode 1024x768MR-16@60
setenv vram 16M omapfb.vram=0:8M,1:4M,2:4M
setenv console tty0 console=ttyS2,115200n8
if test "${beaglerev}" = "AxBx"; then
setenv rdaddr 0x81000000
setenv optargs mem=80M@0x80000000 musb_hdrc.fifomode=5
elif test "${beaglerev}" = "Cx"; then
setenv rdaddr 0x88000000
setenv ramroot /dev/ram0 rw ramdisk_size=131072 initrd=${rdaddr},128M
setenv optargs mem=80M@0x80000000 mem=128M@0x88000000
musb_hdrc.fifomode=5
else
setenv rdaddr 0x88000000
setenv ramroot /dev/ram0 rw ramdisk_size=131072 initrd=${rdaddr},128M
setenv optargs mem=80M@0x80000000 mem=384M@0x88000000
fi
run loadramdisk
led 0 off
run loaduimage
led 1 on
run ramboot
i think the problem is due to the
setenv ramroot /dev/ram0 rw ramdisk_size.... line
i dont want to boot to ramdisk
what should i specify
I strongly recommend not using FAT32 as the FAT partition. Use FAT or FAT16. FAT works better and we have seen issues on some cards trying to use FAT32.
)