Booting Beagle Software

The two cases that need to be considered are: 1) the factory installed u-boot is running fine and 2) the NAND flash needs to be completely replaced back to factory conditions.

this page is linked to for the HP Boot tool, i found it here.

http://www.bootdisk.com/pendrive.htm

Hi, I have this problem.

kernel panic - not syncing: VFS:Unable to mount root fs ...

Can somebody suggest me, how to solve this.

Hi,

It worked, it mounted File system.

Just followed

http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat

since i used Ubuntu 8.04 LTS Geometry of SD card options was not working fine me. If you need any help on this pls let me know.

Bootargs for NAND (JFFS2) File System) TBD Bootargs for NFS (using Ethernet over USB Dongle) TBD

what it mean TBD

TBD means "to be done"

i m trying to boot 4m mmc plus card having total 13 pin just after partioning and adding image files to it.

it displays Texas Instruments X-Loader 1.41 Starting on with MMC Reading boot sector 265136 Bytes Read from MMC Starting OS Bootloader from MMC... U-Boot 2009.01-00013-g52eddcd (Feb 03 2009 - 22:25:11) OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz OMAP3 Beagle board + LPDDR/NAND DRAM: 128 MB NAND: 256 MiB Using default environment In: serial Out: serial Err: serial Board revision Ax/Bx Serial #2cee00030000000004013f790301b004 Hit any key to stop autoboot: 0 reading boot.scr Unable to read "boot.scr" from mmc 0:1 reading uImage.bin Unable to read "uImage.bin" from mmc 0:1 Booting from nand ... NAND read: device 0 offset 0x280000, size 0x400000

4194304 bytes read: OK

PROVIDE SOLUTION

biswajit.jun, Which version of u-boot do you use? I had same when I tried version on Angstrom demo files (it messes with bootup environment). Try older version like 1.3.3 - it works OK.

So I finally got the board speaking through hyperterminal. I however am having trouble getting it to recognize the SD card and boot with MMC? Anyone have any suggestions?

Hi, I have this issue wherein I get CRC verification failed when I do a bootm after copying the kernel image from SD to memory.. I tried 2-3 different images, but in vain. I tries the same image given for verification in google code.. pls advice... what are the possible reasons? The image is fully copied to memory... no problem there. Thanks, -Rajesh

Whats the best way to set up the fstab for a board booting from MMC?

I get a bunch of errors on startup, and I'm assuming they're from trying to mount the main filesystem as flash...

Guys, After creating the two partitions, I copied the files in the order specified on the beagleboard page, http://code.google.com/p/beagleboard/wiki/BeagleboardRevCValidation to partition labled W95 FAT32(LBA)

Disk /dev/sdb: 2032 MB, 2032664576 bytes 255 heads, 63 sectors/track, 247 cylinders Units = cylinders of 16065 512 = 8225280 bytes

Disk identifier: 0x112a1eb6

Device Boot Start End Blocks Id System

/dev/sdb1 1 50 401593+ c W95 FAT32 (LBA)

/dev/sdb2 51 247 1582402+ 83 Linux

Command (m for help):

MLO u-boot.bin u-boot-f.bin ramdisk.gz uImage.bin boot.scr x-load.bin.ift normal.scr

The instructions did not specify what files go to the respective partitions. So, I copied everything onto the FAT32 partition.

I just cannot get the beagleboard(Rev B7) to boot from SD card.I do NOT know what else to try. This is frustrating. Please help.

Hi gurushunkara, I used the Angstrom files on a revision C3 boards and it worked quite well, so I suggest you try Angstrom first. You say "I just cannot get the beagleboard(Rev B7) to boot from SD card" - can you explain what happens when you boot?

Can other versions of Linux other than the Angstrom be run on the Beagle Board..I have to run matlab on the linux (this is the reason !) !

I'm in the same situation as gurushunkara. I have beagleboard Rev C3 with 2GB card. I have tried with 8GB and 1GB card. I just can't get it to boot from SD card. it starts up with beagle image, then beagle image is wiped away, but pawns are left. then board just hangs...

Please help!

try to copy "MLO u-boot.bin u-boot-f.bin ramdisk.gz uImage.bin boot.scr x-load.bin.ift normal.scr" files one by one on you mmc and rename it before copy one other file, and START by MLO file.

I have purchased a beagleboard. On powering it up using USB port (from Laptop) it keeps printing "Texas Instruments X-Loader ....." continuously. And no LED except POWER LED gets on.

But whe I use AC power then there is no output on console. But it seems that board is booting as after some time 3 LEDs get oned.

I am not sure whether its a hardware issue or what.

I used the files and followed the procedure from http://code.google.com/p/beagleboard/wiki/BeagleboardRevCValidation

I get following messages:

U-Boot 2009.01-dirty (Feb 19 2009 - 12:23:21)

I2C: ready OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz OMAP3 Beagle board + LPDDR/NAND DRAM: 256 MB NAND: 256 MiB Using default environment

MUSB: using high speed In: serial usbtty Out: serial usbtty Err: serial usbtty Board revision C Serial #662c0003000000000403230910011005 Hit any key to stop autoboot: 0 reading boot.scr

Unable to read "boot.scr" from mmc 0:1

I also renamed the normal.scr as boot.scr and re-tried, it didn't continue further. Kindly help.

!!!Need Help !!! I got the kernel compiled for power management features on Beagal. The Image compiled I renamed to uImage and downloaded to the SD card with the proper sequence. Beagal loads the image and ramdisk and after some time throws the error "Wrong Image format " Is this the problem with Kernel image or download process?

Thanks in advance.. -Pandurang

As with a few other people above, I had a problem with my initial bootup after preparing the SD card: "Wrong Image Format for bootm command" and "ERROR: can't get kernel image!"

The problem in my case was the version of U-Boot. I was running the "U-Boot 2009.01-dirty (Feb 19 2009 - 12:23:21)" version, which came from an Angstrom distro. This version either doesn't support boot.scr, or leaves some settings in NAND that interfere with the Ubuntu boot.scr - not sure which.

The solution is to upgrade to a more recent version of U-Boot -- the 2009.11 rc1 version currently listed at http://elinux.org/BeagleBoardUbuntu#Upgrade_U-Boot did the trick for me.

If you're not sure that U-Boot is the problem, you can try manually entering the commands that are in the Ubuntu boot.scr file. In my case, Ubuntu booted OK when I did so.

HTH,

Dan.

I connected serial port to system using USB to Serial connecter, later given the power supply, in terminal junk characters are showing.Any help?

I downloaded files from Angstrom and copied as per guidelines. When I tried to load uImage using the command fatload mmc 0 80000000 uImage , it is giving the error Unable to read "uImage" from mmc 0:1.

what will be the issue, any idea? Also on what basis we are deciding the address of uImage (80000000)?

Thanks, San

Hi, I tried to mount root fs using NFS but I get a kernel panic. The last traces I have are:

VFS: Mounted root (nfs filesystem) on device 0:12 Freeing init memory: 172k Warning: unable to open an initial console Kernel panic - not syncing : No init found. try passing init= option to kernel

The kernel i loaded from mmc. When I use the same root fs and kernel on SD card all is working.

To mount root fs using NFS I have processed as following

1. boot with uImage and rootfs on SD card

2) When boot complete create /dev/nfs directory 3) Start eth0 interface (ethernet over USB adapter) and ping NFS server IP.

Beagleboard# netcfg eth0 up Beagleboard# netcfg eth0 dchp Beagleboard# netcfg Beagleboard# ping NFS_SERVER_IP

4)Reset board and stop boot to update environement variable using commands:

Beagleboard# setenv bootargs 'console=ttyS2,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=NFS_SERVER_IP:/ROOT_FS_PATH,nolock,rsize=1024,wsize=1024,rootdelay=2' Beagleboard# setenv bootcm 'mmc init; faltload mmc 0 84000000 uImage; bootm 84000000' Beagleboard# boot

I alos tried:

Beagleboard# setenv bootargs 'console=ttyS2,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=NFS_SERVER_IP:/ROOT_FS_PATH,nolock,rsize=1024,wsize=1024,rootdelay=2 init=/init' with no success.

I there something to change between root fs on SD card and on NFS server to make init work? As I am new on Beagleboard, Is it possible for somebody to give a full step by step explanation (or link to explanation) on how to mount root fs from NFS server on Beagleboard C3 using ethernet over USB dongle? Thanks for your help, Michel

@michel I just hit the same problem and found out it's my host nfs setup that has problems. Adding the line "/my_nfs_dir_path (rw,no_root_squash,no_all_squash,sync)" to /etc/exports and restarting nfs service on my nfs host fixed it for me.

Hi, can anyone tell me what is the minimum SD card storage capacity required?? I need to buy a new SD card for this, but dont want to spend extra money on space i dont require. so wats the recommended size? Also, does anyone know if android rowboat can be loaded and booted from flash?? if so can u plz give me a link to such a tutorial? thnks a lot!

i have a problem in communication with the BB. I can get the messages coming from the BB but i can't send any commands. What could be wrong in my setup ? - i tried to use almost all the terminal emulators known with the same results !!

@ cspatlolla: are you sure you correctly configured the COM port to 115200 baudrate ? i got the same output and the COM was configured to be 9600 bps.

Regards, -- A.El-Saeed

A.El-Saeed,

Had the same problem. Mine was due to using an incorrect serial cable. You must use a Null-modem cable. Other serial cables have the rx/tx lines wired differently. Null-modem cables are wired correctly.

John

cspatlolla,

Had the same problem on a BB C4. I got "40W" with some additional junk characters.

In short, the TI ROM routine is looking for some very specific things on the SD card, if any one of them is wrong, you get the "40W".

Here's what happened. I had everything booting up nicely from an 8G SDCard. I then typed in "nand unlock" and "nand erase" at the bootloader prompt as described here http://code.google.com/p/beagleboard/wiki/BeagleNANDFlashing (don't ask me why I did that).

No problem I thought. I can reflash the bootloader, x-loader, etc. from the SD Card. Using the SDCard which only a minute earlier worked like a charm, now failed with "40W". Conclusion: the MMC routines in the bootloader and the kernel factory installed on the BB, seem to be more forgiving than the TI ROM code.

After trying a bunch of different things:

• used HP utility to format the disk (my version is 2.1.8 which may be incorrect according to some comments in various pages out there)
• tried 8G, 2G, 16M cards (saw some comments about certain sizes being too big and I thought I possibly might have a faulty SD card)
• tried "SDHC" and just "SD" cards (based on a TI wiki page comment)
• tried the USB recovery method (from WinXP/cygwin, didn't work at all)
• Stopped using Windows XP and started using Linux (Ubuntu 9.1) as the host.
• tried the mkcard.txt file in the angstrom distribution; It uses mkfs.vfat, vs mkfs.msdos (which may or may not be the same); It also has the DD command at the top of the script (don't know if that's significant or not).
• tried sfdisk; tried fdisk
• tried two partitions vs one partition (again, don't know if it's significant)
• wrote a shell script to reformat and load the SD card, so I could absolutely, positively state that MLO is the first file on the virgin partition (as it has to be).
• various other tries: cursing, yelling loudly, watching copious sci-fi TV, playing heavy metal at 11, etc.

I finally used the procedure here:

http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat

which failed (again) until I followed the comment by "challinan, Aug 05, 2009" and used "51", not "+50" for the size of partition #1. Voila it worked.

Well, except for one time, when I got the "40W" again. I pulled the SD Card out and reseated it and it started working again.

Lesson learned: there's a lot of chaff out there. I hope I'm not contributing to it now but I have successfully created additional SD cards using the same technique so I have a tiny bit of evidence it's good.

Next step, loading angstrom...

John

BTW. Here's the script for creating the partitions. Take note of the copyright (i.e. it's not mine!)

To invoke it use "sudo ./mkcard /dev/sdf" . The 'sdf' part is what the SD card shows up as on my Ubuntu 9.1. Yours will be different and how to locate it is described in the first couple of steps in

http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat

#! /bin/sh
# mkcard.sh v0.5
# (c) Copyright 2009 Graeme Gregory <dp@xora.org.uk>
# Licensed under terms of GPLv2
#
# Parts of the procudure base on the work of Denys Dmytriyenko
# http://wiki.omap.com/index.php/MMC_Boot_Format

# JA:
#  http://code.google.com/p/beagleboard/wiki/LinuxBootDiskFormat
# and
#  mkcard.txt at http://www.angstrom-distribution.org/demo/beagleboard/
# used 2GB microSD 

export LC_ALL=C

if [ $# -ne 1 ]; then
	echo "Usage: $0 <drive>"
	exit 1;
fi

DRIVE=$1

umount ${DRIVE}1

SIZE=`fdisk -l $DRIVE | grep Disk | grep bytes | awk '{print $5}'`
echo DISK SIZE: $SIZE bytes

CYLINDERS=`echo $SIZE/255/63/512 | bc`
echo CYLINDERS: $CYLINDERS

sfdisk -D --heads 255 --sectors 63 --cylinders $CYLINDERS $DRIVE <<EOF
,51,c,*
,,,-
EOF

sleep 1

echo Resulting Partition table:
fdisk -l $DRIVE

umount ${DRIVE}1
mkfs.msdos -F 32 -n "boot" ${DRIVE}1

umount ${DRIVE}2
mkfs.ext3 -L "rootfs" ${DRIVE}2

Hi

I am getting an error when trying to read the uImage. when i type the fatload command and hit enter it reads image then says 'unable to read "uImage" from mmc 0:1. i have the latest uboot kernal and everything else is upto date.

How do we know what location the uImage is at why 0x80000000 how do i check that my image is at this location ? Cheers Phil

U-Boot 2009.11-svn12 ( 8��月 16 2010 - 17:25:40) OMAP3530-GP ES3.1, CPU-OPP2 L3-165MHz OMAP3 SBC3530 + LPDDR/NAND I2C: ready DRAM: 128 MB NAND: 256 MiB In: serial Out: serial Err: serial Ethernet MAC address: 02:c0:05:01:b0:05 Die ID #170000040000000004036ac00501b005 Net: smc911x-0 Hit any key to stop autoboot: 0 mmc1 is available reading boot.scr Unable to read "boot.scr" from mmc 0:1 reading uImage 3195484 bytes read Booting from mmc ... ## Booting kernel from Legacy Image at 82000000 ...

Image Name: Angstrom/2.6.32/beagleboard Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3195420 Bytes = 3 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK

booting stops here.. what could be the problem for that? please suggest me some solutions

Hi im having the same problem as above. I get slight further to done, booting the kernel and then it stops any help would be great

I just started getting this problem when dealing with my base-image. It seems like nothing obvious bad is happening. Perhaps thats all it is to this uImage. In any case if you are having trouble I recommend trying out this page. It has a shell script that creates your Angstrom Image for you. It worked for me on first try! :) (Well actually a little more cause I was dumbnut and saved uImage as uImage.bin, which gave me unable to read "uImage" error):

http://www.angstrom-distribution.org/building-angstrom

cheers. -V

my kernel hung at OK starting kernel.

This is from torvald's 2.6 mainstream kernel (not omap git tree) and running on beagleboard xm.

Does anyone know what's the problem? thanks

A Dumb question. Why FAT32 is recommended for boot partition? Any specific reasons?

I got solution of error "unable to open initial consol" first check whether your /dev folder is having files or not and make sure that you using uImage made from same kernel version of which you using as root fs.

use this also may it helps you.. OMAP3 beagleboard.org # setenv bootargs console=ttyS2,115200n8 noinitrd root=/dev/mmcblk0p1 init=/linuxrc rootfstype=ext2 rw rootdelay=1 nohz=off

Better to make rootfs using rootstock.

Hello,

I get the following output on the terminal and the booting halts. What might be going wrong here?

Texas Instruments X-Loader 1.4.4ss (Jul 28 2010 - 16:59:13) Beagle xM Rev A Reading boot sector Loading u-boot.bin from mmc

U-Boot 2010.12-rc3 (Jan 06 2011 - 09:52:08)

OMAP3630/3730-GP ES2.0, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 512 MiB

Bootargs for NAND (JFFS2) File System):

setenv bootargs 'console=ttyS2,115200n8 mpurate=auto buddy=none camera=none vram=12M omapfb.mode=dvi:1280x1024MR-16@60 omapdss.def_disp=dvi root=ubi0:beagleboard-rootfs ubi.mtd=4 rootfstype=ubifs'

- Works for me

I liked it much and its really appreciative. http://www.memoryclearance.com/catalogsearch/result/?q=a2251711&x=0&y=0

I am using beagle board-xm which i boot from sd/mmc card with kernel image and file system.MMC card is made bootable and configured correctly. I had already boot beagle board,mounted the file system and worked with it,It was working properly. But suddenly due to some unknown reasons, Now as I setup the hardware and try to boot the beagle board it shows following statements and repeatedly shows it. << Texas Instruments X-Loader 1.5.0 Beagle xm >> This two lines are repeatedly shown by the board,it doesn't boot...Looks like u-boot is not booting properly or it gets reset repeatedly..why is this happening?

Ok, please assist.

I'm able to format my 2Gb SD card using the mkcard.txt that create a boot partition of 75 MB and an Angtrom partition of 3.5 GB.

Bassically, here's what I,do :

1- Copy the MOL (1 file) to the boot partition 2- Copy the u-boot.img (1 file) to the boot partition 3- Untar the Angstrom-Beagleboard-.tar.bz2 to the Angstrom partition (no error) 4- Unmount the SD card, plug it into the Beagleboot and powerup

and I get this error :

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

Please assist!

Hi All,

I have a terrible issue. My beagleboard OMAP3530-GP Rev C1/C2/C3 came with a USB to Supply cable and therefore I plugged the USB to the PC and the other end fitted neatly to the supply 5V. In the beginning it booted very well once I had copied MLO, u-boot.bin uInitrd and uImage all from the formatted SDcard. However, in a freaky moment I did " nand erase 0 80000 " and "nand erase 80000 160000 " after this I rebooted my board only to find except the power on LED, none of the other LEDs lighting up :( Also, the minicom shows me a set of junk character. I tried pressing reset, user buttons etc. I even tried a UART recovery procedure. However the procedure stalls at "./ukermit -p /dev/ttyUSB0 -f u-boot.bin" and after 2-3 min I just plugged out the power USB cable as I wasn't able to transfer the uboot.bin. PLEASE HELP. What is the problem?