imx28 evk board - NFS mount and boot failure

sureshbabu1z · ‎07-09-2012

Hello All,

I am facing problem while NFS mout and boot from TFTP Server and client.

Could you please help he I am unable to find problem where it is occurring.

1) I have set it up tftpboot and tftp service also i added.

-> tftp loading image.

2) NFS

server(Host Linux ip) - 192.168.1.34

etc/exports -

/tmp/fs *(rw,sync,subtree_check)
/tools/rootfs *(rw,sync,subtree_check)

3) for NFS mounting

sudo mount -t nfs 192.168.1.34:/tools/rootfs /tools/rootfs -->?

the above mounting step is right or wrong.

otherwise please help me.

4) current printenv

MX28 U-Boot > printenv
bootcmd=run bootcmd_net
bootdelay=3
baudrate=115200
netmask=255.255.255.0
loadaddr=0x42000000
bootcmd_net=run bootargs_nfs; dhcp; bootm
bootargs_mmc=setenv bootargs ${bootargs} root=/dev/mmcblk0p3 rw rootwait ip=dhc}
bootcmd_mmc=run bootargs_mmc; mmc read 0 ${loadaddr} 100 3000; bootm
ethact=FEC0
nfsroot=/tools/rootfs
bootargs_nfs=setenv bootargs ${bootargs} root=/dev/nfs ip=dhcp nfsroot=${server�
gatewayip=192.168.1.1
bootargs=console=ttyAM0,115200n8 root=/dev/nfs ip=dhcp nfsroot=192.168.1.101:/h�
bootfile=uImage
ethaddr=00:04:9F:01:D2:E4
serverip=192.168.1.34
ipaddr=192.168.1.31
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 2009.08 (Jul 05 2012 - 16:57:23)

Environment size: 863/130044 bytes
MX28 U-Boot >

5)

This is the message i am getting

U-Boot 2009.08 (Jul 05 2012 - 16:57:23)

Freescale i.MX28 family
CPU:   454 MHz
BUS:   151 MHz
EMI:   205 MHz
GPMI:   24 MHz
DRAM: 128 MB
MMC:   IMX_SSP_MMC: 0, IMX_SSP_MMC: 1
In:    serial
Out:   serial
Err:   serial
Net:   got MAC address from IIM: 00:04:9f:01:d2:e4
FEC0
Hit any key to stop autoboot: 0
** Too many args (max. 16) **
BOOTP broadcast 1
FEC: Link is down 7809
BOOTP broadcast 2
BOOTP broadcast 3
DHCP client bound to address 192.168.1.22
Using FEC0 device
TFTP from server 192.168.1.34; our IP address is 192.168.1.22
Filename 'uImage'.
Load address: 0x42000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##############################################
done
Bytes transferred = 2562288 (2718f0 hex)
## Booting kernel from Legacy Image at 42000000 ...
   Image Name:   Linux-2.6.35.3-571-gcca29a0
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2562224 Bytes = 2.4 MB
   Load Address: 40008000
   Entry Point: 40008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.35.3-571-gcca29a0 (ivcbar049adm@ubuntu) (gcc version 4.4.4 (42
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Freescale MX28EVK board
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
Kernel command line: console=ttyAM0,115200n8 root=/dev/nfs ip=dhcp nfsroot=192.5
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 124316k/124316k available, 6756k reserved, 0K highmem
Virtual kernel memory layout:
    vector : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xfde00000 - 0xffe00000   ( 32 MB)
    vmalloc : 0xc8800000 - 0xf0000000   ( 632 MB)
    lowmem : 0xc0000000 - 0xc8000000   ( 128 MB)
    modules : 0xbf000000 - 0xc0000000   ( 16 MB)
      .init : 0xc0008000 - 0xc0030000   ( 160 kB)
      .text : 0xc0030000 - 0xc04f7000   (4892 kB)
      .data : 0xc04f8000 - 0xc0535960   ( 247 kB)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
        RCU-based detection of stalled CPUs is disabled.
        Verbose stalled-CPUs detection is disabled.
NR_IRQS:288
Console: colour dummy device 80x30
console [ttyAM0] enabled
Calibrating delay loop... 226.09 BogoMIPS (lpj=1130496)
pid_max: default: 32768 minimum: 301
Security Framework initialized
SELinux: Initializing.
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
regulator: vddd: 800 <--> 1575 mV at 1500 mV fast normal
regulator: vdddbo: 800 <--> 1575 mV fast normal
regulator: vdda: 1500 <--> 2275 mV at 1800 mV fast normal
vddio = 3380000, val=10
regulator: vddio: 2880 <--> 3680 mV at 3380 mV fast normal
regulator: overall_current: fast normal
regulator: vbus5v:
regulator: mxs-duart-1: fast normal
regulator: mxs-bl-1: fast normal
regulator: mxs-i2c-1: fast normal
regulator: mmc_ssp-1: fast normal
regulator: mmc_ssp-2: fast normal
regulator: charger-1: fast normal
regulator: power-test-1: fast normal
regulator: cpufreq-1: fast normal
i.MX IRAM pool: 124 KB@0xc8820000
Initializing GPMI pins
usb DR wakeup device is registered
IMX usb wakeup probe
audit: cannot initialize inotify handle
bio: create slab <bio-0> at 0
SCSI subsystem initialized
Freescale USB OTG Driver loaded, $Revision: 1.55 $
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource mxs clock source
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Bus freq driver module loaded
IMX usb wakeup probe
usb h1 wakeup device is registered
mxs_cpu_init: cpufreq init finished
audit: initializing netlink socket (disabled)
type=2000 audit(0.610:1): initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
msgmni has been set to 242
alg: No test for stdrng (krng)
cryptodev: driver loaded.
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Console: switching to colour frame buffer device 100x30
mxs-duart.0: ttyAM0 at MMIO 0x80074000 (irq = 47) is a DebugUART
mxs-auart.0: ttySP0 at MMIO 0x8006a000 (irq = 112) is a mxs-auart.0
Found APPUART 3.1.0
mxs-auart.1: ttySP1 at MMIO 0x8006c000 (irq = 113) is a mxs-auart.1
Found APPUART 3.1.0
mxs-auart.2: ttySP2 at MMIO 0x8006e000 (irq = 114) is a mxs-auart.2
Found APPUART 3.1.0
mxs-auart.3: ttySP3 at MMIO 0x80070000 (irq = 115) is a mxs-auart.3
Found APPUART 3.1.0
brd: module loaded
loop: module loaded
i.MX GPMI NFC
NFC: Version 1, 8-chip GPMI and BCH
Boot ROM: Version 1, Single-chip boot area, block mark swapping supported
Scanning for NAND Flash chips...
No NAND device found.
gpmi-nfc gpmi-nfc.0: Chip scan failed
mxs-spi mxs-spi.0: Max possible speed 24000 = 24000000/2 kHz
mxs-spi mxs-spi.0: at 0x80014000 mapped to 0xF0014000, irq=84, bus 1, DMA ver_m4
FEC Ethernet Driver
fec_enet_mii_bus: probed
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
fsl-ehci fsl-ehci: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci: irq 93, io base 0x80080000
fsl-ehci fsl-ehci: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 2
fsl-ehci fsl-ehci.0: irq 92, io base 0x80090000
fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
ARC USBOTG Device Controller driver (1 August 2005)
mice: PS/2 mouse device common for all mice
input: mxs-kbd as /devices/platform/mxs-kbd.0/input/input0
input: MXS touchscreen as /devices/virtual/input/input1
MXS RTC driver v1.0 hardware v2.3.0
mxs-rtc mxs-rtc.0: rtc core: registered mxs-rtc as rtc0
IR NEC protocol handler initialized
IR RC5(x) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
Linux video capture interface: v2.00
mxs-pxp mxs-pxp.0: initialized
mxs watchdog: initialized, heartbeat 19 sec
mxs-mmc: MXS SSP Controller MMC Interface driver
mxs-mmc mxs-mmc.0: mmc0: MXS SSP MMC DMAIRQ 82 ERRIRQ 96
dcp dcp.0: DCP crypto enabled.!
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
sgtl5000-i2c 0-000a: SGTL5000 revision 17
mxs-spdif mxs-spdif.0: MXS SPDIF Audio Transmitter
No device for codec mxs spdif
No device for DAI mxs spdif
No device for DAI mxs-saif
No device for DAI mxs-spdif
asoc: SGTL5000 <-> mxs-saif mapping ok
mmc0: new high speed SDHC card at address d555
mmcblk0: mmc0:d555 SU04G 3.79 GiB
mmcblk0: p1 p2 p3
Failed to add route LINE_OUT->Ext Spk
asoc: mxs spdif <-> mxs-spdif mapping ok
ALSA device list:
#0: mxs-evk (SGTL5000)
#1: mxs-evk (mxs spdif)
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
mxs-rtc mxs-rtc.0: setting system clock to 1970-01-01 00:59:04 UTC (3544)
eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=0:00, irq=-1)
eth1: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1)
Sending DHCP requests .
PHY: 0:00 - Link is Up - 100/Full
.., OK
IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.1.31
IP-Config: Complete:
     device=eth0, addr=192.168.1.31, mask=255.255.255.0, gw=192.168.1.1,
     host=192.168.1.31, domain=ivcbar.local, nis-domain=(none),
     bootserver=0.0.0.0, rootserver=192.168.1.34, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.34
Looking up port of RPC 100005/1 on 192.168.1.34
VFS: Mounted root (nfs filesystem) on device 0:14.
Freeing init memory: 160K
init started: BusyBox v1.15.0 ()
starting pid 1113, tty '': '/etc/rc.d/rcS'
Mounting /proc and /sys
Starting the hotplug events dispatcher udevd
Synthesizing initial hotplug events
Setting the hostname to freescale
Mounting filesystems
Booted NFS, not relocating: /tmp /var
ln: /etc/mtab: Permission denied
mount: mounting usbfs on /proc/bus/usb failed: No such file or directory
Running sysctl
Setting up networking on loopback device:
rm: cannot remove '/etc/resolv.conf': Permission denied
Setting up networking on eth0:
nfs: server 192.168.1.34 not responding, still trying

I have one IP address(192.168.1.31) but some it is showing some other ip address(192.168.1.22).

Colin_MTData · ‎07-16-2012

Hello Suresh, You're getting further than I can with TFTP & NFS but I can help a little. 1) I'm not sure what this is. 2) Looks OK to me (but mine isn't working at all yet). Mine is more restrictive: /tools/rootfs 192.168.1.0/255.255.255.0(rw,no_root_squash,no_subtree_check,sync) NOTE: I think the "no_root_squash" will be important for you as root on the target will want root access to the rootfs tree (Check with someone who knows more about NFS) 3) This isn't needed (and if it is on your host server then it is wrong) It's the target machine that will eventually mount the host root directory as it's own root, not on /tools/rootfs 4)Notice that when the command bootargs_nfs is run ("bootargs_nfs=setenv bootargs ${bootargs} root=/de....") it will effectively append to bootargs each time. bootargs is supposed to be just "ttyAM0,115200n8" but your environment has been saved with bootargs as it is after the append and so when you boot it tries to add even more on to the end and exceeds 16 args. Set bootargs back to the correct string and saveenv again. 5)I'm envious I can't get this bit to work at all. My FEC0 isn't up. Your server (linux host) is 192.168.1.34. Some dhcp server (probably 192.168.1.34) is returning the 192.168.1.22 to the target when u-boot uses bootp/tftp to request an address. If you want to have a fixed address for your target I think you need to change the "ip=dhcp" to "ip=${ipaddr}" in the bootargs_nfs env. variable. (I'm not 100% sure because I can't get my ether net port up). After all that it still doesn't help you with your main problem of "nfs: server 192.168.1.34 not responding, still trying". I assume "/tools/rootfs" is where you have put the rootfs of the system. Colin

Colin_MTData · ‎07-16-2012

Hello Suresh, You're getting further than I can with TFTP & NFS but I can help a little. 1) I'm not sure what this is. 2) Look OK to me (but mine isn't working at all) 3) This isn't needed (and if it is on your host server then it is wrong) It's the target machine that will eventually mount the host root directory as it's own root, not on /tools/rootfs 4)Notice that when the command bootargs_nfs is run ("bootargs_nfs=setenv bootargs ${bootargs} root=/de....") it will effectively append to bootargs each time. bootargs is supposed to be just "ttyAM0,115200n8" but your environment has been saved with bootargs as it is after the append and so when you boot it tries to add even more on to the end and exceeds 16 args. Set bootargs back to the correct string and saveenv again. 5)I'm envious I can't get this bit to work at all. My FEC0 isn't up. Your server (linux host) is 192.168.1.34. Some dhcp server (probably 192.168.1.34) is returning the 192.168.1.22 to the target when u-boot uses bootp/tftp to request an address. If you want to have a fixed address for your target I think you need to change the "ip=dhcp" to "ip=${ipaddr}" in the bootargs_nfs env. variable. (I'm not 100% sure because I can't get my ether net port up). After all that it still doesn't help you with your main problem of "nfs: server 192.168.1.34 not responding, still trying". I assume "/tools/rootfs" is where you have put the rootfs of the system. Colin