[meta-intel] g_ether functionality for Intel E3845 CPU (valley-island, bay-trail)

[Tan, Jui Nee]

Hi,
Please make sure USB OTG Support is enabled (PCI Mode) in BIOS.

BIOS Setup:
Device Manager / System Setup / South Cluster Configuration / USB Configuration / USB OTG Support  [PCI Mode]

Thanks,
Juinee

From: Henrik Haugaard Jensen [mailto:hhj at trackman.com]
Sent: Monday, December 3, 2018 8:52 PM
To: Tan, Jui Nee <jui.nee.tan at intel.com>
Subject: RE: [meta-intel] g_ether functionality for Intel E3845 CPU (valley-island, bay-trail)

Hi Juinee,
I tried building exactly as specified ( I did also add IMAGE_INSTALL_append = " kernel-module-g-ether kernel-module-dwc3-pci " to local.conf).
But g_ether module won’t load:

:
dwc3-pci 0000:00:16.0: enabling device (0000 -> 0002)
dwc3 dwc3.1.auto: changing max_speed on rev 5533210a
random: crng init done
random: 3 urandom warning(s) missed due to ratelimiting
EXT4-fs (sda2): re-mounted. Opts: data=ordered
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

Poky (Yocto Project Reference Distro) 2.5.1 intel-corei7-64 /dev/ttyS0

intel-corei7-64 login: root
root at intel-corei7-64:~# lsmod
    Not tainted
dwc3_pci 16384 0 - Live 0xffffffffc009e000
root at intel-corei7-64:~# modprobe g_ether
g_ether dwc3.1.auto: failed to start g_ether: -2
g_ether dwc3.1.auto: failed to start g_ether: -2
modprobe: can't load module g_ether (kernel/drivers/usb/gadget/legacy/g_ether.ko): unknown symbol in module, or unknown parameter
:

There is no additional info in /var/log/messages about the unknown symbol/parameter.
As mention everythings worked with “Jethro @ kernel ver. 3.10” so I do not think it is hardware.

Any suggestions?

BR
Henrik

From: Tan, Jui Nee <jui.nee.tan at intel.com<mailto:jui.nee.tan at intel.com>>
Sent: Friday, 23 November 2018 03.10
To: Henrik Haugaard Jensen <hhj at trackman.com<mailto:hhj at trackman.com>>; meta-intel at yoctoproject.org<mailto:meta-intel at yoctoproject.org>
Subject: RE: [meta-intel] g_ether functionality for Intel E3845 CPU (valley-island, bay-trail)

Hi,

Please follow Sumo build procedure that built against Poky (Yocto Project Reference Distro) 2.5.1 meta-intel 9.1 linux-intel 4.14 and add following configurations:

• Create file meta-intel/recipes-kernel/linux/linux-intel/usb.cfg and add below kernel configs to file usb.cfg:
CONFIG_USB_GADGET=y
CONFIG_NOP_USB_XCEIV=y
CONFIG_ETHER_GADGET=m
CONFIG_USB_DWC3=y
# CONFIG_USB_DWC3_HOST is not set (Gadget only!)
CONFIG_USB_DWC3_GADGET=y
CONFIG_USB_DWC3_PCI=m

• To include file "usb.cfg", add below line to kernel recipe file meta-intel/common/recipes-kernel/linux/linux-intel_4.14.bb
   SRC_URI_append = " file://usb.cfg<file:///\\usb.cfg>"

After adding above configurations successfully, build the image and boot it.

Finally, run following command on terminal:
1.       modprobe g_ether
2.       lsmod –  after modprobe g_ether, you will find g_ether in the list.
3.       Ifconfig – you can see usb0 interface now.

Thanks,
Juinee

From: meta-intel-bounces at yoctoproject.org<mailto:meta-intel-bounces at yoctoproject.org> [mailto:meta-intel-bounces at yoctoproject.org] On Behalf Of Henrik Haugaard Jensen
Sent: Wednesday, October 31, 2018 7:48 PM
To: meta-intel at yoctoproject.org<mailto:meta-intel at yoctoproject.org>
Subject: [meta-intel] g_ether functionality for Intel E3845 CPU (valley-island, bay-trail)

We have successfully used meta-intel jethro branch for our device based on an intel E3845 CPU.

Now we need to upgrade to a newer Linux kernel to get full camera/video/media support. But when building new BSP with sumo it turns out that g_ether usb gadget driver is not working neither with linux-intel 4.9 or 4.14.

My related kernel configs ( which works for meta-intel Jethro) are:
CONFIG_USB_GADGET=y
CONFIG_NOP_USB_XCEIV=y
CONFIG_ETHER_GADGET=m
CONFIG_USB_DWC3=y
# CONFIG_USB_DWC3_HOST is not set (Gadget only!)
CONFIG_USB_DWC3_GADGET=y
CONFIG_USB_DWC3_PCI=m

The error I get is :
udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers

and the usb0 network interface does not show up.

What am I missing?

Best Regards
Henrik

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-intel/attachments/20181204/8cf6edd3/attachment-0001.html>