Part Number:AM3358
Tool/software: Linux
Hi,
My board is basically based on beaglebone black, I need to add support to Lan9514 ww1.microchip.com/.../00002306a.pdf.
Actually the board support kernel boot with tftp and load root file system with nfs, everything works really well with default Ethernet interface cpws.
Now I'm trying to achieve the same result using the evb9514 https://www.microchip.com/Developmenttools/ProductDetails/EVB9514. The first step was to add support in u-boot and after reading some documentations I did and now I can load the kernel with tftp using the external eth, now is the time to allow kernel nfs load the root filesystem. Of course
the la9514 is fully supported in linux4.14, I'm using the ti-processor-sdk-linux-am335x-evm-05.01.00.11. if I run the kernel and the root filesystem from default interface and attach the evb, it is fully supported hub+ethernet.
From u-boot the kernel params are
console=ttyS0,115200n8 root=/dev/nfs nfsroot=${serverip}:/media/ubuntu_ext_ws/tisdk/targetNFS/,nolock,v3,tcp,rsize=4096,wsize=4096 rw ip=dhcp
The most important param is ip=dhcp, from https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt it seems in case of multiple interface device the first one that take a good configuration will be
used as default interface, so in theory if the Ethernet cable is only attached to lan9515 it should works.
So the final step is to add the evb statically in the device tree, here is what I done in am335x-boneblack.dts
&usb { usb1@1 { compatible = "usb424,9514"; reg = <1>; #address-cells = <1>; #size-cells = <0>; ethernet: usbether@1 { compatible = "usb424,ec00"; reg = <1>; }; }; };
Unfortunately the evb is not detect after the kernel is load and the nfs can't run. I'm quite new with the device tree so I suppose the problem is there
Thanks