Hello, I am trying to setup a tftpboot to boot the kernel and an nfsroot to use a rootfs via nfs. I am using the beagleboard kernel and uboot:
BeagleV-Ahead / beaglev-ahead-linux · GitLab
BeagleV-Ahead / beaglev-ahead-u-boot · GitLab
What is working:
When I boot the linux and then after complete boot setup an IP, I can ping the BeagleV-Ahead from my PC and vice-versa.
Regarding booting the kernel via tftpboot from uboot:
When I get into the uboot prompt, set an ipaddr, netmask and ethaddr and then try to ping the BeagleV-Ahead from PC and vice versa, it does NOT work. I also don’t see any ICMP message from the BeagleV-Ahead towards the PC in wireshark. I hence assume that either I misconfigured something or that the uboot does not yet correctly feature networking capabilities? Does anyone know the status here or/and can help?
Regarding including the rootfs via nfs:
When I boot the kernel, I use the following bootcommands:
fatload mmc 1:1 ${kernel_addr_r} Image; fatload mmc 1:1 ${fdt_addr_r} light-beagle.dtb; setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath},proto=tcp,nfsvers=3 rootfstype=ext4 rootwait console=ttyS0,115200 earlycon clk_ignore_unused net.ifnames=0; booti ${kernel_addr_r} - ${fdt_addr_r};
Thereby serverip and rootpath and ipaddr are set beforhand. However again I don’t see any traffic from the BeagleV-Ahead towards my PC in wireshark. The necessary ethernet driver (dwmac-light) is activated in the kernel config and also if I boot the rootfs via SD card, then I can ping my PC from the board and vice versa. Does anyone has a hint, what I might be doing wrong? Are there additional kernel-configs which I might have to activate to be able to use nfs?
Best regards,
Kilian