USB mouse not working with Android jb4.2.2_1.0.0 BSP on SABRE SDB

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

USB mouse not working with Android jb4.2.2_1.0.0 BSP on SABRE SDB

Jump to solution
3,629 Views
llatvala
Contributor I

I'm setting up Sabre SDB imx6q board. Just got Android jb4.2.2_1.0.0 BSP demo image successfully installed and adjusted u-boot configuration according to the instructions.

 

Now there is still a problem with USB. I’m trying to connect a mouse into USB-OTG adapter.

I tried to connect directly and via powered usb hub, but there’s no response.

I've attached the boot log and there are some lines stating that USB is disabled: android_usb: already disabled

 

Any idea why and what to do to get USB working?

 

-Lari

Original Attachment has been moved to: jb422_bootlog.txt.zip

Labels (2)
Tags (4)
0 Kudos
1 Solution
833 Views
PeterChan
NXP Employee
NXP Employee

Are you trying the android_jb4.2.2_1.0.0-ga prebuilt image? When a USB mouse is plugged to the OTG port, you should see the following messages:

root@android:/ # ID int (ID is 0)

udc suspend begins

USB Gadget suspend ends

ehci fsl drv resume begins: DR

will resume roothub and its children

ehci_fsl_bus_resume begins, DR

ehci_fsl_bus_resume ends, DR

ehci fsl drv resume ends: DR

USB Charger Connected.

usb 1-1: new low speed USB device number 2 using fsl-ehci

usb 1-1: device v046d pc05a is not supported

input: Logitech USB Optical Mouse as /devices/platform/fsl-ehci.0/usb1/1-1/1-1:1.0/input/input9

generic-usb 0003:046D:C05A.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-fsl-ehci.0-1/input0

Please plug in the USB mouse before the android request suspend state. In this prebuilt image, USB device connection (such as USB mouse) does not wake up the board.

View solution in original post

0 Kudos
4 Replies
833 Views
Yuri
NXP Employee
NXP Employee

Note :USB OTG port of the SDB with special cable (USB_ID grounded) should used

to connect a USB device. The second USB connector of the SDP is used as console

(USB-to-UART).

0 Kudos
833 Views
llatvala
Contributor I

I created the following adapter which grounds the USB ID pin, and verified the connections with multimeter.

1 ---  Red   --- 1 (VBUS)

2 --- White --- 2 (D-)

3 --- Green --- 3 (D+)

4 --- Black --- 4 (ID)

5             \--- 5 (GND)

Didn't work for me. USB mouse is still not recognized during boot. The boot log is identical to the previously attached one.

Any idea why Android USB would be disabled during boot, as these messages would suggest: android_usb: already disabled

0 Kudos
833 Views
YixingKong
Senior Contributor IV

Ilatvala, please click Correct Answer/Helpful Answer if your issue has been resolved.

Thanks,

Yixing

0 Kudos
834 Views
PeterChan
NXP Employee
NXP Employee

Are you trying the android_jb4.2.2_1.0.0-ga prebuilt image? When a USB mouse is plugged to the OTG port, you should see the following messages:

root@android:/ # ID int (ID is 0)

udc suspend begins

USB Gadget suspend ends

ehci fsl drv resume begins: DR

will resume roothub and its children

ehci_fsl_bus_resume begins, DR

ehci_fsl_bus_resume ends, DR

ehci fsl drv resume ends: DR

USB Charger Connected.

usb 1-1: new low speed USB device number 2 using fsl-ehci

usb 1-1: device v046d pc05a is not supported

input: Logitech USB Optical Mouse as /devices/platform/fsl-ehci.0/usb1/1-1/1-1:1.0/input/input9

generic-usb 0003:046D:C05A.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-fsl-ehci.0-1/input0

Please plug in the USB mouse before the android request suspend state. In this prebuilt image, USB device connection (such as USB mouse) does not wake up the board.

0 Kudos