Cubox i nfs root

[andre77]

Hi, someone can explain me how can i modify the uenv.txt file for boot from an nfs root file system?

[moonman]

http://forum.solid-run.com/kodi-xbmc-pl ... t2190.html

[andre77]

I moonman, thanks for reply, I tested the method read from your link.
I have made an uEnv.txt file like this:
$this->bbcode_second_pass_code('', '
serverip=10.0.0.200
ipaddr=10.0.0.7
ip_dyn=
get_cmd=tftp
zImage=zImage
bootfile=zImage
rootpath=/cuboxroot/boot
storagepath=/cuboxroot
nfsopts=proto=tcp,hard,timeo=70,retrans=3
videoopts=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=16 dmfc=3
netargs=setenv bootargs "ip=dhcp boot=NFS=${serverip}:${rootpath},${nfsopts} \
disk=NFS=${serverip}:${storagepath},${nfsopts} video=${videoopts} quiet"
')

then i have logged into the cubox via serial usb and then power it.
the output from cubox is this:

$this->bbcode_second_pass_code('', '
U-Boot SPL 2013.10-rc4 (Aug 28 2015 - 06:20:08)
Boot Device: SD1
spl: error reading image u-boot.img, err - -1
Load image from RAW...


U-Boot 2013.10-rc4 (Aug 28 2015 - 06:20:08)

CPU: Freescale i.MX6Q rev1.5 at 792 MHz
Reset cause: POR
Board: MX6-CuBox-i
DRAM: 2 GiB
MMC: FSL_SDHC: 0
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Net: FEC [PRIME]
Hit any key to stop autoboot: 0
mmc0 is current device
** File not found /boot.scr **
478 bytes read in 28 ms (16.6 KiB/s)
Importing environment from mmc0 ...
Booting from net ...
Using FEC device
TFTP from server 10.0.0.200; our IP address is 10.0.0.7
Filename 'zImage'.
Load address: 0x10800000
Loading: ##################################################
4.3 MiB/s
done
Bytes transferred = 6240648 (5f3988 hex)
Using FEC device
TFTP from server 10.0.0.200; our IP address is 10.0.0.7
Filename 'imx6q-cubox-i.dtb'.
Load address: 0x18000000
Loading: ###################################################
2.9 MiB/s
done
Bytes transferred = 33907 (8473 hex)
Loaded imx6q-cubox-i.dtb
Booting zImage
Kernel image @ 0x10800000 [ 0x000000 - 0x5f3988 ]
## Flattened Device Tree blob at 18000000
Booting using the fdt blob at 0x18000000
Using Device Tree in place at 18000000, end 1800b472

Starting kernel ...

')

and the boot process stay blocked at the starting kernel line

[moonman]

remove 'quite' to see what's up.