imx8Mmini ethernet with multimedia yocto build

[davidvescovi]

when I do a yocto imx8Mmini evk build with a target image "fsl-image-qt5" or "fsl-image-gui" it includes ethernet support and it works fine. If I do the same build but target "fsl-image-multimedia" it builds the image correctly and everything else runs fine but there is no ethernet connectivity. I searched through the packages but can't find what includes the ethernet support. I see the qt5 and gui builds include some "test" packages and it looks like they are the only differences. How can I get ethernet support in a "multimedia" only build?

This is a headless target and I would like to reduce the image foot print.

[davidvescovi]

I do see a difference in he documentation between imx-yocto-L4.14.98_2.0.0_ga and imx-yocto-L4.19.35_1.1.0.
The 4.19.35 docs show an additional "imx-image-multimedia" whereas the 4.14.98 does not show this one. I suspect building "fsl-image-multimedia" under the L4.14.98_2.0.0_ga BSP may be building the "community" image that may not have full support for the iMX8Mmini.???

[kunalkotecha1]

Hi davidvescovi,

Are you getting an ethernet device when you give the "ifconfig -a" command? If no, can you please check the device tree file used has enabled the ethernet device or not. If you are getting the ethernet device, then you need to up the interface. Have you tried with that? Are you facing any issue in that?

Regards,

Kunal

[davidvescovi]

please read the previous comments ... I already posted the ifconfig.
here it is again:

when I do an ifconfig on multimedia build I get:

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:80 errors:0 dropped:0 overruns:0 frame:0
TX packets:80 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6080 (5.9 KiB) TX bytes:6080 (5.9 KiB)

[davidvescovi]

and ifconfig -a yield's:

root@imx8mmevk:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:04:9F:05:F9:47
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:80 errors:0 dropped:0 overruns:0 frame:0
TX packets:80 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6080 (5.9 KiB) TX bytes:6080 (5.9 KiB)

p2p0 Link encap:Ethernet HWaddr CE:C0:79:3A:67:54
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan0 Link encap:Ethernet HWaddr CC:C0:79:B6:67:54
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Just not getting an IP address??

[kunalkotecha1]

Hi davidvescovi ,

This is what I was looking for. You just need to up the ethernet interface and assign the IP address to it. Perform below steps on consle:

ifconfig eth0 up

udhcpc -i eth0

Regards,

Kunal

[davidvescovi]

again this does not address my original question.
My question is why is there a difference in the builds between fsl-image-gui and fsl-image-multimedia?
I realize I could do console commands to get it to work AFTER build at run time but I want to know where in the yocto image build procedure (recipe, logon script, bootloader etc.) is the area I need to change to get a fsl-image-multimedia build to act the same as a fsl-image-gui? i.e. connect, get IP address etc.  I need to know what is the change at build time?  

[davidvescovi]

and yes I realize I could just tack on these two command to a power up script but again that does NOT answer my question. 

[davidvescovi]

could this be because the fsl-image-multimedia uses a different network manager (connman,systemd-networkd,NetworkManager) than fsl-image-qt5? If which one uses what?

[davidvescovi]

board looks like SCH-31407 REV C1

[davidvescovi]

Yes, ethernet is working fine with "fsl-image-gui" and "fsl-image-qt5 builds" as I previously stated.
Here are the EXACT steps to reproduce (directly from the imx-yocto-L4.14.98_2.0.0_ga docs):
1. Install dependences and repo
2.  mkdir imx-yocto-bsp

3. cd imx-yocto-bsp

4. repo init -u https://source.codeaurora.org/external/imx/imx-manifest -b imx-linux-sumo -m imx-4.14.98-2.0.0_ga.xml

5. repo sync

6.  DISTRO=fsl-imx-xwayland MACHINE=imx8mmevk source fsl-setup-release.sh -b build-xwayland

7. bitbake fsl-image-multimedia

8. burn SD card and boot

No ethernet connectivity.

Same procedure but use "bitabake fsl-image-qt5", burn SD card and boot ethernet connectivity works.

[davidvescovi]

could it be something in the bootloader build?

[davidvescovi]

maybe not bootloader related as I am using the same bootload between gui and multimedia build and it makes no difference ... still does not work

[igorpadykov]

one can try to recheck build steps

https://community.nxp.com/docs/DOC-94849 

Best regards
igor

[davidvescovi]

May you should try it on the iMX8m Mini evk. I rechecked it several times. This version does NOT support ethernet when building fsl-image-multimedia. I have been using this version for almost a year now building several times a week.

[kunalkotecha1]

Hi davidvescovi ,

Sorry for the late reply. I was into something else.

Strange to know that you are still facing an issue. I have already verified in i.MX8MMini EVK. I have verified that GStreamer packages are installed as well as ethernet is enabled. Is ethernet working in your EVK? Which revision of EVK you are using?

Regards,

Kunal

[igorpadykov]

one can try L4.14.98_2.3.1 GA  28 February 2020 consolidated release 

Linux 4.14.98_2.3.1-patch Documentation

[davidvescovi]

when I do an ifconfig on multimedia build I get:

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:80 errors:0 dropped:0 overruns:0 frame:0
TX packets:80 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6080 (5.9 KiB) TX bytes:6080 (5.9 KiB)

[davidvescovi]

 I am using imx-yocto-L4.14.98_2.0.0_ga and following the directions as described in the i.MX Yocto project user's guide for that exact version.

using fsl-imx-xwayland distro and imx8mmevk machine.

DISTRO=fsl-imx-xwayland MACHINE=imx8mmevk source fsl-setup-release.sh -b build-xwayland

 Tried several times:

"bitbake fsl-image-gui" works with ethernet  "bitbake fsl-image-multimedia" builds but no ethernet.

[davidvescovi]

Please explain what needs to be modified to the add iMX8Mmini fsl-image-multimedia build to get ethernet support.

[kunalkotecha1]

Hi davidvescovi,

As suggested by igorpadykov, you can follow steps from user guide. I have verified the i.MX8MMini EVK with fsl-imx-wayland Distro and "bitbake fsl-image-multimedia" image. I am able to use the ethernet interface with multimedia packages as well. Let us know if you still face any issues after following the yocto user guide.  I have verified in L4.14.98 version.

Regards,

Kunal