Hello.  I'm working on getting the BBB booting over network, for our CI 
testbench.  I've got it booting the kernel over tftp:

setenv autoload no
setenv bootdelay 2
setenv ipaddr 192.168.0.2
setenv gatewayip 192.168.0.1
setenv netmask 255.255.255.0
setenv serverip 162.x.x.x

tftp 0x80300000 /boot/one/vmlinuz-3.8.13-bone70
tftp 0x81600000 /boot/one/initrd.img-3.8.13-bone70
setenv initrd_size ${filesize}
tftp 0x815f0000 /boot/one/am335x-boneblack.dtb
setenv bootargs 'console=ttyO0,115200n8 root=/dev/nfs 
nfsroot=162.x.x.x:/root/one 
ip=192.168.0.2:162.x.x.x:192.168.0.1:255.255.255.0:one:eth0:off quiet 
init=/lib/systemd/systemd'
bootz 0x80300000 0x81600000:${initrd_size} 0x815f0000

but connecting to the NFS root filesystem times out:

Starting kernel ...


Uncompressing Linux... done, booting the kernel.
[    0.354449] omap2_mbox_probe: platform not supported
[    0.509602] tps65217-bl tps65217-bl: no platform data provided
[    0.572862] bone-capemgr bone_capemgr.9: slot #0: No cape found
[    0.609972] bone-capemgr bone_capemgr.9: slot #1: No cape found
[    0.647079] bone-capemgr bone_capemgr.9: slot #2: No cape found
[    0.684188] bone-capemgr bone_capemgr.9: slot #3: No cape found
[    0.699936] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN 
conflict P8.45 (#5:BB-BONELT-HDMI)
[    0.709504] bone-capemgr bone_capemgr.9: slot #6: Failed verification
[    0.716242] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB
-BONELT-HDMIN:00A0 (prio 2)
[    0.732702] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' 
failed
[    0.795795] pinctrl-single 44e10800.pinmux: pin 44e10854 already 
requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[    0.807478] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -
22
[    0.814753] pinctrl-single 44e10800.pinmux: could not request pin 21 on 
device pinctrl-single
[    1.034056] libphy: PHY 4a101000.mdio:01 not found
[    1.039123] net eth0: phy 4a101000.mdio:01 not found on slave 1
Loading, please wait...
IP-Config: eth0 hardware address d0:5f:b8:fa:42:dd mtu 1500
IP-Config: eth0 guessed broadcast address 192.168.0.255
IP-Config: eth0 complete:
 address: 192.168.0.2      broadcast: 192.168.0.255    netmask: 255.255.
255.0
 gateway: 192.168.0.1      dns0     : 0.0.0.0          dns1   : 0.0.0.0
 host   : one
 rootserver: 162.x.x.x rootpath:
 filename  :
connect: Connection timed out
connect: Connection timed out
connect: Connection timed out

It's timing out, but under DHCP it doesn't even get that far.  It doesn't 
list the "rootpath" so I wonder if that got passed to the kernel?

Here is the exports file on the server:

/tftpboot/root/one 162.x.x.x/28(rw,nohide,insecure,no_subtree_check,async,
no_root_squash)

I can mount the nfs share on another device:

root@beaglebone:/# mount 162.x.x.x:/ /mnt
root@beaglebone:/# cd /mnt/
root@beaglebone:/mnt# ls
tftpboot


I'm not sure what to try next.  Any ideas?

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to