TFTP&NFS imx6qsabrelite boot error

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

TFTP&NFS imx6qsabrelite boot error

1,077 Views
zhangmeiyu
Contributor I

hi ,

I  am trying to boot ubuntu14.04 from NFS on imx6qsabrelite, but problems occourred.

the rootfs is already in the /home/nfs

The follows are my uboot Environment variables:

U-Boot > pri
baudrate=115200
board=sabrelite
boot_fdt=try
bootargs=console=ttymxc1,115200 root=/dev/nfs ip=192.168.0.140:192.168.0.136:192.168.0.1:255.255.255.0::eth0:on nfsroot=192.168.0.136:/home/nfs,v3,tcp
bootcmd=tftp 0x12000000 zImage_nt;tftp 0x18000000 imx6q-nitrogen6x.dtb;bootz 0x12000000 - 0x18000000
bootdelay=1
bootscript=echo Running bootscript from mmc ...; source
console=ttymxc1
cpu=6Q
ethact=FEC
ethaddr=00:19:b8:03:a9:cc
ethprime=FEC
fdt_addr=0x18000000
fdt_file=imx6q-nitrogen6x.dtb
fdt_high=0xffffffff
fileaddr=18000000
filesize=caa0
gatewayip=192.168.0.1
get_cmd=tftp
image=zImage_nt
initrd_high=0xffffffff
ip_dyn=no
ipaddr=192.168.0.140
loadaddr=0x12000000
loadbootscript=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${script};
loadfdt=fatload mmc ${mmcdev}:${mmcpart} ${fdt_addr} ${fdt_file}
loaduimage=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${uimage}
mmcargs=setenv bootargs console=${console},${baudrate} root=${mmcroot}
mmcboot=echo Booting from mmc ...; run mmcargs; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if run loadfdt; then bootm ${loadaddr} - ${fdt_addr}; else if test ${boot_fdt} = try; then bootm; else echo WARN: Cannot load the DT; fi; fi; else bootm; fi;
mmcdev=0
mmcpart=1
mmcroot=/dev/mmcblk0p2 rootwait rw
netargs=setenv bootargs console=ttymxc1,115200 root=/dev/nfs ip=192.168.0.140:192.168.0.136:192.168.0.1:255.255.255.0::eth7:on nfsroot=192.168.0.136:/home/nfs,v3,tcp
netboot=echo Booting from net ...; run netargs; if test ${ip_dyn} = yes; then setenv get_cmd dhcp; else setenv get_cmd tftp; fi; ${get_cmd} ${uimage}; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if ${get_cmd} ${fdt_addr} ${fdt_file}; then bootm ${loadaddr} - ${fdt_addr}; else if test ${boot_fdt} = try; then bootm; else echo WARN: Cannot load the DT; fi; fi; else bootm; fi;
netmask=255.255.255.0
nfsroot=/home/nfs
script=boot.scr
serverip=192.168.0.136
uimage=uImage

The last part of the print information is:

mmcblk2: mmc2:e624 SC16G 14.8 GiB
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 3 ports detected
mmcblk2: p1 p2
mmc3: host does not support reading read-only switch. assuming write-enable.
mmc3: new SDHC card at address 0001
mmcblk3: mmc3:0001 00000 3.72 GiB
mmcblk3: p1 p2
mxc_vdoa 21e4000.vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
mxc_asrc 2034000.asrc: mxc_asrc registered
mxc_vpu 2040000.vpu: VPU initialized
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
sgtl5000 0-000a: sgtl5000 revision 0x11
init_gpio_data:-2
init_gpio_data:-2
sgtl5000 0-000a: Failed to get supply 'VDDD': -19
0-000a: 1200 mV normal
sgtl5000 0-000a: Using internal LDO instead of VDDD
imx-sgtl5000 sound.25: sgtl5000 <-> 2028000.ssi mapping ok
imx-audio-hdmi sound-hdmi.26: hdmi-hifi <-> hdmi_audio.17 mapping ok
NET: Registered protocol family 26
TCP: cubic registered
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: BNEP socket layer initialized
8021q: 802.1Q VLAN Support v1.8
rfkill_gpio bt_rfkill.39: bt_rfkill device registered.
Key type dns_resolver registered
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
Registering SWP/SWPB emulation handler
wlan-en: disabling
usb_otg_vbus: disabling
regulator-dummy: disabling
snvs_rtc 20cc034.snvs-rtc-lp: setting system clock to 1970-01-01 00:00:01 UTC (1)
ALSA device list:
#0: imx6q-nitrogen6x-sgtl5000
#1: imx-hdmi-soc
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
1f00 768 mtdblock0 (driver?)
1f01 8 mtdblock1 (driver?)
1f02 1272 mtdblock2 (driver?)
b300 15558144 mmcblk2 driver: mmcblk
b301 131072 mmcblk2p1 ebee47f2-01
b302 15426048 mmcblk2p2 ebee47f2-02
b308 3903488 mmcblk3 driver: mmcblk
b309 131072 mmcblk3p1 07bfd0f5-01
b30a 3771392 mmcblk3p2 07bfd0f5-02
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

Is my environment variable set incorrectly?especially the red part,or the rootfs i used is broken ? any suggestion ?Thanks.

zhang

Labels (2)
0 Kudos
1 Reply

654 Views
Carlos_Musich
NXP Employee
NXP Employee

Hi,

we do not support Ubuntu but you can refer to the following documents for help:

Yocto NFS &amp; TFTP boot 

i.MX6 NFS booting with Ubuntu 12.04.02 Precise 

Set up NFS Environment and Boot up Board 

Setting up a Debian server for network booting the i.MX6 sabre sd platform 


Regards,
Carlos
NXP Technical Support
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos