I have the ConnectCore i.MX6UL Starter Kit and I built the core-image-base image using Yocto and the DEY layer version 2.4. I have found a few differences between the behavior of this image when booted via NFS vs booting from NAND. To boot via NFS, I use the u-boot command "dboot linux tftp".
The first problem I see when booting via NFS is that the firmware for the wlan does not get loaded. The qualcomm.sh script in /etc/udev/scripts is supposed to create the appropriate links. This script runs, but the links are not created. I can workaround this issue by manually creating the links and re-booting.
Once the first problem is resolved, the next problem is that the wlan0 interface is not being managed by NetworkManager as I would expect. I compared all of the configuration files for NetworkManager, ifupdown, hostapd, etc... and found no differences between these files on the NFS filesystem and the UBI filesystem on NAND. I have not been able to find out why this happens or find a workaround. Here is the output of nmcli dev:
When boot via NFS
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected eth0
can0 can unmanaged --
sit0 iptunnel unmanaged --
lo loopback unmanaged --
p2p0 wifi unmanaged --
wlan0 wifi unmanaged --
wlan1 wifi unmanaged --
When boot via NAND
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected eth0
wlan0 wifi disconnected --
can0 can unmanaged --
sit0 iptunnel unmanaged --
lo loopback unmanaged --
wlan1 wifi unmanaged --
The main difference between these two runtime configurations is that eth0 is being used to mount the root file system. I suppose that somehow confuses NetworkManager. Does anyone have experience booting to NFS with this starter kit?
Thanks.
-John G.