USB keyboard and USB mouse not detected on Apalis iMX6 Dual?

Tips on what to check to troubleshoot USB devices are not being detected?

lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  • The keyboard works fine on other embedded Linux devices.
  • The keyboard had worked previously ( yet not the same image version ).

dmesg output:

    dmesg |grep -i USB
    [    0.085674] usb_host_vbus: supplied by usb_host_vbus_hub
    [    0.087026] usbcore: registered new interface driver usbfs
    [    0.087071] usbcore: registered new interface driver hub
    [    0.087149] usbcore: registered new device driver usb
    [    0.523526] usbcore: registered new interface driver asix
    [    0.523576] usbcore: registered new interface driver ax88179_178a
    [    0.523609] usbcore: registered new interface driver cdc_ether
    [    0.523644] usbcore: registered new interface driver net1080
    [    0.523679] usbcore: registered new interface driver cdc_subset
    [    0.523714] usbcore: registered new interface driver zaurus
    [    0.523773] usbcore: registered new interface driver cdc_ncm
    [    0.523779] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    [    0.523974] usbcore: registered new interface driver usb-storage
    [    0.524053] usbcore: registered new interface driver usbserial
    [    0.524086] usbcore: registered new interface driver usbserial_generic
    [    0.524120] usbserial: USB Serial support registered for generic
    [    0.524151] usbcore: registered new interface driver ftdi_sio
    [    0.524177] usbserial: USB Serial support registered for FTDI USB Serial Device
    [    0.524205] usbcore: registered new interface driver pl2303
    [    0.524231] usbserial: USB Serial support registered for pl2303
    [    0.525382] usbmisc_imx 2184800.usbmisc: 2184800.usbmisc supply vbus-wakeup not found, using dummy regulator
    [    0.526478] imx_usb 2184000.usb: 2184000.usb supply vbus not found, using dummy regulator
    [    0.531706] imx_usb 2184200.usb: 2184200.usb supply vbus not found, using dummy regulator
    [    0.534953] ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 1
    [    0.562762] ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00
    [    0.563455] hub 1-0:1.0: USB hub found
    [    0.928151] usbcore: registered new interface driver usbhid
    [    0.928155] usbhid: USB HID core driver
    [    7.706837] usb0: HOST MAC be:43:b9:5c:15:18
    [    7.709773] usb0: MAC 0a:43:7d:c2:9b:6d
    [    7.781194] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
    [   31.192855] usb_otg_vbus: disabling
    [   31.192868] usb_host_vbus_hub: disabling
    [   31.192879] usb_host_vbus: disabling

Thanks in advance for any tips or suggestions,

-Ed

Could you provide some details?

  • carrier board you are using

  • Image version

  • Boot your board without keyboard, insert keyboard, Collect full dmesg and lsusb output and attach them as a text files.

The current build broke somethings. When I rollback to a previous image, USB keyboard and mouse worked fine. I will use previous image for now. Thanks you. -Ed

hi @embeddedEd

Thanks for your Input.
I would recommend you to stick to Bsp 3.0.4 and move Bsp 5.0, once we have done a public release.

Best regards,
Jaski

I had a similar issue with a Colibri iMX6 Dual. It seems that the imx6qdl-colibri.dtsi previously, 2.8b6 bsp, had a device tree node for usbh1, which is no longer present in the 3.0.4 bsp.

&usbh1 {
vbus-supply = <&reg_usb_host_vbus>;
status = “disabled”;
};

The device tree imx6dl-colibri-eval-v3.dts in the 3.0.4 bsp changed to:
&usbh1 {
vbus-supply = <&reg_usb_host_vbus>;
status = “okay”;
};

I assume something similar happened in the Apalis device tree files. I am using a custom device tree based on the colibri eval device tree and when I added the vbus-supply property my USB devices started working again.

Regards,
Chris

The formatting seemed to replace text in my previous comment. Maybe a code block will work.

&usbh1 {
	vbus-supply = <&reg_usb_host_vbus>;
	status = "okay";
};

Regards,
Chris

Dear @ChrisP,

Thanks a lot for the feedback. We moved the usbh1 node from the dtsi file to the dts file. If you have a custom device tree file you have to add the changes there as you figured out yourself

Best Regards,

Janani