Boot from SD fails (Command 8, Error 0201)

[samweber]

I've been banging my head against the "Can't boot from SD card" problem for a good while now.  Here's where I'm currently at:

Marvell>> boot
Error! cmd : 8, err : 0201
SD found. Card desciption is:
Manufacturer:       0x03, OEM "SD"
Product name:       "SU02G", revision 8.0
Serial number:      553266355
Manufacturing date: 7/2008
CRC:                0x00, b0 = 0

NAND read: device 0 offset 0x100000, size 0x400000

Reading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-04-04   1:49:44 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2070252 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.............................................................
..................................................................... done, boot
ing the kernel.

----------------------

System is frozen at this point.


Here's my environment (informed by the "SD Card As Root File System" wiki:

baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
run_diag=yes
stdin=serial
stdout=serial
stderr=serial
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x1
00000(root)
mainlineLinux=no
CASset=min
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
MALLOC_len=1
ethprime=egiga0
netbsd_en=no
vxworks_en=no
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/m
tdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x20
00000;
disaMvPnp=no
ethaddr=00:50:43:90:03:30
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
enaAutoRecovery=yes
pcieTune=no
ethact=egiga0
ipaddr=192.168.76.42
serverip=192.168.76.100
bootargs_root=root=b301
bootcmd=mmcinit; setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs
_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
bootdelay=10

---------------

Note:

I downloaded v3.4.19 of u-boot and used bubt to burn the supplied image (u-boot-rd88f6281Sheevaplug_400db_nand.bin).  I did this because the mmcinit command was not present in my (older) version of u-boot and the wiki made it sound as if mmcinit might be the missing piece.  It did, in fact, get me beyond the original kernel panic.

[birdman]

Your bootcmd mentions $(bootargs_console), but that isn't defined.  You do have a console variable defined.  If you've posted this in another thread then I thought you had a "_" missing in the command to set $(bootargs_console), which may explain why you have a console set with what should be in it.

[leadog]

I see a "nand read.e" in the bootcmd. If you want to boot from the MMC don't you need something like "ext2load mmc 0:1 0x800000 /uImage" ?

Have you checked out the installer available here http://plugcomputer.org/plugwiki/index.php/SheevaPlug_Installer ? Those guys seem to have a pretty good setup for loading up a recent kernel and uBoot. They support an install onto MMC.

[samweber]

Error 0202 from command 8 comes from mmcinit.  When I type mmcinit from the u-boot console, it gives the error the first time but not on subsequent attempts.  This is likely a timing issue with the media.

Thanks for the good suggestions.  I'm going to upgrade my kernel and see what happens.

[samweber]

Have you checked out the installer available here http://plugcomputer.org/plugwiki/index.php/SheevaPlug_Installer ? Those guys seem to have a pretty good setup for loading up a recent kernel and uBoot. They support an install onto MMC.

After spending all day yesterday bashing at trying to get the right parameters into u-boot (newest version) for SD card RFS support, all I got for my effort was that I found a bug in the latest u-boot (separate thread).  The kernel panics instead of reading the RFS on the SD card.  So, in desperation, I decided to try the above installer in hopes that the version of the kernel is the problem.  In the end, the windows program falls over when it needs the ftdi drivers and the failure is resilient to all the debugging tips offered.  I am now going start from scratch  and HOPE (only plan left) that the v1.2 set of downloads include components that work together and support the RFS on SD card (I originally configured my plug with v1.1 of the documentation and downloads).

If anyone has a coherent, correct procedure (with version numbers of the components used) for getting the SD card to actually support the RFS, that would be an excellent contribution.  For extra credit, the solution would either not include the FTDI driver mess or would explicate the way one might install and use the recommended drivers.