User Info
Добро пожаловать, Guest Пользователей: 4 Поисковых ботов: 3 Гостей: 1
ADA007
Пункты: 3113
Регистрация: 01.08.2011
Пол: Мужчина
И снова здравствуйте!
В ходе подключения USB возникла следующая проблема. Плата на imx233 ядро 2.6.35. Подсоединяю USB HUB 2.0 ... Система определяет, что мол Хаб подключен видит 4 порта USB. Подключаю флэш... система ее определяет .... флэшка монтируется и читается нормально. А вот клава с мыше никак не подхватываются ядром...все время вижу ругать типа
Код
usb 1-1.4: new low speed USB device using fsl-ehci and address 3
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: Cannot enable port 4. Maybe the USB cable is bad?
hub 1-1:1.0: cannot disable port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: Cannot enable port 4. Maybe the USB cable is bad?
hub 1-1:1.0: cannot disable port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: Cannot enable port 4. Maybe the USB cable is bad?
hub 1-1:1.0: cannot disable port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: Cannot enable port 4. Maybe the USB cable is bad?
hub 1-1:1.0: cannot disable port 4 (err = -71)
hub 1-1:1.0: unable to enumerate USB device on port 4
hub 1-1:1.0: cannot disable port 4 (err = -71)
usb 1-1: reset full speed USB device using fsl-ehci and address 2
И дальше все в таком духе....Помниться, читая тему "первые телодвижения" с платой imx233
sasamy сталкивался с проблемой нерабочей мыши&клавы.
Подскажите, как решается данная проблема?
ADA007
Пункты: 3113
Регистрация: 01.08.2011
Пол: Мужчина
Еще вот такую ругань выдает
Код
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 1
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 2
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 3
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 4
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 5
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 6
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 7
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 8
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 9
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 10
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 11
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 12
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 13
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 14
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 15
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 16
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 17
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 18
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 19
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 20
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 21
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 22
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 23
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 24
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 25
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 26
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 27
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 28
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 29
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 30
fsl-ehci fsl-ehci: detected XactErr len 0/8 retry 31
fsl-ehci fsl-ehci: devpath 1 ep0out 3strikes
usb usb1: clear tt buffer port 1, a7 ep0 t00080248
hub 1-1:1.0: cannot disable port 1 (err = -71)
hub 1-1:1.0: transfer --> -71
usb 1-1: unlink qh128-0e01/c3ce7a80 start 2 [1/2 us]
fsl-ehci fsl-ehci: reused qh c3ce7a80 schedule
usb 1-1: link qh128-0e01/c3ce7a80 start 2 [1/2 us]
hub 1-1:1.0: transfer --> -71
usb 1-1: unlink qh128-0e01/c3ce7a80 start 2 [1/2 us]
fsl-ehci fsl-ehci: reused qh c3ce7a80 schedule
usb 1-1: link qh128-0e01/c3ce7a80 start 2 [1/2 us]
hub 1-1:1.0: transfer --> -71
usb 1-1: unlink qh128-0e01/c3ce7a80 start 2 [1/2 us]
fsl-ehci fsl-ehci: reused qh c3ce7a80 schedule
usb 1-1: link qh128-0e01/c3ce7a80 start 2 [1/2 us]
hub 1-1:1.0: transfer --> -71
usb 1-1: unlink qh128-0e01/c3ce7a80 start 2 [1/2 us]
fsl-ehci fsl-ehci: reused qh c3ce7a80 schedule
usb 1-1: link qh128-0e01/c3ce7a80 start 2 [1/2 us]
hub 1-1:1.0: transfer --> -71
usb 1-1: unlink qh128-0e01/c3ce7a80 start 2 [1/2 us]
fsl-ehci fsl-ehci: reused qh c3ce7a80 schedule
usb 1-1: link qh128-0e01/c3ce7a80 start 2 [1/2 us]
hub 1-1:1.0: transfer --> -71
usb 1-1: unlink qh128-0e01/c3ce7a80 start 2 [1/2 us]
fsl-ehci fsl-ehci: reused qh c3ce7a80 schedule
usb 1-1: link qh128-0e01/c3ce7a80 start 2 [1/2 us]
hub 1-1:1.0: transfer --> -71
usb 1-1: unlink qh128-0e01/c3ce7a80 start 2 [1/2 us]
fsl-ehci fsl-ehci: reused qh c3ce7a80 schedule
usb 1-1: link qh128-0e01/c3ce7a80 start 2 [1/2 us]
hub 1-1:1.0: state 7 ports 3 chg 0000 evt 0000
hub 1-1:1.0: resetting for error -71
usb 1-1: unlink qh128-0e01/c3ce7a80 start 2 [1/2 us]
usb 1-1: reset full speed USB device using fsl-ehci and address 7
fsl-ehci fsl-ehci: port 1 high speed
fsl-ehci fsl-ehci: GetStatus port 1 status 10001805 POWER sig=j PE CONNECT
usb 1-1: ep0 maxpacket = 8
hub 1-1:1.0: enabling power on all ports
usb 1-1: link qh128-0e01/c3ce7a80 start 3 [1/2 us]
hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 1-1:1.0: state 7 ports 3 chg 0000 evt 0000
На сколько я понял из поиска по google - usb freescale пытается подключиться на 12 Мб\с как к full speed device к клаве и мыше, хотя они low speed. И хаб тут непричем...хоть 2.0 хоть 1.1 сувать нет разницы.
Вобщем пока подключить low speed device не удалось.
sasamy
Пункты: 83542
Регистрация: 14.08.2009
Цитата
На сколько я понял из поиска по google - usb freescale пытается подключиться на 12 Мб\с как к full speed device к клаве и мыше, хотя они low speed. И хаб тут непричем...хоть 2.0 хоть 1.1 сувать нет разницы.
Вобщем пока подключить low speed device не удалось.
Хаб
Цитата
usb 1-1: new high speed USB device using fsl-ehci and address 2
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
Клавиатура
Цитата
usb 1-1.3: new low speed USB device using fsl-ehci and address 3
input: HID 0566:3002 as /devices/platform/fsl-ehci/usb1/1-1/1-1.3/1-1.3:1.0/input/input0
generic-usb 0003:0566:3002.0001: input: USB HID v1.10 Keyboard [HID 0566:3002] on usb-fsl-ehci-1.3/input0
input: HID 0566:3002 as /devices/platform/fsl-ehci/usb1/1-1/1-1.3/1-1.3:1.1/input/input1
generic-usb 0003:0566:3002.0002: input: USB HID v1.10 Device [HID 0566:3002] on usb-fsl-ehci-1.3/input1
Мышь
Цитата
usb 1-1.2: new low speed USB device using fsl-ehci and address 5
input: Microsoft Microsoft Notebook/Mobile Optical Mouse 2.0 as /devices/platform/fsl-ehci/usb1/1-1/1-1.2/1-1.2:1.0/input/inp4
generic-usb 0003:045E:007D.0005: input: USB HID v1.10 Mouse [Microsoft Microsoft Notebook/Mobile Optical Mouse 2.0] on usb-fs0
ADA007
Пункты: 3113
Регистрация: 01.08.2011
Пол: Мужчина
Но у меня такая картина
Hub =
Код
usb 1-1: new full speed USB device using fsl-ehci and address 2
usb 1-1: New USB device found, idVendor=05e3, idProduct=0606
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1: Product: USB Hub 2.0
usb 1-1: Manufacturer: ALCOR
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
Мышь (такая ID 0458:009d KYE Systems Corp. (Mouse Systems))
Код
usb 1-1.4: new low speed USB device using fsl-ehci and address 3
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: Cannot enable port 4. Maybe the USB cable is bad?
hub 1-1:1.0: cannot disable port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: Cannot enable port 4. Maybe the USB cable is bad?
hub 1-1:1.0: cannot disable port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: Cannot enable port 4. Maybe the USB cable is bad?
hub 1-1:1.0: cannot disable port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: cannot reset port 4 (err = -71)
hub 1-1:1.0: Cannot enable port 4. Maybe the USB cable is bad?
hub 1-1:1.0: cannot disable port 4 (err = -71)
hub 1-1:1.0: unable to enumerate USB device on port 4
hub 1-1:1.0: cannot disable port 4 (err = -71)
usb 1-1: reset full speed USB device using fsl-ehci and address 2
Получается что он Мышь сует в адрес 3 ... не может подключить и сбрасывает хаб на порту 2.
Хотел в ядре отрубить ECHI HCD 2.0 .... но ядро компилится с ошибкой. Перебрал, наверное, уже все настройки в разделе usb ядра. Ничего пока не помогает...
Может ли это быть из-за root fs неправильно собранной?
Мой dmesg =
Код
Linux version 2.6.35.3 (root@celeron) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #324 PREEMPT Wed Mar 14 23:12:08
EET 2012
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Freescale MX23EVK board
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: console=ttyAM0,115200 ssp1=spi1 ssp2=mmc lcd_panel=tvenc_pal root=/dev/mmcblk0p2 rootwait
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 60640k/60640k available, 4896k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xfde00000 - 0xffe00000 ( 32 MB)
vmalloc : 0xc4800000 - 0xf0000000 ( 696 MB)
lowmem : 0xc0000000 - 0xc4000000 ( 64 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc0027000 ( 124 kB)
.text : 0xc0027000 - 0xc03f8000 (3908 kB)
.data : 0xc03f8000 - 0xc04243a0 ( 177 kB)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
RCU-based detection of stalled CPUs is disabled.
Verbose stalled-CPUs detection is disabled.
NR_IRQS:224
Console: colour dummy device 80x30
console [ttyAM0] enabled
Calibrating delay loop... 195.78 BogoMIPS (lpj=978944)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
regulator: dummy:
NET: Registered protocol family 16
regulator: vddd: 800 <--> 1575 mV at 1550 mV fast normal
regulator: vdddbo: 800 <--> 1575 mV fast normal
regulator: vdda: 1500 <--> 2275 mV at 1750 mV fast normal
regulator: vddio: 2800 <--> 3575 mV at 3300 mV fast normal
regulator: overall_current: fast normal
regulator: mxs-duart-1: fast normal
regulator: mxs-bl-1: fast normal
regulator: mxs-i2c-1: fast normal
regulator: mmc_ssp-1: fast normal
regulator: mmc_ssp-2: fast normal
regulator: charger-1: fast normal
regulator: power-test-1: fast normal
regulator: cpufreq-1: fast normal
i.MX IRAM pool: 28 KB@0xc4808000
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource mxs clock source
musb_hdrc: version 6.0, pio, host, debug=0
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
Bus freq driver module loaded
WARNING : No battery connected !
Aborting power driver initialization
mxs-battery: probe of mxs-battery.0 failed with error 1
mxs_cpu_init: cpufreq init finished
msgmni has been set to 118
alg: No test for stdrng (krng)
cryptodev: driver loaded.
io scheduler noop registered
io scheduler cfq registered (default)
Console: switching to colour frame buffer device 80x30
mxs-duart.0: ttyAM0 at MMIO 0x80070000 (irq = 0) is a DebugUART
brd: module loaded
loop: module loaded
mxs-spi mxs-spi.0: Max possible speed 96000 = 96000000/2 kHz
mxs-spi mxs-spi.0: at 0x80010000 mapped to 0xF0010000, irq=14, bus 1, DMA ver_major 3
ks8851 spi1.0: message enable is 0
ks8851 spi1.0: eth0: revision 1, MAC 1a:88:f8:47:56:3d, IRQ 195
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
usbcore: registered new interface driver hwa-rc
usbmon: debugfs is not available
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
fsl-ehci fsl-ehci: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci: irq 11, io base 0x80080000
fsl-ehci fsl-ehci: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: Freescale On-Chip EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.35.3 ehci_hcd
usb usb1: SerialNumber: fsl-ehci
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver wusb-cbaf
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
usbcore: registered new interface driver usblp
usbcore: registered new interface driver cdc_wdm
usbcore: registered new interface driver usbtmc
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver libusual
usbcore: registered new interface driver ums-alauda
usbcore: registered new interface driver ums-cypress
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-isd200
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-karma
usbcore: registered new interface driver ums-onetouch
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
usbcore: registered new interface driver ums-usbat
usbcore: registered new interface driver mdc800
mdc800: v0.7.5 (30/10/2000):USB Driver for Mustek MDC800 Digital Camera
usbcore: registered new interface driver microtekX6
usbcore: registered new interface driver usbserial
usbserial: USB Serial Driver core
usbcore: registered new interface driver adutux
adutux adutux (see www.ontrak.net) v0.0.13
adutux is an experimental driver. Use at your own risk
usbcore: registered new interface driver cypress_cy7c63
usbcore: registered new interface driver cytherm
cytherm: v1.0:Cypress USB Thermometer driver
usbcore: registered new interface driver emi26 - firmware loader
usbcore: registered new interface driver emi62 - firmware loader
driver ftdi-elan built at 23:12:03 on Mar 14 2012
usbcore: registered new interface driver ftdi-elan
idmouse: 0.6:Siemens ID Mouse FingerTIP Sensor Driver
usbcore: registered new interface driver idmouse
usbcore: registered new interface driver iowarrior
usbcore: registered new interface driver isight_firmware
usbcore: registered new interface driver usblcd
usbcore: registered new interface driver ldusb
usbcore: registered new interface driver usbled
usbcore: registered new interface driver legousbtower
legousbtower: v0.96:LEGO USB Tower Driver
usbcore: registered new interface driver rio500
rio500: v1.1:USB Rio 500 driver
usbcore: registered new interface driver usbtest
usbcore: registered new interface driver trancevibrator
trancevibrator: v1.1:PlayStation 2 Trance Vibrator driver
usbcore: registered new interface driver usbsevseg
mice: PS/2 mouse device common for all mice
Linux video capture interface: v2.00
mxs-pxp mxs-pxp.0: initialized
mxs watchdog: initialized, heartbeat 19 sec
mxs-mmc: MXS SSP Controller MMC Interface driver
mxs-mmc mxs-mmc.0: mmc0: MXS SSP MMC DMAIRQ 20 ERRIRQ 15
dcp dcp.0: DCP crypto enabled.!
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
mxs-adc-audio mxs-adc-audio.0: MXS ADC/DAC Audio Codec
No device for DAI mxs adc/dac
No device for DAI mxs adc/dac
asoc: mxs adc/dac <-> mxs adc/dac mapping ok
ALSA device list:
#0: MXS EVK (mxs adc/dac)
IPv4 over IPv4 tunneling driver
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
Waiting for root device /dev/mmcblk0p2...
mmc0: new high speed SD card at address b368
mmcblk0: mmc0:b368 NCard 1.86 GiB
mmcblk0: p1 p2
EXT2-fs (mmcblk0p2): warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem) on device 179:2.
Или тут причина более банальная : в том, что в ядре нет драйвера на данное устройство? Я уже теряюсь в догадках, что это может быть?