Angstrom Console - USB not working?

GoogleGroups
1

Hi all,

I'm using an angstrom root file system, with my own uImage, compiled
from kernel 2.6.37. I access the console trough serial interface (with
serial to usb convertor.)

I enabled all kernel flags for HID, USB, keboard, etc. But when I
start up my system my USB devices don't seem to be powered up. (eg. my
lasermouse isn't giving any light, also my keyboard isn't working...)

* not when using an external USB hub (powered externally)
* not when connecting a mouse
* not when connecting a keyboard.

I think I'm missing something trivial here... any ideas? (eg. when
hitting the console, and not running X11 or anything, can I use the
mouse? or is there a command needed to power them up?)

Thanks

2

Are you using power supply or powered from USB cable?

3

The serial port designation is differentt in 2.6.37.

From Robert earlier:

Double check:
http://elinux.org/BeagleBoardDebian#Serial_Ports
with: uname -r
2.6.35.X-xX and < = ttyS2
2.6.36++ = ttyO2…

Gerald

4

@Gerald: Yes, I have no problem talking to the console, I changed all
ports to tty02. I can do everything, I have internet etc, only no usb.

@Caius: I'm using a power supply for the board.

Thanks.

5

You're probably missing the angstrom patches to make 2.6.37 work

6

Could you point me to these patches?

7

It seems I didn't have the flag EHCI set when compiling the kernel.
(DeviceDrivers -> USB support -> EHCI)

now, lsusb gives me:
root@beagleboard:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and in the logs I get:
root@beagleboard:~# dmesg | grep usb
[ 0.064544] usbcore: registered new interface driver usbfs
[ 0.065490] usbcore: registered new interface driver hub
[ 0.066162] usbcore: registered new device driver usb
[ 2.589599] drivers/usb/core/inode.c: creating file 'devices'
[ 2.589904] drivers/usb/core/inode.c: creating file '001'
[ 2.620605] usb usb1: default language 0x0409
[ 2.620697] usb usb1: udev 1, busnum 1, minor = 0
[ 2.620727] usb usb1: New USB device found, idVendor=1d6b,
idProduct=0002
[ 2.627868] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 2.635467] usb usb1: Product: OMAP-EHCI Host Controller
[ 2.641021] usb usb1: Manufacturer: Linux 2.6.37-dirty ehci_hcd
[ 2.647247] usb usb1: SerialNumber: ehci-omap.0
[ 2.654266] usb usb1: usb_probe_device
[ 2.654296] usb usb1: configuration #1 chosen from 1 choice
[ 2.654907] usb usb1: adding 1-0:1.0 (config #1, interface 0)
[ 2.656188] hub 1-0:1.0: usb_probe_interface
[ 2.656219] hub 1-0:1.0: usb_probe_interface - got id
[ 2.667449] drivers/usb/core/inode.c: creating file '001'
[ 3.870117] usbcore: registered new interface driver usbhid
[ 3.876007] usbhid: USB HID core driver
[ 5.778533] usb usb1: bus auto-suspend
[ 66.418426] usb usb1: usb auto-resume
[ 68.777954] usb usb1: bus auto-suspend
[ 828.681610] usb usb1: usb auto-resume
[ 830.777984] usb usb1: bus auto-suspend

but the red light of the mouse isn't on yet... any ideas?

root@beagleboard:~# ls /dev/input/
by-path event0 mice

Thanks

8

Your using an xM board right?

2.6.37 doesn't turn on the ehci regulator for the xM:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.37.y.git;a=history;f=arch/arm/mach-omap2/board-omap3beagle.c;h=14f42240ae792bf01fcd289d60d441d9d55eb328;hb=HEAD

they were merged in 2.6.38-rc's..
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=arch/arm/mach-omap2/board-omap3beagle.c;h=46d814ab5656c078e6fad0a013c2ce8c39e312e5;hb=HEAD

Regards,

9

I'm using an IGEPv2 actually, so a beagleboard clone. (beagleboard was
out of stock at that time)

After setting the kernel flags for EHCI support I got it working, no
patching was needed.

Thanks for the help!