topic Re: SABRE Board: Not able to mount root filesystem in i.MX Processors

SABRE Board: Not able to mount root filesystem

Swamy — Thu, 22 Sep 2011 12:48:48 GMT

Hello,

I am trying to boot the SABRE Tablet board with Linux image taken from the freescale website. I am getting following error where it is pointing for unable to mount the rootfs filesytem. Please suggest.

Printenv output:

MX53-SMD U-Boot > printenvbootdelay=3baudrate=115200netdev=eth0ethprime=FEC0uboot=u-boot.binkernel=uImagenfsroot=/opt/eldk/armbootargs_nfs=setenv bootargs ${bootargs} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcpbootcmd_net=run bootargs_base bootargs_nfs; tftpboot ${loadaddr} ${kernel}; bootmethact=FEC0bootcmd_mmc=run bootargs_basebootargs_mmc;mmc read 0 ${loadaddr} 0x800 0x1800;bootmbootcmd=run bootcmd_mmcloadaddr=0x70800000bootargs_mmc=set bootargs root=/dev/mmcblk0p1 rw rootwait rwvideo=mxcdi1fb:RGB666,XGA di1_primaryldb=di1bootargs_base=setenv bootargs console=ttymxc0,115200stdin=serialstdout=serialstderr=serial
Environment size: 629/131068 bytesMX53-SMD U-Boot >

Regards,

Swamy

Root-NFS: No NFS server available, giving up.VFS: Unable to mount root fs via NFS, trying floppy.List of all partitions:1f00 256 mtdblock0 (driver?)1f01 3840 mtdblock1 (driver?)0800 31266648 sda driver: sdb300 3872256 mmcblk0 driver: mmcblk b301 3868160 mmcblk0p1No filesystem could mount root, tried: jffs2Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)[<80039524>] (unwind_backtrace+0x0/0xf0) from [<8040d0d0>] (panic+0x6c/0xe0)[<8040d0d0>] (panic+0x6c/0xe0) from [<80008ddc>] (mount_block_root+0x1cc/0x20c)[<80008ddc>] (mount_block_root+0x1cc/0x20c) from [<80009028>] (prepare_namespace+0x11c/0x174)[<80009028>] (prepare_namespace+0x11c/0x174) from [<800084a0>] (kernel_init+0x120/0x168)[<800084a0>] (kernel_init+0x120/0x168) from [<800359e0>] (kernel_thread_exit+0x0/0x8)mmc1: Timeout waiting for hardware interrupt.mxsdhci:

============== REGISTER DUMP ==============mxsdhci: Sys addr: 0x00000000 | Version: 0x00001201mxsdhci: Blk size: 0x00000000 | Blk cnt: 0x00000001mxsdhci: Argument: 0x00018000 | Trn mode: 0x05020000mxsdhci: Present: 0xff880008 | Host ctl: 0x00000121mxsdhci: Clock: 0x000010ffmxsdhci: Int stat: 0x00000000mxsdhci: Int enab: 0x117f010f | Sig enab: 0x117f000fmxsdhci: Caps: 0x07f30000mxsdhci: ===========================================

Re: SABRE Board: Not able to mount root filesystem

amanda_mcgregor — Wed, 12 Oct 2011 20:29:55 GMT

Hi Swamy,

Were you able to find a solution, or is this still an open issue for you?

Regards,

Amanda

Re: SABRE Board: Not able to mount root filesystem

Swamy — Fri, 09 Dec 2011 13:23:03 GMT

It is giving me following log....

IT stops me there....It does not mount root. Please help

My Printenv

MX53-SMD U-Boot > printenv
bootdelay=3
baudrate=115200
loadaddr=0x70800000
netdev=eth0
ethprime=FEC0
uboot=u-boot.bin
kernel=uImage
nfsroot=/opt/eldk/arm
ethact=FEC0
bootargs=console=ttymxc0,115200root=/dev/mmcblk0p1 rootwait rwvideo=mxcdi1fb:RGB666,VGA di1_primaryldb=di1 ip=none
bootargs_nfs=setenv bootargs ${bootargs} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp
bootcmd_net=run bootargs_base bootargs_nfs; tftpboot ${loadaddr} ${kernel};
bootcmd_mmc=run bootargs_base bootargs_mmc; mmc read 0 ${loadaddr} 0x800 0x1800;
bootcmd=run bootcmd_mmc
bootargs_mmc=setenv bootargs ${bootargs}root=/dev/mmcblk0p1 rootwait rwvideo=mxcdi1fb:RGB666,VGA di1_primaryldb=di1 ip=none
bootargs_base=setenv bootargs console=ttymxc0,115200
stdin=serial
stdout=serial
stderr=serial

Environment size: 754/131068 bytes
MX53-SMD U-Boot >

regulator_init_complete: incomplete constraints, leaving DA9052_LDO1 on
mxc_rtc mxc_rtc.0: setting system clock to 1970-01-01 00:25:28 UTC (1528)
Waiting for root device ...
mmc1: queuing unknown CIS tuple 0x80 (1 bytes)
mmc1: queuing unknown CIS tuple 0x81 (1 bytes)
mmc1: queuing unknown CIS tuple 0x82 (1 bytes)
mmc1: new high speed SDIO card at address 0001
AR6000: Unsupported configuration opcode: 3
AR6000: Unsupported configuration opcode: 3
HIF Interrupt processing is SYNC ONLY
AR6000: Unsupported configuration opcode: 7
AR6000: Unsupported configuration opcode: 5
In aggr_init..
going out of aggr_init..status OK
Unknown firmware revision: 805307778
ar6000_avail: ar6000_sysfs_bmi_get_config failed
mmc2: new high speed MMC card at address 0001
mmcblk0: mmc2:0001 SEM08G 7.39 GiB
mmcblk0: p1 p2 p3 < p5 p6 > p4