stability USB memory sticks for the common OHCI USB layer.
An embedded and charset-unspecified text was scrubbed...
Name: increase-usb-control-timeout.patch
Url: http://lists.denx.de/pipermail/u-boot/attachments/20080922/a51f2d88/attachment.txt
Le lundi 22 septembre 2008 ? 14:42 +0200, Remy Bohmer a ?crit :
Quoted 4 lines
pi?ce jointe document texte brut (increase-usb-control-timeout.patch) Hello Stelian,
As promised, here is the first patch to test.
Unfortunately it doesn't seem to make much difference, see the log below. I've enabled USB_DEBUG in common/usb.c in case some of the more verbose printouts ring someone's bell.
Quoted 3 lines
If it does not help, I would like to wait until you are able to verify if your problem with _your_ USB sticks also exists on a AT91sam9261-ek, to be able to differentiate if the problem is USB stick related or SoC related.
Sure, I'll try to test this next monday.
Stelian.
usb reset
(Re)start USB...
USB: scanning bus for devices... New Device 0usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0 length 0x40usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0 length 0x40usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0 length 0x40 set address 1usb_control_msg: request: 0x5, requesttype: 0x0, value 0x1 index 0x0 length 0x0usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0 length 0x12usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 index 0x0 length 0x8usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 index 0x0 length 0x19 get_conf_no 0 Result 25, wLength 25
if 0, ep 0
##EP epmaxpacketin[1] = 2
set configuration 1usb_control_msg: request: 0x9, requesttype: 0x0, value 0x1 index 0x0 length 0x0 new device strings: Mfr=0, Product=1, SerialNumber=0usb_control_msg: request: 0x6, requesttype: 0x80, value 0x300 index 0x0 length 0xFF USB device number 1 default language ID 0x409usb_control_msg: request: 0x6, requesttype: 0x80, value 0x301 index 0x409 length 0xFF Manufacturer
Product OHCI Root Hub
SerialNumberusb_control_msg: request: 0x6, requesttype: 0xA0, value 0x2900 index 0x0 length 0x4usb_control_msg: request: 0x6, requesttype: 0xA0, value 0x2900 index 0x0 length 0x9usb_control_msg: request: 0x0, requesttype: 0xA0, value 0x0 index 0x0 length 0x4usb_control_msg: request: 0x3, requesttype: 0x23, value 0x8 index 0x1 length 0x0usb_control_msg: request: 0x3, requesttype: 0x23, value 0x8 index 0x2 length 0x0usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length 0x4usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length 0x4usb_control_msg: request: 0x1, requesttype: 0x23, value 0x10 index 0x1 length 0x0usb_control_msg: request: 0x3, requesttype: 0x23, value 0x4 index 0x1 length 0x0usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length 0x4usb_control_msg: request: 0x1, requesttype: 0x23, value 0x14 index 0x1 length 0x0 New Device 1usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0 length 0x40
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5)usb_new_device: 64 byte descrusb_control_msg: request: 0x3, requesttype: 0x23, value 0x4 index 0x1 length 0x0usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length 0x4usb_control_msg: request: 0x1, requesttype: 0x23, value 0x14 index 0x1 length 0x0 set address 2usb_control_msg: request: 0x5, requesttype: 0x0, value 0x2 index 0x0 length 0x0
ERROR: submit_control_message: pipesize for pipe 80000000 is zero
USB device not accepting new address (error=80000000)usb_control_msg: request: 0x1, requesttype: 0x23, value 0x1 index 0x1 length 0x0usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x2 length 0x4 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
U-Boot>
Signature · 1 line
Stelian Pop <[email protected]>
Hello Stelian,
Thanks for the logging. This is useful info.
Quoted 5 lines
usb_control_msg: request:0x1, requesttype:0x23, value0x14index0x1length0x0New Device 1usb_control_msg: request:0x6, requesttype:0x80, value0x100index0x0length0x40
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5)
Apparently the 1st access to the device already fails.
Can you please try to set "#define CONFIG_LEGACY_USB_INIT_SEQ 1" in your include/configs/<board>.h ?
This enables the old way U-boot does the device initialisation. If this helps I have to check 1 of my patches, which changed this behaviour to make it compliant to the USB standard.
The legacy implementation of U-boot is just wrong, but it might work.
Kind Regards,
Remy
Quoted 20 lines
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5)
usb_new_device: 64 byte descrusb_control_msg: request:0x3, requesttype:0x23, value0x4index0x1length0x0usb_control_msg: request:0x0, requesttype:0xA3, value0x0index0x1length0x4usb_control_msg: request:0x1, requesttype:0x23, value0x14index0x1length0x0set address 2usb_control_msg: request:0x5, requesttype:0x0, value0x2index0x0length0x0
ERROR:submit_control_message: pipesize for pipe 80000000 is zeroUSB device not accepting new address (error=80000000)
usb_control_msg: request:0x1, requesttype:0x23, value0x1index0x1length0x0usb_control_msg: request:0x0, requesttype:0xA3, value0x0index0x2length0x42 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
U-Boot>
--
Stelian Pop <[email protected]>
Le mardi 23 septembre 2008 ? 12:31 +0200, Remy Bohmer a ?crit :
Quoted 10 lines
Hello Stelian,
Thanks for the logging. This is useful info.
Quoted 5 lines
usb_control_msg: request:0x1, requesttype:0x23, value0x14index0x1length0x0New Device 1usb_control_msg: request:0x6, requesttype:0x80, value0x100index0x0length0x40
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5)
Quoted 7 lines
Apparently the 1st access to the device already fails.
Can you please try to set "#defineCONFIG_LEGACY_USB_INIT_SEQ1" in your include/configs/<board>.h ?
This enables the old way U-boot does the device initialisation. If this helps I have to check 1 of my patches, which changed this behaviour to make it compliant to the USB standard.
The legacy implementation of U-boot is just wrong, but it might work.
Already did, and didn't change much... it still fails more or less the same way.
Signature · 1 line
Stelian Pop <[email protected]>