Booting the beagleboard

Hi!

I'm trying to boot of SD (using MLO on mmcblk0p1) to SD (ext2
partition on mmcblk0p2), but I'm having some troubles with it.

What I did:

1) Have uboot load the image and boot it:
  set bootargs "console=ttyS2,115200n8 noinitrd root=/dev/mmcblk0p2
rootdelay=5 rootfstype=ext2"
  set bootcmd 'mmcinit ; fatload mmc 0:1 0x80000000 uimage.ti ;
bootm' ; saveenv

2) prepare card according to http://code.google.com/p/beagleboard/wiki/BootingBeagleBoard

3) reset

The bootlog with the kernel from code.google:

Linux version 2.6.22.1-omap1 (root@fedoraserver) (gcc version 4.2.0
20070413 (prerelease) (CodeSourcery Sourcery G++ Lite 2007q1-21)) #2
Wed Mar 26 16:39:33 IST 2008
CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7), cr=00c5387f
Machine: OMAP3 Beagle board

[...]

Kernel command line: "console=ttyS2,115200n8 noinitrd root=/dev/
mmcblk0p2 rootdelay=5 rootfstype=ext2"

[...]

drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
<3>Root-NFS: No NFS server available, giving up.
Root-NFS: No NFS server available, giving up.
<3>VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "<NULL>" or unknown-block(2,0)
VFS: Cannot open root device "<NULL>" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available
partitions:
Please append a correct "root=" boot option; here are the available
partitions:
<0>Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
block(2,0)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
block(2,0)

And there are no messages from the mmc subsystem, so it looks like
this kernel doesn't have SD support.

linux-omap git + dirks patches gives:

## Booting image at 80000000 ...
   Image Name: Angstrom/2.6.24+2.6.25rc7-git039
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 1343056 Bytes = 1.3 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
OK

Starting kernel ...
<silence>

So something is wrong there as well.

I'm going to try rebuilding 2.6.22 with SD support.

regards,

Koen

Hi Koen,

Hi!

I’m trying to boot of SD (using MLO on mmcblk0p1) to SD (ext2
partition on mmcblk0p2), but I’m having some troubles with it.

What I did:

  1. Have uboot load the image and boot it:
    set bootargs “console=ttyS2,115200n8 noinitrd root=/dev/mmcblk0p2
    rootdelay=5 rootfstype=ext2”
    set bootcmd ‘mmcinit ; fatload mmc 0:1 0x80000000 uimage.ti ;
    bootm’ ; saveenv

I doubt linux taking your second partition as mmcblk0p2. Can you try booting our ramdisk and then see what is the partition name given by linux for your Second partition on SD card. You can then change the bootargs accordingly.

  1. prepare card according to http://code.google.com/p/beagleboard/wiki/BootingBeagleBoard

  2. reset

The bootlog with the kernel from code.google:

Linux version 2.6.22.1-omap1 (root@fedoraserver) (gcc version 4.2.0
20070413 (prerelease) (CodeSourcery Sourcery G++ Lite 2007q1-21)) #2
Wed Mar 26 16:39:33 IST 2008
CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7), cr=00c5387f
Machine: OMAP3 Beagle board

[…]

Kernel command line: “console=ttyS2,115200n8 noinitrd root=/dev/
mmcblk0p2 rootdelay=5 rootfstype=ext2”

[…]

drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
<3>Root-NFS: No NFS server available, giving up.
Root-NFS: No NFS server available, giving up.
<3>VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device “” or unknown-block(2,0)
VFS: Cannot open root device “” or unknown-block(2,0)
Please append a correct “root=” boot option; here are the available
partitions:
Please append a correct “root=” boot option; here are the available
partitions:
<0>Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
block(2,0)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
block(2,0)

And there are no messages from the mmc subsystem, so it looks like
this kernel doesn’t have SD support.

linux-omap git + dirks patches gives:

Booting image at 80000000 …

Image Name: Angstrom/2.6.24+2.6.25rc7-git039
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1343056 Bytes = 1.3 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum … OK
OK

Starting kernel …

So something is wrong there as well.

This is because the UART is configured to UART1 it should be configured to UART 3

I’m going to try rebuilding 2.6.22 with SD support.

Try my new patches on omap GIT (copied this list as well).

Regards,
Khasim

I have been using /dev/mmcblk0p2 as my root partition without problems
using my own compilation of the kernel. The challenge I've had is in
the formatting of the first (FAT) partition.

I'm surprised SD support wasn't in the kernel image. I started a
message from home, but I was going to upload my kernel first (so I
never sent it).

I also found the use of 2007q1-21 as strange. I've been using
2007q3-53 for a couple of months now.

koen wrote:
...

linux-omap git + dirks patches gives:

...

So something is wrong there as well.

Khasim sent Beagle kernel patches to OMAP list

http://marc.info/?l=linux-omap&m=120834741315244&w=2

I think it would be best to go on with these most up to date patches.

Cheers

Dirk