iMX6 SABRE SD can't see USB mouse and keyboard

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

iMX6 SABRE SD can't see USB mouse and keyboard

Jump to solution
6,883 Views
mogenslauridsen
Contributor III

Hi,

I have just received a iMX6 SABRE SD board (MCIMX6Q-SDB) but I can't make external usb mouse/keyboard work.

I have attached an usb mouse and keyboard via a hub which is connected to the USB OTG (J505). Then I inserted the supplied SD card (marked MX6Q-SDB Android r13.4) and powered on the board.

I can see on the debug console that the CPU boots, and after a while I see the the Android logo and start image on the attached HDMI monitor.

Everything looks fine.... but the board does not seem to power on the usb mouse/keyboard and does not respond to them at all. I have tried external power to the usb hub, but that didn't change anything. I have also tried connecting the mouse or keyboard directly to the usb otg. Still no contact...

I have tried to connect the usb otg to a PC, and can see the files on the SD card/board via the PC. So the connector seem to be OK.

My board is marked with these two revision number labels:

SCH-27516 Rev C2

700-27516 Rev A

I am a bit worried by the message from U-Boot:

"Board: i.MX6Q-SABRESD: unknown-board Board: 0x63012 [POR ]"

Is this board newer/incompatible with the supplied Android image?

/Mogens

************************************************* debug console ******************************************

U-Boot 2009.08-00602-g3f71ed9 (Nov 26 2012 - 17:31:49)

CPU: Freescale i.MX6 family TO1.2 at 792 MHz

Temperature:   43 C, calibration data 0x59a4d77d

mx6q pll1: 792MHz

mx6q pll2: 528MHz

mx6q pll3: 480MHz

mx6q pll8: 50MHz

ipg clock     : 66000000Hz

ipg per clock : 66000000Hz

uart clock    : 80000000Hz

cspi clock    : 60000000Hz

ahb clock     : 132000000Hz

axi clock   : 264000000Hz

emi_slow clock: 29333333Hz

ddr clock     : 528000000Hz

usdhc1 clock  : 198000000Hz

usdhc2 clock  : 198000000Hz

usdhc3 clock  : 198000000Hz

usdhc4 clock  : 198000000Hz

nfc clock     : 24000000Hz

Board: i.MX6Q-SABRESD: unknown-board Board: 0x63012 [POR ]

Boot Device: SD

I2C:   ready

DRAM:   1 GB

MMC:   FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2,FSL_USDHC: 3

In:    serial

Out:   serial

Err:   serial

i2c: I2C2 SDA is low, start i2c recovery...

I2C2 Recovery success

i2c: I2C3 SDA is low, start i2c recovery...

I2C3 Recovery success

Found PFUZE100! device id=10

Net:   got MAC address from IIM: 00:04:9f:02:6e:97

FEC0 [PRIME]

Hit any key to stop autoboot:  0

kernel   @ 10808000 (4089604)

ramdisk  @ 11800000 (167796)

kernel cmdline:

        use uboot command line:

        console=ttymxc0,115200 androidboot.console=ttymxc0 vmalloc=400M init=/init video=mxcfb0:dev=hdmi,1920x1080M@60 video=mxcfb1:off video=mxcfb2:off fbmem=28M

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Initializing cgroup subsys cpuset

Initializing cgroup subsys cpu

Linux version 3.0.35-04880-gc9dfae3 (jkudrick@kudrick-10) (gcc version 4.4.3 (GCC) ) #3 SMP PREEMPT Tue Oct 23 23:22:08 CDT 2012

CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d

CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache

Machine: Freescale i.MX 6Quad/DualLite/Solo Sabre-SD Board

Ignoring unrecognised tag 0x54410008

Memory policy: ECC disabled, Data cache writealloc

CPU identified as i.MX6Q, silicon rev 1.2

PERCPU: Embedded 7 pages/cpu @c1138000 s5760 r8192 d14720 u32768

Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 203776

Kernel command line: console=ttymxc0,115200 androidboot.console=ttymxc0 vmalloc=400M init=/init video=mxcfb0:dev=hdmi,1920x1080M@60 video=mxcfb1:off video=mxcfb2:off fbmem=28M

PID hash table entries: 2048 (order: 1, 8192 bytes)

Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)

Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)

Memory: 576MB 228MB = 804MB total

Memory: 804976k/804976k available, 243600k reserved, 413696K highmem

Virtual kernel memory layout:

    vector  : 0xffff0000 - 0xffff1000   (   4 kB)

    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)

    DMA     : 0xfbe00000 - 0xffe00000   (  64 MB)

    vmalloc : 0xd9800000 - 0xf2000000   ( 392 MB)

    lowmem  : 0xc0000000 - 0xd9000000   ( 400 MB)

    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)

    modules : 0xbf000000 - 0xbfe00000   (  14 MB)

      .init : 0xc0008000 - 0xc0042000   ( 232 kB)

      .text : 0xc0042000 - 0xc0791d40   (7488 kB)

      .data : 0xc0792000 - 0xc0800580   ( 442 kB)

       .bss : 0xc08005a4 - 0xc092efd0   (1211 kB)

Preemptible hierarchical RCU implementation.

NR_IRQS:496

MXC GPIO hardware

sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms

MXC_Early serial console at MMIO 0x2020000 (options '115200')

bootconsole [ttymxc0] enabled

Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)

pid_max: default: 32768 minimum: 301

Mount-cache hash table entries: 512

Initializing cgroup subsys cpuacct

CPU: Testing write buffer coherency: ok

hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available

CPU1: Booted secondary processor

CPU2: Booted secondary processor

CPU3: Booted secondary processor

Brought up 4 CPUs

SMP: Total of 4 processors activated (6324.22 BogoMIPS).

print_constraints: dummy:

NET: Registered protocol family 16

print_constraints: vddpu: 725 <--> 1300 mV at 1100 mV fast normal

print_constraints: vddcore: 725 <--> 1300 mV at 1100 mV fast normal

print_constraints: vddsoc: 725 <--> 1300 mV at 1200 mV fast normal

print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal

print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal

print_constraints: vdd3p0: 2800 <--> 3150 mV at 3000 mV fast normal

hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.

hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.

hw-breakpoint: maximum watchpoint size is 4 bytes.

L310 cache controller enabled

l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x02070000, Cache size: 1048576 B

IMX usb wakeup probe

bio: create slab <bio-0> at 0

print_constraints: SPKVDD: 4200 mV

print_constraints: vmmc: 3300 mV

SCSI subsystem initialized

spi_imx imx6q-ecspi.0: probed

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

Freescale USB OTG Driver loaded, $Revision: 1.55 $

add wake up source irq 75

mc_pfuze 1-0008: ID: 0,Full lay: 1 ,Metal lay: 1

mc_pfuze 1-0008: FAB: 0 ,FIN: 0

print_constraints: PFUZE100_SW1A: 300 <--> 1875 mV at 1425 mV

print_constraints: PFUZE100_SW1B: 300 <--> 1875 mV at 300 mV

print_constraints: PFUZE100_SW1C: 300 <--> 1875 mV at 1425 mV

print_constraints: PFUZE100_SW2: 800 <--> 3950 mV at 3300 mV

print_constraints: PFUZE100_SW3A: 400 <--> 1975 mV at 1500 mV

print_constraints: PFUZE100_SW3B: 400 <--> 1975 mV at 1500 mV

print_constraints: PFUZE100_SW4: 800 <--> 3950 mV at 3150 mV

print_constraints: PFUZE100_SWBST: 5000 <--> 5150 mV at 5000 mV

print_constraints: PFUZE100_VSNVS: 1200 <--> 3000 mV at 1800 mV

print_constraints: PFUZE100_VREFDDR: at 750 mV

print_constraints: PFUZE100_VGEN1: 800 <--> 1550 mV at 1500 mV

print_constraints: PFUZE100_VGEN2: 800 <--> 1550 mV at 1500 mV

print_constraints: PFUZE100_VGEN3: 1800 <--> 3300 mV at 2800 mV

print_constraints: PFUZE100_VGEN4: 1800 <--> 3300 mV at 1800 mV

print_constraints: PFUZE100_VGEN5: 1800 <--> 3300 mV at 3000 mV

print_constraints: PFUZE100_VGEN6: 1800 <--> 3300 mV at 3300 mV

imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)

imx-ipuv3 imx-ipuv3.1: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)

mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 driver probed

mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 dphy version is 0x3130302a

MIPI CSI2 driver module loaded

Advanced Linux Sound Architecture Driver Version 1.0.24.

Bluetooth: Core ver 2.16

NET: Registered protocol family 31

Bluetooth: HCI device and connection manager initialized

Bluetooth: HCI socket layer initialized

Bluetooth: L2CAP socket layer initialized

Bluetooth: SCO socket layer initialized

max17135 2-0048: PMIC MAX17135 for eInk display

i2c-core: driver [max17135] using legacy suspend method

i2c-core: driver [max17135] using legacy resume method

Switching to clocksource mxc_timer1

NET: Registered protocol family 2

IP route cache hash table entries: 16384 (order: 4, 65536 bytes)

TCP established hash table entries: 65536 (order: 7, 524288 bytes)

TCP bind hash table entries: 65536 (order: 7, 786432 bytes)

TCP: Hash tables configured (established 65536 bind 65536)

TCP reno registered

UDP hash table entries: 256 (order: 1, 8192 bytes)

UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)

NET: Registered protocol family 1

RPC: Registered named UNIX socket transport module.

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

RPC: Registered tcp NFSv4.1 backchannel transport module.

Unpacking initramfs...

Freeing initrd memory: 160K

PMU: registered new PMU device of type 0

Static Power Management for Freescale i.MX6

wait mode is enabled for i.MX6

cpaddr = d9880000 suspend_iram_base=d98fc000

PM driver module loaded

IMX usb wakeup probe

i.MXC CPU frequency driver

highmem bounce pool size: 64 pages

ashmem: initialized

JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.

msgmni has been set to 764

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

mxc_mipi_dsi mxc_mipi_dsi: i.MX MIPI DSI driver probed

MIPI DSI driver module loaded

mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver hdmi

mxc_hdmi mxc_hdmi: Detected HDMI controller 0x13:0xa:0xa0:0xc1

fbcvt: 1920x1080@60: CVT Name - 2.073M9

imx-ipuv3 imx-ipuv3.0: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)

mxc_sdc_fb mxc_sdc_fb.1: Can't get fb option for mxcfb1!

mxc_sdc_fb mxc_sdc_fb.2: Can't get fb option for mxcfb2!

imx-sdma imx-sdma: loaded firmware 1.1

imx-sdma imx-sdma: initialized

fbcvt: 1920x1080@60: CVT Name - 2.073M9

Serial: IMX driver

imx-uart.2: ttymxc2 at MMIO 0x21ec000 (irq = 60) is a IMX

imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX

console [ttymxc0] enabled, bootconsole disabled

console [ttymxc0] enabled, bootconsole disabled

loop: module loaded

m25p80 spi0.0: unrecognized JEDEC id ffffff

vcan: Virtual CAN interface driver

CAN device driver interface

flexcan netdevice driver

FEC Ethernet Driver

fec_enet_mii_bus: probed

PPP generic driver version 2.4.2

PPP Deflate Compression module registered

PPP BSD Compression module registered

PPP MPPE Compression module registered

NET: Registered protocol family 24

PPTP driver version 0.8.5

tun: Universal TUN/TAP device driver, 1.6

tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>

ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1

fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000

fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

add wake up source irq 72

fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2

fsl-ehci fsl-ehci.1: irq 72, io base 0x02184200

fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00

hub 2-0:1.0: USB hub found

hub 2-0:1.0: 1 port detected

usbcore: registered new interface driver cdc_acm

cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

usbcore: registered new interface driver usbserial

usbserial: USB Serial Driver core

USB Serial support registered for GSM modem (1-port)

usbcore: registered new interface driver option

option: v0.7.2:USB Driver for GSM modems

USB Serial support registered for Qualcomm USB modem

usbcore: registered new interface driver qcserial

ARC USBOTG Device Controller driver (1 August 2005)

android_usb gadget: Mass Storage Function, version: 2009/09/11

android_usb gadget: Number of LUNs=1

lun0: LUN: removable file: (no medium)

Gadget Android: controller 'fsl-usb2-udc' not recognized

android_usb gadget: android_usb ready

Suspend udc for OTG auto detect

fsl-usb2-udc: bind to driver android_usb

mousedev: PS/2 mouse device common for all mice

input: gpio-keys as /devices/platform/gpio-keys/input/input0

input: max11801_ts as /devices/platform/imx-i2c.1/i2c-1/1-0048/input/input1

egalax_ts 1-0004: egalax_ts: failed to read firmware version

egalax_ts: probe of 1-0004 failed with error -5

egalax_ts 2-0004: egalax_ts: failed to read firmware version

egalax_ts: probe of 2-0004 failed with error -5

elan - Read Hello Packet Failed

elan-touch: probe of 2-0010 failed with error -22

i2c-core: driver [isl29023] using legacy suspend method

i2c-core: driver [isl29023] using legacy resume method

using rtc device, snvs_rtc, for alarms

snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0

i2c /dev entries driver

Linux video capture interface: v2.00

ov5642_read_reg:write reg error:reg=300a

ov5642_probe:cannot find camera

ov5640_read_reg:write reg error:reg=300a

ov5640_probe:cannot find camera

mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16

mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17

usbcore: registered new interface driver uvcvideo

USB Video Class driver (v1.1.0)

mag3110 2-000e: check mag3110 chip ID

input: mag3110 as /devices/virtual/input/input2

mag3110 2-000e: mag3110 is probed

i2c-core: driver [mag3110] using legacy suspend method

i2c-core: driver [mag3110] using legacy resume method

input: mma845x as /devices/virtual/input/input3

imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)

device-mapper: uevent: version 1.0.3

device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: dm-devel@redhat.com

Bluetooth: Virtual HCI driver ver 1.3

Bluetooth: HCI UART driver ver 2.2

Bluetooth: HCIATH3K protocol initialized

Bluetooth: Generic Bluetooth USB driver ver 0.6

usbcore: registered new interface driver btusb

sdhci: Secure Digital Host Controller Interface driver

sdhci: Copyright(c) Pierre Ossman

mmc0: SDHCI controller on platform [sdhci-esdhc-imx.3] using DMA

mmc1: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA

mmc2: SDHCI controller on platform [sdhci-esdhc-imx.1] using DMA

mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed

VPU initialized

mxc_asrc registered

revserved_memory_account:viv_gpu registerd

Thermal calibration data is 0x59a4d77d

Anatop Thermal registered as thermal_zone0

anatop_thermal_probe: default cooling device is cpufreq!

usbcore: registered new interface driver usbhid

usbhid: USB HID core driver

logger: created 256K log 'log_main'

logger: created 256K log 'log_events'

logger: created 256K log 'log_radio'

logger: created 256K log 'log_system'

usbcore: registered new interface driver snd-usb-audio

mxc_hdmi_soc mxc_hdmi_soc.0: MXC HDMI Audio

Cirrus Logic CS42888 ALSA SoC Codec Driver

i2c-core: driver [cs42888] using legacy suspend method

i2c-core: driver [cs42888] using legacy resume method

mmc0: new high speed DDR MMC card at address 0001

mmcblk0: mmc0:0001 SEM08G 7.39 GiB

mmcblk0boot0: mmc0:0001 SEM08G partition 1 2.00 MiB

mmcblk0boot1: mmc0:0001 SEM08G partition 2 2.00 MiB

mmcblk0: unknown partition table

wm8962 0-001a: customer id 0 revision D

mmcblk0boot1: unknown partition table

mmcblk0boot0: unknown partition table

input: WM8962 Beep Generator as /devices/platform/imx-i2c.0/i2c-0/0-001a/input/input4

asoc: wm8962 <-> imx-ssi.1 mapping ok

imx_3stack asoc driver

asoc: mxc-hdmi-soc <-> imx-hdmi-soc-dai.0 mapping ok

ALSA device list:

  #0: wm8962-audio

  #1: imx-hdmi-soc

Netfilter messages via NETLINK v0.30.

nf_conntrack version 0.5.0 (12580 buckets, 50320 max)

ctnetlink v0.93: registering with nfnetlink.

NF_TPROXY: Transparent proxy support initialized, version 4.1.0

NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.

xt_time: kernel timezone is -0000

IPv4 over IPv4 tunneling driver

GRE over IPv4 demultiplexor driver

ip_tables: (C) 2000-2006 Netfilter Core Team

arp_tables: (C) 2002 David S. Miller

TCP cubic registered

NET: Registered protocol family 10

ip6_tables: (C) 2000-2006 Netfilter Core Team

IPv6 over IPv4 tunneling driver

NET: Registered protocol family 17

NET: Registered protocol family 15

can: controller area network core (rev 20090105 abi 8)

NET: Registered protocol family 29

can: raw protocol (rev 20090105)

can: broadcast manager protocol (rev 20090105 t)

Bluetooth: RFCOMM TTY layer initialized

Bluetooth: RFCOMM socket layer initialized

Bluetooth: RFCOMM ver 1.11

Bluetooth: BNEP (Ethernet Emulation) ver 1.3

Bluetooth: BNEP filters: protocol multicast

Bluetooth: HIDP (Human Interface Emulation) ver 1.2

L2TP core driver, V2.0

PPPoL2TP kernel driver, V2.0

L2TP IP encapsulation support (L2TPv3)

L2TP netlink interface

L2TP ethernet pseudowire support (L2TPv3)

lib80211: common routines for IEEE802.11 drivers

VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4

Bus freq driver module loaded

mmc1: new high speed SDHC card at address e624

mmcblk1: mmc1:e624 SU08G 7.40 GiB

Bus freq driver Enabled

mmcblk1: p1 p2 p3 < p5 p6 p7 p8 p9 > p4

mxc_dvfs_core_probe

DVFS driver module loaded

regulator_init_complete: PFUZE100_VGEN6: incomplete constraints, leaving on

regulator_init_complete: PFUZE100_VGEN3: incomplete constraints, leaving on

regulator_init_complete: PFUZE100_VGEN2: incomplete constraints, leaving on

regulator_init_complete: PFUZE100_VGEN1: incomplete constraints, leaving on

regulator_init_complete: vddpu: incomplete constraints, leaving on

snvs_rtc snvs_rtc.0: setting system clock to 2013-05-14 12:29:18 UTC (1368534558)

Freeing init memory: 232K

init: cannot find '/system/bin/gpu_init.sh', disabling 'gpu_init'

init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'

android_usb: already disabled

mtp_bind_config

warning: `rild' uses 32-bit capabilities (legacy support in use)

root@android:/ # input: eCompass as /devices/virtual/input/input5

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

request_suspend_state: wakeup (3->0) at 17025111004 (2013-05-14 12:29:31.827944670 UTC)

eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:01, irq=-1)

ADDRCONF(NETDEV_UP): eth0: link is not ready

acc_open

acc_release

CPU3: shutdown

CPU2: shutdown

PHY: 1:01 - Link is Up - 1000/Full

ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready


Labels (2)
Tags (3)
0 Kudos
1 Solution
1,864 Views
mogenslauridsen
Contributor III

I have found the problem:

The OTG-USB plug I used didn't ground pin 5 in the usb plug. So the board didn't switch to usb host.

After this, the mouse and keyboard works!

View solution in original post

0 Kudos
7 Replies
1,864 Views
brajeshsharma
Contributor II

Hi Mogens ,

I am facing the similar problem with USB mouse and Keyboard and getting the same log as you are getting on boot regrading android_usb . As mentioned here i shorted the pin 4 & 5 of OTG plug on my board but still the same problem . Please suggest something on it .

Thanks & Regards

Brajesh Sharma

0 Kudos
1,865 Views
mogenslauridsen
Contributor III

I have found the problem:

The OTG-USB plug I used didn't ground pin 5 in the usb plug. So the board didn't switch to usb host.

After this, the mouse and keyboard works!

0 Kudos
1,864 Views
carlobarbaro
Contributor III

Hello, I'm encountering your same problem: brand new SABRE SD board with default Android image, but connecting a powered usb hub with a mouse + keyboard these peripherals don't work.

The only difference is that my OTG-USB plug HAS USB_OTG_ID pin grounded (it is pin 4 in the usb plug and is connected to pin 5 = ground).

When the board performs the boot process, I get the same boot log as your and mouse don't work (it is an optical mouse and don't ever get powered since the led don't lit)

If I connect the hub (with mouse attached) after the system has booted I get the following log message:

otg udc vbus rising wakeup

USB Charger Connected.

Any suggestion?

Can you post the log message generated by your working SABRE SD when you plug-in your hub with mouse and keyboard attached?

Thank you and best regards

Carlo

0 Kudos
1,864 Views
brajeshsharma
Contributor II

Hi Carlo ,

I am facing the similar problem with USB mouse and Keyboard and getting the same log as mentioned here on top during  boot ( regrading android_usb ) . As you suggested  i shorted the pin 4 & 5 of OTG plug on my sabreSD board  but still the same problem . Please suggest something on it .

Thanks & Regards

Brajesh Sharma

0 Kudos
1,864 Views
mogenslauridsen
Contributor III

Hi,

I have now checked the output to the console. (Using the Android image delivered together with the board)

When I plug in the OTG-USB cable:

     USB Charger Connected.

And when I connect a mouse to the OTG-USB cable:

     usb 1-1: new low speed USB device number 2 using fsl-ehci usb 1-1: device v04b3 p310c is not supported

     input: USB Optical Mouse as

     /devices/platform/fsl-ehci.0/usb1/1-1/1-1:1.0/input/input6

     generic-usb 0003:04B3:310C.0001: input,hidraw0: USB HID v1.11 Mouse [USB Optical Mouse] on usb-fsl-ehci.0-1/input0

Hope this helps you.

Best regards,

Mogens

0 Kudos
1,864 Views
carlobarbaro
Contributor III

Hello Mogens,

seems that in my log is missing the second part, i.e. the USB device detected.

When I saw your post I thinked immediately that the problem was the cable so I hardwired the USB_OTG_ID pin to ground, but without success.

Effectively I verified that my cable already made the right connection.

I think I'm running on some incompatibility problem with mouse or the hub I'm using.

When I'll find a suitable adapter I'll try to connect the mouse direcly to the Sabre OTG port, without any hub.

Thank you and best regards,

Carlo

0 Kudos
1,864 Views
mogenslauridsen
Contributor III

Hi,

The board is at my work and I am home right now, so I can't make a log file for you. I might be able to do that tomorrow or Monday.

I made a short circuit between pin 4 and pin 5 on the Sabre board to verify that the problem was in my USB-OTG plug. After this short-circuit the mouse/keyboard worked. (And I believe it worked until I rebooted the board, even when I removed the short-circuit).

You can try that and see if it helps. (I was also sure I had the right USB-OTG plug, until I realized that I didn't :-)).

BTW: I don't use power on the USB hub. The Sabre board can deliver power for both keyboard and mouse (at least in my case).

Best regards,

Mogens

0 Kudos