[U-Boot] USB EHCI driver

[U-Boot] USB EHCI driver

[FrancescoVT]

Hi,

I'm developing an USB EHCI driver for ADS5121e. Now , I completed
initialization sequence for my SOC EHCI Controller. My scope is to use with
mass storage, but I think that ehci core layer don't work correctly. Do
somebody use EHCI CORE layer for Mass storage and it was ok? 

Thank you.
-- 
View this message in context: http://www.nabble.com/USB-EHCI-driver-tp22598488p22598488.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

[U-Boot] USB EHCI driver

[Michael Trimarchi]

Hi,

FrancescoVT wrote:
> Hi,
>
> I'm developing an USB EHCI driver for ADS5121e. Now , I completed
> initialization sequence for my SOC EHCI Controller. My scope is to use with
> mass storage, but I think that ehci core layer don't work correctly. Do
> somebody use EHCI CORE layer for Mass storage and it was ok? 
>   
Can you report exactly your problem? What happen?
> Thank you.
>   
Michael

[U-Boot] USB EHCI driver

[FrancescoVT]

Hi,

this is the report of my problem.
I have initialized the SOC FSL EHCI controller, and  I typed usb start from
u-boot console.
I can see controller and mass storage, but mass storage doesn't seem to be
correctly configurated.
Can you explain to me what I must expect?

Thank you very much,
Francesco.
 
EHCI SOC FSL: USB Init....Completed!
Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... New Device 0
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0
length 0x8
req=6 (0x6), type=128 (0x80), value=256, index=0
USB_DT_DEVICE request
set address 1
usb_control_msg: request: 0x5, requesttype: 0x0, value 0x1 index 0x0 length
0x0
req=5 (0x5), type=0 (0x0), value=1, index=0
USB_REQ_SET_ADDRESS
Len is 0
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0
length 0x12
req=6 (0x6), type=128 (0x80), value=256, index=0
USB_DT_DEVICE request
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 index 0x0
length 0x8
req=6 (0x6), type=128 (0x80), value=512, index=0
USB_DT_CONFIG config
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 index 0x0
length 0x19
req=6 (0x6), type=128 (0x80), value=512, index=0
USB_DT_CONFIG config
get_conf_no 0 Result 25, wLength 25
if 0, ep 0
##EP epmaxpacketin[1] = 2048
set configuration 1
usb_control_msg: request: 0x9, requesttype: 0x0, value 0x1 index 0x0 length
0x0
req=9 (0x9), type=0 (0x0), value=1, index=0
USB_REQ_SET_CONFIGURATION
Len is 0
new device strings: Mfr=1, Product=2, SerialNumber=0
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x300 index 0x0
length 0xFF
req=6 (0x6), type=128 (0x80), value=768, index=0
USB_DT_STRING config
USB device number 1 default language ID 0x1
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x301 index 0x1
length 0xFF
req=6 (0x6), type=128 (0x80), value=769, index=1
USB_DT_STRING config
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x302 index 0x1
length 0xFF
req=6 (0x6), type=128 (0x80), value=770, index=1
USB_DT_STRING config
Manufacturer u-boot
Product      EHCI Host Controller
SerialNumber 
usb_control_msg: request: 0x6, requesttype: 0xA0, value 0x2900 index 0x0
length 0x4
req=6 (0x6), type=160 (0xa0), value=10496, index=0
USB_DT_HUB config
usb_control_msg: request: 0x6, requesttype: 0xA0, value 0x2900 index 0x0
length 0x8
req=6 (0x6), type=160 (0xa0), value=10496, index=0
USB_DT_HUB config
usb_control_msg: request: 0x0, requesttype: 0xA0, value 0x0 index 0x0 length
0x4
req=0 (0x0), type=160 (0xa0), value=0, index=0
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x8 index 0x1 length
0x0
req=3 (0x3), type=35 (0x23), value=8, index=1
Len is 0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length
0x4
req=0 (0x0), type=163 (0xa3), value=0, index=1
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length
0x4
req=0 (0x0), type=163 (0xa3), value=0, index=1
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x10 index 0x1
length 0x0
req=1 (0x1), type=35 (0x23), value=16, index=1
Len is 0
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x4 index 0x1 length
0x0
req=3 (0x3), type=35 (0x23), value=4, index=1
Len is 0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length
0x4
req=0 (0x0), type=163 (0xa3), value=0, index=1
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x14 index 0x1
length 0x0
req=1 (0x1), type=35 (0x23), value=20, index=1
unknown feature 14
requesttype=23, request=1, value=14, index=1, length=0
New Device 1
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0
length 0x8
dev=1ffecc58, pipe=80000080, buffer=1ffecd5c, length=8, req=1ffeb1fc
req=6 (0x6), type=128 (0x80), value=256 (0x100), index=0
EHCI fail timeout STD_ASS reset

      USB device not responding, giving up (status=80000000)
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x1 index 0x1 length
0x0
req=1 (0x1), type=35 (0x23), value=1, index=1
Len is 0
2 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found



Michael Trimarchi-2 wrote:
> 
> Hi,
> 
> FrancescoVT wrote:
>> Hi,
>>
>> I'm developing an USB EHCI driver for ADS5121e. Now , I completed
>> initialization sequence for my SOC EHCI Controller. My scope is to use
>> with
>> mass storage, but I think that ehci core layer don't work correctly. Do
>> somebody use EHCI CORE layer for Mass storage and it was ok? 
>>   
> Can you report exactly your problem? What happen?
>> Thank you.
>>   
> Michael
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
> 
> 

-- 
View this message in context: http://www.nabble.com/USB-EHCI-driver-tp22598488p22599570.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

[U-Boot] USB EHCI driver

[Gupta Maneesh-B18878]

Which SOC you are trying to use? I had faced some more issues while
porting the USB core layer related to descriptors also.

Regards
Maneesh
 

> -----Original Message-----
> From: u-boot-bounces at lists.denx.de 
> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of FrancescoVT
> Sent: Thursday, March 19, 2009 6:27 PM
> To: u-boot at lists.denx.de
> Subject: Re: [U-Boot] USB EHCI driver
> 
> 
> Hi,
> 
> this is the report of my problem.
> I have initialized the SOC FSL EHCI controller, and  I typed 
> usb start from u-boot console.
> I can see controller and mass storage, but mass storage 
> doesn't seem to be correctly configurated.
> Can you explain to me what I must expect?
> 
> Thank you very much,
> Francesco.
>  
> EHCI SOC FSL: USB Init....Completed!
> Register 10011 NbrPorts 1
> USB EHCI 1.00
> scanning bus for devices... New Device 0
> usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 
> index 0x0 length 0x8
> req=6 (0x6), type=128 (0x80), value=256, index=0 
> USB_DT_DEVICE request set address 1
> usb_control_msg: request: 0x5, requesttype: 0x0, value 0x1 
> index 0x0 length 0x0
> req=5 (0x5), type=0 (0x0), value=1, index=0 
> USB_REQ_SET_ADDRESS Len is 0
> usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 
> index 0x0 length 0x12
> req=6 (0x6), type=128 (0x80), value=256, index=0 USB_DT_DEVICE request
> usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 
> index 0x0 length 0x8
> req=6 (0x6), type=128 (0x80), value=512, index=0 USB_DT_CONFIG config
> usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 
> index 0x0 length 0x19
> req=6 (0x6), type=128 (0x80), value=512, index=0 
> USB_DT_CONFIG config get_conf_no 0 Result 25, wLength 25 if 
> 0, ep 0 ##EP epmaxpacketin[1] = 2048 set configuration 1
> usb_control_msg: request: 0x9, requesttype: 0x0, value 0x1 
> index 0x0 length 0x0
> req=9 (0x9), type=0 (0x0), value=1, index=0 
> USB_REQ_SET_CONFIGURATION Len is 0 new device strings: Mfr=1, 
> Product=2, SerialNumber=0
> usb_control_msg: request: 0x6, requesttype: 0x80, value 0x300 
> index 0x0 length 0xFF
> req=6 (0x6), type=128 (0x80), value=768, index=0 
> USB_DT_STRING config USB device number 1 default language ID 0x1
> usb_control_msg: request: 0x6, requesttype: 0x80, value 0x301 
> index 0x1 length 0xFF
> req=6 (0x6), type=128 (0x80), value=769, index=1 USB_DT_STRING config
> usb_control_msg: request: 0x6, requesttype: 0x80, value 0x302 
> index 0x1 length 0xFF
> req=6 (0x6), type=128 (0x80), value=770, index=1 
> USB_DT_STRING config Manufacturer u-boot
> Product      EHCI Host Controller
> SerialNumber
> usb_control_msg: request: 0x6, requesttype: 0xA0, value 
> 0x2900 index 0x0 length 0x4
> req=6 (0x6), type=160 (0xa0), value=10496, index=0 USB_DT_HUB config
> usb_control_msg: request: 0x6, requesttype: 0xA0, value 
> 0x2900 index 0x0 length 0x8
> req=6 (0x6), type=160 (0xa0), value=10496, index=0 USB_DT_HUB config
> usb_control_msg: request: 0x0, requesttype: 0xA0, value 0x0 
> index 0x0 length
> 0x4
> req=0 (0x0), type=160 (0xa0), value=0, index=0
> usb_control_msg: request: 0x3, requesttype: 0x23, value 0x8 
> index 0x1 length 0x0
> req=3 (0x3), type=35 (0x23), value=8, index=1 Len is 0
> usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 
> index 0x1 length
> 0x4
> req=0 (0x0), type=163 (0xa3), value=0, index=1
> usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 
> index 0x1 length
> 0x4
> req=0 (0x0), type=163 (0xa3), value=0, index=1
> usb_control_msg: request: 0x1, requesttype: 0x23, value 0x10 
> index 0x1 length 0x0
> req=1 (0x1), type=35 (0x23), value=16, index=1 Len is 0
> usb_control_msg: request: 0x3, requesttype: 0x23, value 0x4 
> index 0x1 length 0x0
> req=3 (0x3), type=35 (0x23), value=4, index=1 Len is 0
> usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 
> index 0x1 length
> 0x4
> req=0 (0x0), type=163 (0xa3), value=0, index=1
> usb_control_msg: request: 0x1, requesttype: 0x23, value 0x14 
> index 0x1 length 0x0
> req=1 (0x1), type=35 (0x23), value=20, index=1 unknown 
> feature 14 requesttype=23, request=1, value=14, index=1, 
> length=0 New Device 1
> usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 
> index 0x0 length 0x8 dev=1ffecc58, pipe=80000080, 
> buffer=1ffecd5c, length=8, req=1ffeb1fc
> req=6 (0x6), type=128 (0x80), value=256 (0x100), index=0 EHCI 
> fail timeout STD_ASS reset
> 
>       USB device not responding, giving up (status=80000000)
> usb_control_msg: request: 0x1, requesttype: 0x23, value 0x1 
> index 0x1 length 0x0
> req=1 (0x1), type=35 (0x23), value=1, index=1 Len is 0
> 2 USB Device(s) found
>        scanning bus for storage devices... 0 Storage Device(s) found
> 
> 
> 
> Michael Trimarchi-2 wrote:
> > 
> > Hi,
> > 
> > FrancescoVT wrote:
> >> Hi,
> >>
> >> I'm developing an USB EHCI driver for ADS5121e. Now , I completed 
> >> initialization sequence for my SOC EHCI Controller. My scope is to 
> >> use with mass storage, but I think that ehci core layer don't work 
> >> correctly. Do somebody use EHCI CORE layer for Mass storage and it 
> >> was ok?
> >>   
> > Can you report exactly your problem? What happen?
> >> Thank you.
> >>   
> > Michael
> > _______________________________________________
> > U-Boot mailing list
> > U-Boot at lists.denx.de
> > http://lists.denx.de/mailman/listinfo/u-boot
> > 
> > 
> 
> --
> View this message in context: 
> http://www.nabble.com/USB-EHCI-driver-tp22598488p22599570.html
> Sent from the Uboot - Users mailing list archive at Nabble.com.
> 
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
> 
> 

[U-Boot] USB EHCI driver

[FrancescoVT]

I have written an initialization sequence for Freescale MPC5121e. This CPU
contain an OTG and DR module with UTMI+ phy. I tested Linux USB driver for
this controller and it works. Infact I analyzed what Linux driver code did
and I applied it to my code in u-boot.


Gupta Maneesh-B18878 wrote:
> 
> Which SOC you are trying to use? I had faced some more issues while
> porting the USB core layer related to descriptors also.
> 
> Regards
> Maneesh
>  
> 
>> -----Original Message-----
>> From: u-boot-bounces at lists.denx.de 
>> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of FrancescoVT
>> Sent: Thursday, March 19, 2009 6:27 PM
>> To: u-boot at lists.denx.de
>> Subject: Re: [U-Boot] USB EHCI driver
>> 
>> 
>> Hi,
>> 
>> this is the report of my problem.
>> I have initialized the SOC FSL EHCI controller, and  I typed 
>> usb start from u-boot console.
>> I can see controller and mass storage, but mass storage 
>> doesn't seem to be correctly configurated.
>> Can you explain to me what I must expect?
>> 
>> Thank you very much,
>> Francesco.
>>  
>> EHCI SOC FSL: USB Init....Completed!
>> Register 10011 NbrPorts 1
>> USB EHCI 1.00
>> scanning bus for devices... New Device 0
>> usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 
>> index 0x0 length 0x8
>> req=6 (0x6), type=128 (0x80), value=256, index=0 
>> USB_DT_DEVICE request set address 1
>> usb_control_msg: request: 0x5, requesttype: 0x0, value 0x1 
>> index 0x0 length 0x0
>> req=5 (0x5), type=0 (0x0), value=1, index=0 
>> USB_REQ_SET_ADDRESS Len is 0
>> usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 
>> index 0x0 length 0x12
>> req=6 (0x6), type=128 (0x80), value=256, index=0 USB_DT_DEVICE request
>> usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 
>> index 0x0 length 0x8
>> req=6 (0x6), type=128 (0x80), value=512, index=0 USB_DT_CONFIG config
>> usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 
>> index 0x0 length 0x19
>> req=6 (0x6), type=128 (0x80), value=512, index=0 
>> USB_DT_CONFIG config get_conf_no 0 Result 25, wLength 25 if 
>> 0, ep 0 ##EP epmaxpacketin[1] = 2048 set configuration 1
>> usb_control_msg: request: 0x9, requesttype: 0x0, value 0x1 
>> index 0x0 length 0x0
>> req=9 (0x9), type=0 (0x0), value=1, index=0 
>> USB_REQ_SET_CONFIGURATION Len is 0 new device strings: Mfr=1, 
>> Product=2, SerialNumber=0
>> usb_control_msg: request: 0x6, requesttype: 0x80, value 0x300 
>> index 0x0 length 0xFF
>> req=6 (0x6), type=128 (0x80), value=768, index=0 
>> USB_DT_STRING config USB device number 1 default language ID 0x1
>> usb_control_msg: request: 0x6, requesttype: 0x80, value 0x301 
>> index 0x1 length 0xFF
>> req=6 (0x6), type=128 (0x80), value=769, index=1 USB_DT_STRING config
>> usb_control_msg: request: 0x6, requesttype: 0x80, value 0x302 
>> index 0x1 length 0xFF
>> req=6 (0x6), type=128 (0x80), value=770, index=1 
>> USB_DT_STRING config Manufacturer u-boot
>> Product      EHCI Host Controller
>> SerialNumber
>> usb_control_msg: request: 0x6, requesttype: 0xA0, value 
>> 0x2900 index 0x0 length 0x4
>> req=6 (0x6), type=160 (0xa0), value=10496, index=0 USB_DT_HUB config
>> usb_control_msg: request: 0x6, requesttype: 0xA0, value 
>> 0x2900 index 0x0 length 0x8
>> req=6 (0x6), type=160 (0xa0), value=10496, index=0 USB_DT_HUB config
>> usb_control_msg: request: 0x0, requesttype: 0xA0, value 0x0 
>> index 0x0 length
>> 0x4
>> req=0 (0x0), type=160 (0xa0), value=0, index=0
>> usb_control_msg: request: 0x3, requesttype: 0x23, value 0x8 
>> index 0x1 length 0x0
>> req=3 (0x3), type=35 (0x23), value=8, index=1 Len is 0
>> usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 
>> index 0x1 length
>> 0x4
>> req=0 (0x0), type=163 (0xa3), value=0, index=1
>> usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 
>> index 0x1 length
>> 0x4
>> req=0 (0x0), type=163 (0xa3), value=0, index=1
>> usb_control_msg: request: 0x1, requesttype: 0x23, value 0x10 
>> index 0x1 length 0x0
>> req=1 (0x1), type=35 (0x23), value=16, index=1 Len is 0
>> usb_control_msg: request: 0x3, requesttype: 0x23, value 0x4 
>> index 0x1 length 0x0
>> req=3 (0x3), type=35 (0x23), value=4, index=1 Len is 0
>> usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 
>> index 0x1 length
>> 0x4
>> req=0 (0x0), type=163 (0xa3), value=0, index=1
>> usb_control_msg: request: 0x1, requesttype: 0x23, value 0x14 
>> index 0x1 length 0x0
>> req=1 (0x1), type=35 (0x23), value=20, index=1 unknown 
>> feature 14 requesttype=23, request=1, value=14, index=1, 
>> length=0 New Device 1
>> usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 
>> index 0x0 length 0x8 dev=1ffecc58, pipe=80000080, 
>> buffer=1ffecd5c, length=8, req=1ffeb1fc
>> req=6 (0x6), type=128 (0x80), value=256 (0x100), index=0 EHCI 
>> fail timeout STD_ASS reset
>> 
>>       USB device not responding, giving up (status=80000000)
>> usb_control_msg: request: 0x1, requesttype: 0x23, value 0x1 
>> index 0x1 length 0x0
>> req=1 (0x1), type=35 (0x23), value=1, index=1 Len is 0
>> 2 USB Device(s) found
>>        scanning bus for storage devices... 0 Storage Device(s) found
>> 
>> 
>> 
>> Michael Trimarchi-2 wrote:
>> > 
>> > Hi,
>> > 
>> > FrancescoVT wrote:
>> >> Hi,
>> >>
>> >> I'm developing an USB EHCI driver for ADS5121e. Now , I completed 
>> >> initialization sequence for my SOC EHCI Controller. My scope is to 
>> >> use with mass storage, but I think that ehci core layer don't work 
>> >> correctly. Do somebody use EHCI CORE layer for Mass storage and it 
>> >> was ok?
>> >>   
>> > Can you report exactly your problem? What happen?
>> >> Thank you.
>> >>   
>> > Michael
>> > _______________________________________________
>> > U-Boot mailing list
>> > U-Boot at lists.denx.de
>> > http://lists.denx.de/mailman/listinfo/u-boot
>> > 
>> > 
>> 
>> --
>> View this message in context: 
>> http://www.nabble.com/USB-EHCI-driver-tp22598488p22599570.html
>> Sent from the Uboot - Users mailing list archive at Nabble.com.
>> 
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
>> 
>> 
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
> 
> 

-- 
View this message in context: http://www.nabble.com/USB-EHCI-driver-tp22598488p22600620.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

[U-Boot] USB EHCI driver

[Gupta Maneesh-B18878]

Have you faced any issues w.r.t accessing the root hub Device
Descriptors?

Regards
Maneesh 

> -----Original Message-----
> From: u-boot-bounces at lists.denx.de 
> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of FrancescoVT
> Sent: Thursday, March 19, 2009 7:20 PM
> To: u-boot at lists.denx.de
> Subject: Re: [U-Boot] USB EHCI driver
> 
> 
> I have written an initialization sequence for Freescale 
> MPC5121e. This CPU contain an OTG and DR module with UTMI+ 
> phy. I tested Linux USB driver for this controller and it 
> works. Infact I analyzed what Linux driver code did and I 
> applied it to my code in u-boot.
> 
> 
> Gupta Maneesh-B18878 wrote:
> > 
> > Which SOC you are trying to use? I had faced some more issues while 
> > porting the USB core layer related to descriptors also.
> > 
> > Regards
> > Maneesh
> >  
> > 
> >> -----Original Message-----
> >> From: u-boot-bounces at lists.denx.de
> >> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of FrancescoVT
> >> Sent: Thursday, March 19, 2009 6:27 PM
> >> To: u-boot at lists.denx.de
> >> Subject: Re: [U-Boot] USB EHCI driver
> >> 
> >> 
> >> Hi,
> >> 
> >> this is the report of my problem.
> >> I have initialized the SOC FSL EHCI controller, and  I typed usb 
> >> start from u-boot console.
> >> I can see controller and mass storage, but mass storage 
> doesn't seem 
> >> to be correctly configurated.
> >> Can you explain to me what I must expect?
> >> 
> >> Thank you very much,
> >> Francesco.
> >>  
> >> EHCI SOC FSL: USB Init....Completed!
> >> Register 10011 NbrPorts 1
> >> USB EHCI 1.00
> >> scanning bus for devices... New Device 0
> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
> 0x100 index 
> >> 0x0 length 0x8
> >> req=6 (0x6), type=128 (0x80), value=256, index=0 USB_DT_DEVICE 
> >> request set address 1
> >> usb_control_msg: request: 0x5, requesttype: 0x0, value 0x1 
> index 0x0 
> >> length 0x0
> >> req=5 (0x5), type=0 (0x0), value=1, index=0 
> USB_REQ_SET_ADDRESS Len 
> >> is 0
> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
> 0x100 index 
> >> 0x0 length 0x12
> >> req=6 (0x6), type=128 (0x80), value=256, index=0 USB_DT_DEVICE 
> >> request
> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
> 0x200 index 
> >> 0x0 length 0x8
> >> req=6 (0x6), type=128 (0x80), value=512, index=0 
> USB_DT_CONFIG config
> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
> 0x200 index 
> >> 0x0 length 0x19
> >> req=6 (0x6), type=128 (0x80), value=512, index=0 
> USB_DT_CONFIG config 
> >> get_conf_no 0 Result 25, wLength 25 if 0, ep 0 ##EP 
> epmaxpacketin[1] 
> >> = 2048 set configuration 1
> >> usb_control_msg: request: 0x9, requesttype: 0x0, value 0x1 
> index 0x0 
> >> length 0x0
> >> req=9 (0x9), type=0 (0x0), value=1, index=0 
> USB_REQ_SET_CONFIGURATION 
> >> Len is 0 new device strings: Mfr=1, Product=2, SerialNumber=0
> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
> 0x300 index 
> >> 0x0 length 0xFF
> >> req=6 (0x6), type=128 (0x80), value=768, index=0 
> USB_DT_STRING config 
> >> USB device number 1 default language ID 0x1
> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
> 0x301 index 
> >> 0x1 length 0xFF
> >> req=6 (0x6), type=128 (0x80), value=769, index=1 
> USB_DT_STRING config
> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
> 0x302 index 
> >> 0x1 length 0xFF
> >> req=6 (0x6), type=128 (0x80), value=770, index=1 
> USB_DT_STRING config 
> >> Manufacturer u-boot
> >> Product      EHCI Host Controller
> >> SerialNumber
> >> usb_control_msg: request: 0x6, requesttype: 0xA0, value 
> 0x2900 index 
> >> 0x0 length 0x4
> >> req=6 (0x6), type=160 (0xa0), value=10496, index=0 
> USB_DT_HUB config
> >> usb_control_msg: request: 0x6, requesttype: 0xA0, value 
> 0x2900 index 
> >> 0x0 length 0x8
> >> req=6 (0x6), type=160 (0xa0), value=10496, index=0 
> USB_DT_HUB config
> >> usb_control_msg: request: 0x0, requesttype: 0xA0, value 
> 0x0 index 0x0 
> >> length
> >> 0x4
> >> req=0 (0x0), type=160 (0xa0), value=0, index=0
> >> usb_control_msg: request: 0x3, requesttype: 0x23, value 
> 0x8 index 0x1 
> >> length 0x0
> >> req=3 (0x3), type=35 (0x23), value=8, index=1 Len is 0
> >> usb_control_msg: request: 0x0, requesttype: 0xA3, value 
> 0x0 index 0x1 
> >> length
> >> 0x4
> >> req=0 (0x0), type=163 (0xa3), value=0, index=1
> >> usb_control_msg: request: 0x0, requesttype: 0xA3, value 
> 0x0 index 0x1 
> >> length
> >> 0x4
> >> req=0 (0x0), type=163 (0xa3), value=0, index=1
> >> usb_control_msg: request: 0x1, requesttype: 0x23, value 0x10 index 
> >> 0x1 length 0x0
> >> req=1 (0x1), type=35 (0x23), value=16, index=1 Len is 0
> >> usb_control_msg: request: 0x3, requesttype: 0x23, value 
> 0x4 index 0x1 
> >> length 0x0
> >> req=3 (0x3), type=35 (0x23), value=4, index=1 Len is 0
> >> usb_control_msg: request: 0x0, requesttype: 0xA3, value 
> 0x0 index 0x1 
> >> length
> >> 0x4
> >> req=0 (0x0), type=163 (0xa3), value=0, index=1
> >> usb_control_msg: request: 0x1, requesttype: 0x23, value 0x14 index 
> >> 0x1 length 0x0
> >> req=1 (0x1), type=35 (0x23), value=20, index=1 unknown feature 14 
> >> requesttype=23, request=1, value=14, index=1, length=0 New Device 1
> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
> 0x100 index 
> >> 0x0 length 0x8 dev=1ffecc58, pipe=80000080, buffer=1ffecd5c, 
> >> length=8, req=1ffeb1fc
> >> req=6 (0x6), type=128 (0x80), value=256 (0x100), index=0 EHCI fail 
> >> timeout STD_ASS reset
> >> 
> >>       USB device not responding, giving up (status=80000000)
> >> usb_control_msg: request: 0x1, requesttype: 0x23, value 
> 0x1 index 0x1 
> >> length 0x0
> >> req=1 (0x1), type=35 (0x23), value=1, index=1 Len is 0
> >> 2 USB Device(s) found
> >>        scanning bus for storage devices... 0 Storage 
> Device(s) found
> >> 
> >> 
> >> 
> >> Michael Trimarchi-2 wrote:
> >> > 
> >> > Hi,
> >> > 
> >> > FrancescoVT wrote:
> >> >> Hi,
> >> >>
> >> >> I'm developing an USB EHCI driver for ADS5121e. Now , I 
> completed 
> >> >> initialization sequence for my SOC EHCI Controller. My 
> scope is to 
> >> >> use with mass storage, but I think that ehci core layer 
> don't work 
> >> >> correctly. Do somebody use EHCI CORE layer for Mass 
> storage and it 
> >> >> was ok?
> >> >>   
> >> > Can you report exactly your problem? What happen?
> >> >> Thank you.
> >> >>   
> >> > Michael
> >> > _______________________________________________
> >> > U-Boot mailing list
> >> > U-Boot at lists.denx.de
> >> > http://lists.denx.de/mailman/listinfo/u-boot
> >> > 
> >> > 
> >> 
> >> --
> >> View this message in context: 
> >> http://www.nabble.com/USB-EHCI-driver-tp22598488p22599570.html
> >> Sent from the Uboot - Users mailing list archive at Nabble.com.
> >> 
> >> _______________________________________________
> >> U-Boot mailing list
> >> U-Boot at lists.denx.de
> >> http://lists.denx.de/mailman/listinfo/u-boot
> >> 
> >> 
> > _______________________________________________
> > U-Boot mailing list
> > U-Boot at lists.denx.de
> > http://lists.denx.de/mailman/listinfo/u-boot
> > 
> > 
> 
> --
> View this message in context: 
> http://www.nabble.com/USB-EHCI-driver-tp22598488p22600620.html
> Sent from the Uboot - Users mailing list archive at Nabble.com.
> 
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
> 
> 

[U-Boot] USB EHCI driver

[FrancescoVT]

No.
I didn't touch the EHCI core layer. I expected that it work.
What do you think about?

THANKS.

Regars
Francesco


Gupta Maneesh-B18878 wrote:
> 
> Have you faced any issues w.r.t accessing the root hub Device
> Descriptors?
> 
> Regards
> Maneesh 
> 
>> -----Original Message-----
>> From: u-boot-bounces at lists.denx.de 
>> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of FrancescoVT
>> Sent: Thursday, March 19, 2009 7:20 PM
>> To: u-boot at lists.denx.de
>> Subject: Re: [U-Boot] USB EHCI driver
>> 
>> 
>> I have written an initialization sequence for Freescale 
>> MPC5121e. This CPU contain an OTG and DR module with UTMI+ 
>> phy. I tested Linux USB driver for this controller and it 
>> works. Infact I analyzed what Linux driver code did and I 
>> applied it to my code in u-boot.
>> 
>> 
>> Gupta Maneesh-B18878 wrote:
>> > 
>> > Which SOC you are trying to use? I had faced some more issues while 
>> > porting the USB core layer related to descriptors also.
>> > 
>> > Regards
>> > Maneesh
>> >  
>> > 
>> >> -----Original Message-----
>> >> From: u-boot-bounces at lists.denx.de
>> >> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of FrancescoVT
>> >> Sent: Thursday, March 19, 2009 6:27 PM
>> >> To: u-boot at lists.denx.de
>> >> Subject: Re: [U-Boot] USB EHCI driver
>> >> 
>> >> 
>> >> Hi,
>> >> 
>> >> this is the report of my problem.
>> >> I have initialized the SOC FSL EHCI controller, and  I typed usb 
>> >> start from u-boot console.
>> >> I can see controller and mass storage, but mass storage 
>> doesn't seem 
>> >> to be correctly configurated.
>> >> Can you explain to me what I must expect?
>> >> 
>> >> Thank you very much,
>> >> Francesco.
>> >>  
>> >> EHCI SOC FSL: USB Init....Completed!
>> >> Register 10011 NbrPorts 1
>> >> USB EHCI 1.00
>> >> scanning bus for devices... New Device 0
>> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
>> 0x100 index 
>> >> 0x0 length 0x8
>> >> req=6 (0x6), type=128 (0x80), value=256, index=0 USB_DT_DEVICE 
>> >> request set address 1
>> >> usb_control_msg: request: 0x5, requesttype: 0x0, value 0x1 
>> index 0x0 
>> >> length 0x0
>> >> req=5 (0x5), type=0 (0x0), value=1, index=0 
>> USB_REQ_SET_ADDRESS Len 
>> >> is 0
>> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
>> 0x100 index 
>> >> 0x0 length 0x12
>> >> req=6 (0x6), type=128 (0x80), value=256, index=0 USB_DT_DEVICE 
>> >> request
>> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
>> 0x200 index 
>> >> 0x0 length 0x8
>> >> req=6 (0x6), type=128 (0x80), value=512, index=0 
>> USB_DT_CONFIG config
>> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
>> 0x200 index 
>> >> 0x0 length 0x19
>> >> req=6 (0x6), type=128 (0x80), value=512, index=0 
>> USB_DT_CONFIG config 
>> >> get_conf_no 0 Result 25, wLength 25 if 0, ep 0 ##EP 
>> epmaxpacketin[1] 
>> >> = 2048 set configuration 1
>> >> usb_control_msg: request: 0x9, requesttype: 0x0, value 0x1 
>> index 0x0 
>> >> length 0x0
>> >> req=9 (0x9), type=0 (0x0), value=1, index=0 
>> USB_REQ_SET_CONFIGURATION 
>> >> Len is 0 new device strings: Mfr=1, Product=2, SerialNumber=0
>> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
>> 0x300 index 
>> >> 0x0 length 0xFF
>> >> req=6 (0x6), type=128 (0x80), value=768, index=0 
>> USB_DT_STRING config 
>> >> USB device number 1 default language ID 0x1
>> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
>> 0x301 index 
>> >> 0x1 length 0xFF
>> >> req=6 (0x6), type=128 (0x80), value=769, index=1 
>> USB_DT_STRING config
>> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
>> 0x302 index 
>> >> 0x1 length 0xFF
>> >> req=6 (0x6), type=128 (0x80), value=770, index=1 
>> USB_DT_STRING config 
>> >> Manufacturer u-boot
>> >> Product      EHCI Host Controller
>> >> SerialNumber
>> >> usb_control_msg: request: 0x6, requesttype: 0xA0, value 
>> 0x2900 index 
>> >> 0x0 length 0x4
>> >> req=6 (0x6), type=160 (0xa0), value=10496, index=0 
>> USB_DT_HUB config
>> >> usb_control_msg: request: 0x6, requesttype: 0xA0, value 
>> 0x2900 index 
>> >> 0x0 length 0x8
>> >> req=6 (0x6), type=160 (0xa0), value=10496, index=0 
>> USB_DT_HUB config
>> >> usb_control_msg: request: 0x0, requesttype: 0xA0, value 
>> 0x0 index 0x0 
>> >> length
>> >> 0x4
>> >> req=0 (0x0), type=160 (0xa0), value=0, index=0
>> >> usb_control_msg: request: 0x3, requesttype: 0x23, value 
>> 0x8 index 0x1 
>> >> length 0x0
>> >> req=3 (0x3), type=35 (0x23), value=8, index=1 Len is 0
>> >> usb_control_msg: request: 0x0, requesttype: 0xA3, value 
>> 0x0 index 0x1 
>> >> length
>> >> 0x4
>> >> req=0 (0x0), type=163 (0xa3), value=0, index=1
>> >> usb_control_msg: request: 0x0, requesttype: 0xA3, value 
>> 0x0 index 0x1 
>> >> length
>> >> 0x4
>> >> req=0 (0x0), type=163 (0xa3), value=0, index=1
>> >> usb_control_msg: request: 0x1, requesttype: 0x23, value 0x10 index 
>> >> 0x1 length 0x0
>> >> req=1 (0x1), type=35 (0x23), value=16, index=1 Len is 0
>> >> usb_control_msg: request: 0x3, requesttype: 0x23, value 
>> 0x4 index 0x1 
>> >> length 0x0
>> >> req=3 (0x3), type=35 (0x23), value=4, index=1 Len is 0
>> >> usb_control_msg: request: 0x0, requesttype: 0xA3, value 
>> 0x0 index 0x1 
>> >> length
>> >> 0x4
>> >> req=0 (0x0), type=163 (0xa3), value=0, index=1
>> >> usb_control_msg: request: 0x1, requesttype: 0x23, value 0x14 index 
>> >> 0x1 length 0x0
>> >> req=1 (0x1), type=35 (0x23), value=20, index=1 unknown feature 14 
>> >> requesttype=23, request=1, value=14, index=1, length=0 New Device 1
>> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
>> 0x100 index 
>> >> 0x0 length 0x8 dev=1ffecc58, pipe=80000080, buffer=1ffecd5c, 
>> >> length=8, req=1ffeb1fc
>> >> req=6 (0x6), type=128 (0x80), value=256 (0x100), index=0 EHCI fail 
>> >> timeout STD_ASS reset
>> >> 
>> >>       USB device not responding, giving up (status=80000000)
>> >> usb_control_msg: request: 0x1, requesttype: 0x23, value 
>> 0x1 index 0x1 
>> >> length 0x0
>> >> req=1 (0x1), type=35 (0x23), value=1, index=1 Len is 0
>> >> 2 USB Device(s) found
>> >>        scanning bus for storage devices... 0 Storage 
>> Device(s) found
>> >> 
>> >> 
>> >> 
>> >> Michael Trimarchi-2 wrote:
>> >> > 
>> >> > Hi,
>> >> > 
>> >> > FrancescoVT wrote:
>> >> >> Hi,
>> >> >>
>> >> >> I'm developing an USB EHCI driver for ADS5121e. Now , I 
>> completed 
>> >> >> initialization sequence for my SOC EHCI Controller. My 
>> scope is to 
>> >> >> use with mass storage, but I think that ehci core layer 
>> don't work 
>> >> >> correctly. Do somebody use EHCI CORE layer for Mass 
>> storage and it 
>> >> >> was ok?
>> >> >>   
>> >> > Can you report exactly your problem? What happen?
>> >> >> Thank you.
>> >> >>   
>> >> > Michael
>> >> > _______________________________________________
>> >> > U-Boot mailing list
>> >> > U-Boot at lists.denx.de
>> >> > http://lists.denx.de/mailman/listinfo/u-boot
>> >> > 
>> >> > 
>> >> 
>> >> --
>> >> View this message in context: 
>> >> http://www.nabble.com/USB-EHCI-driver-tp22598488p22599570.html
>> >> Sent from the Uboot - Users mailing list archive at Nabble.com.
>> >> 
>> >> _______________________________________________
>> >> U-Boot mailing list
>> >> U-Boot at lists.denx.de
>> >> http://lists.denx.de/mailman/listinfo/u-boot
>> >> 
>> >> 
>> > _______________________________________________
>> > U-Boot mailing list
>> > U-Boot at lists.denx.de
>> > http://lists.denx.de/mailman/listinfo/u-boot
>> > 
>> > 
>> 
>> --
>> View this message in context: 
>> http://www.nabble.com/USB-EHCI-driver-tp22598488p22600620.html
>> Sent from the Uboot - Users mailing list archive at Nabble.com.
>> 
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
>> 
>> 
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
> 
> 

-- 
View this message in context: http://www.nabble.com/USB-EHCI-driver-tp22598488p22602751.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

[U-Boot] USB EHCI driver

[FrancescoVT]

I have integrated last USB u-boot code (2009.03rc) into my code and now I get
this:

=> usb start
(Re)start USB...
USB:   
USB Init....Completed!

USB Init....Completed!
Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... New Device 0
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0
length 0x40
req=6 (0x6), type=128 (0x80), value=256, index=0
USB_DT_DEVICE request
set address 1
usb_control_msg: request: 0x5, requesttype: 0x0, value 0x1 index 0x0 length
0x0
req=5 (0x5), type=0 (0x0), value=1, index=0
USB_REQ_SET_ADDRESS
Len is 0
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0
length 0x12
req=6 (0x6), type=128 (0x80), value=256, index=0
USB_DT_DEVICE request
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 index 0x0
length 0x9
req=6 (0x6), type=128 (0x80), value=512, index=0
USB_DT_CONFIG config
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 index 0x0
length 0x19
req=6 (0x6), type=128 (0x80), value=512, index=0
USB_DT_CONFIG config
get_conf_no 0 Result 25, wLength 25
if 0, ep 0
##EP epmaxpacketin[1] = 2048
set configuration 1
usb_control_msg: request: 0x9, requesttype: 0x0, value 0x1 index 0x0 length
0x0
req=9 (0x9), type=0 (0x0), value=1, index=0
USB_REQ_SET_CONFIGURATION
Len is 0
new device strings: Mfr=1, Product=2, SerialNumber=0
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x300 index 0x0
length 0xFF
req=6 (0x6), type=128 (0x80), value=768, index=0
USB_DT_STRING config
USB device number 1 default language ID 0x1
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x301 index 0x1
length 0xFF
req=6 (0x6), type=128 (0x80), value=769, index=1
USB_DT_STRING config
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x302 index 0x1
length 0xFF
req=6 (0x6), type=128 (0x80), value=770, index=1
USB_DT_STRING config
Manufacturer u-boot
Product      EHCI Host Controller
SerialNumber 
usb_control_msg: request: 0x6, requesttype: 0xA0, value 0x2900 index 0x0
length 0x4
req=6 (0x6), type=160 (0xa0), value=10496, index=0
USB_DT_HUB config
usb_control_msg: request: 0x6, requesttype: 0xA0, value 0x2900 index 0x0
length 0x8
req=6 (0x6), type=160 (0xa0), value=10496, index=0
USB_DT_HUB config
usb_control_msg: request: 0x0, requesttype: 0xA0, value 0x0 index 0x0 length
0x4
req=0 (0x0), type=160 (0xa0), value=0, index=0
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x8 index 0x1 length
0x0
req=3 (0x3), type=35 (0x23), value=8, index=1
Len is 0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length
0x4
req=0 (0x0), type=163 (0xa3), value=0, index=1
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length
0x4
req=0 (0x0), type=163 (0xa3), value=0, index=1
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x10 index 0x1
length 0x0
req=1 (0x1), type=35 (0x23), value=16, index=1
Len is 0
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x4 index 0x1 length
0x0
req=3 (0x3), type=35 (0x23), value=4, index=1
Len is 0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length
0x4
req=0 (0x0), type=163 (0xa3), value=0, index=1
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x14 index 0x1
length 0x0
req=1 (0x1), type=35 (0x23), value=20, index=1
Len is 0
New Device 1
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0
length 0x40
dev=1ffebb08, pipe=88000083, buffer=1f9a671a, length=64, req=1ffea214
req=6 (0x6), type=128 (0x80), value=256 (0x100), index=0
EHCI fail timeout STD_ASS reset
usb_new_device: usb_get_descriptor() failed
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x1 index 0x1 length
0x0
req=1 (0x1), type=35 (0x23), value=1, index=1
Len is 0
2 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
=> 

Seem to fail usb_get_descriptor..


FrancescoVT wrote:
> 
> No.
> I didn't touch the EHCI core layer. I expected that it work.
> What do you think about?
> 
> THANKS.
> 
> Regars
> Francesco
> 
> 
> Gupta Maneesh-B18878 wrote:
>> 
>> Have you faced any issues w.r.t accessing the root hub Device
>> Descriptors?
>> 
>> Regards
>> Maneesh 
>> 
>>> -----Original Message-----
>>> From: u-boot-bounces at lists.denx.de 
>>> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of FrancescoVT
>>> Sent: Thursday, March 19, 2009 7:20 PM
>>> To: u-boot at lists.denx.de
>>> Subject: Re: [U-Boot] USB EHCI driver
>>> 
>>> 
>>> I have written an initialization sequence for Freescale 
>>> MPC5121e. This CPU contain an OTG and DR module with UTMI+ 
>>> phy. I tested Linux USB driver for this controller and it 
>>> works. Infact I analyzed what Linux driver code did and I 
>>> applied it to my code in u-boot.
>>> 
>>> 
>>> Gupta Maneesh-B18878 wrote:
>>> > 
>>> > Which SOC you are trying to use? I had faced some more issues while 
>>> > porting the USB core layer related to descriptors also.
>>> > 
>>> > Regards
>>> > Maneesh
>>> >  
>>> > 
>>> >> -----Original Message-----
>>> >> From: u-boot-bounces at lists.denx.de
>>> >> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of FrancescoVT
>>> >> Sent: Thursday, March 19, 2009 6:27 PM
>>> >> To: u-boot at lists.denx.de
>>> >> Subject: Re: [U-Boot] USB EHCI driver
>>> >> 
>>> >> 
>>> >> Hi,
>>> >> 
>>> >> this is the report of my problem.
>>> >> I have initialized the SOC FSL EHCI controller, and  I typed usb 
>>> >> start from u-boot console.
>>> >> I can see controller and mass storage, but mass storage 
>>> doesn't seem 
>>> >> to be correctly configurated.
>>> >> Can you explain to me what I must expect?
>>> >> 
>>> >> Thank you very much,
>>> >> Francesco.
>>> >>  
>>> >> EHCI SOC FSL: USB Init....Completed!
>>> >> Register 10011 NbrPorts 1
>>> >> USB EHCI 1.00
>>> >> scanning bus for devices... New Device 0
>>> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
>>> 0x100 index 
>>> >> 0x0 length 0x8
>>> >> req=6 (0x6), type=128 (0x80), value=256, index=0 USB_DT_DEVICE 
>>> >> request set address 1
>>> >> usb_control_msg: request: 0x5, requesttype: 0x0, value 0x1 
>>> index 0x0 
>>> >> length 0x0
>>> >> req=5 (0x5), type=0 (0x0), value=1, index=0 
>>> USB_REQ_SET_ADDRESS Len 
>>> >> is 0
>>> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
>>> 0x100 index 
>>> >> 0x0 length 0x12
>>> >> req=6 (0x6), type=128 (0x80), value=256, index=0 USB_DT_DEVICE 
>>> >> request
>>> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
>>> 0x200 index 
>>> >> 0x0 length 0x8
>>> >> req=6 (0x6), type=128 (0x80), value=512, index=0 
>>> USB_DT_CONFIG config
>>> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
>>> 0x200 index 
>>> >> 0x0 length 0x19
>>> >> req=6 (0x6), type=128 (0x80), value=512, index=0 
>>> USB_DT_CONFIG config 
>>> >> get_conf_no 0 Result 25, wLength 25 if 0, ep 0 ##EP 
>>> epmaxpacketin[1] 
>>> >> = 2048 set configuration 1
>>> >> usb_control_msg: request: 0x9, requesttype: 0x0, value 0x1 
>>> index 0x0 
>>> >> length 0x0
>>> >> req=9 (0x9), type=0 (0x0), value=1, index=0 
>>> USB_REQ_SET_CONFIGURATION 
>>> >> Len is 0 new device strings: Mfr=1, Product=2, SerialNumber=0
>>> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
>>> 0x300 index 
>>> >> 0x0 length 0xFF
>>> >> req=6 (0x6), type=128 (0x80), value=768, index=0 
>>> USB_DT_STRING config 
>>> >> USB device number 1 default language ID 0x1
>>> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
>>> 0x301 index 
>>> >> 0x1 length 0xFF
>>> >> req=6 (0x6), type=128 (0x80), value=769, index=1 
>>> USB_DT_STRING config
>>> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
>>> 0x302 index 
>>> >> 0x1 length 0xFF
>>> >> req=6 (0x6), type=128 (0x80), value=770, index=1 
>>> USB_DT_STRING config 
>>> >> Manufacturer u-boot
>>> >> Product      EHCI Host Controller
>>> >> SerialNumber
>>> >> usb_control_msg: request: 0x6, requesttype: 0xA0, value 
>>> 0x2900 index 
>>> >> 0x0 length 0x4
>>> >> req=6 (0x6), type=160 (0xa0), value=10496, index=0 
>>> USB_DT_HUB config
>>> >> usb_control_msg: request: 0x6, requesttype: 0xA0, value 
>>> 0x2900 index 
>>> >> 0x0 length 0x8
>>> >> req=6 (0x6), type=160 (0xa0), value=10496, index=0 
>>> USB_DT_HUB config
>>> >> usb_control_msg: request: 0x0, requesttype: 0xA0, value 
>>> 0x0 index 0x0 
>>> >> length
>>> >> 0x4
>>> >> req=0 (0x0), type=160 (0xa0), value=0, index=0
>>> >> usb_control_msg: request: 0x3, requesttype: 0x23, value 
>>> 0x8 index 0x1 
>>> >> length 0x0
>>> >> req=3 (0x3), type=35 (0x23), value=8, index=1 Len is 0
>>> >> usb_control_msg: request: 0x0, requesttype: 0xA3, value 
>>> 0x0 index 0x1 
>>> >> length
>>> >> 0x4
>>> >> req=0 (0x0), type=163 (0xa3), value=0, index=1
>>> >> usb_control_msg: request: 0x0, requesttype: 0xA3, value 
>>> 0x0 index 0x1 
>>> >> length
>>> >> 0x4
>>> >> req=0 (0x0), type=163 (0xa3), value=0, index=1
>>> >> usb_control_msg: request: 0x1, requesttype: 0x23, value 0x10 index 
>>> >> 0x1 length 0x0
>>> >> req=1 (0x1), type=35 (0x23), value=16, index=1 Len is 0
>>> >> usb_control_msg: request: 0x3, requesttype: 0x23, value 
>>> 0x4 index 0x1 
>>> >> length 0x0
>>> >> req=3 (0x3), type=35 (0x23), value=4, index=1 Len is 0
>>> >> usb_control_msg: request: 0x0, requesttype: 0xA3, value 
>>> 0x0 index 0x1 
>>> >> length
>>> >> 0x4
>>> >> req=0 (0x0), type=163 (0xa3), value=0, index=1
>>> >> usb_control_msg: request: 0x1, requesttype: 0x23, value 0x14 index 
>>> >> 0x1 length 0x0
>>> >> req=1 (0x1), type=35 (0x23), value=20, index=1 unknown feature 14 
>>> >> requesttype=23, request=1, value=14, index=1, length=0 New Device 1
>>> >> usb_control_msg: request: 0x6, requesttype: 0x80, value 
>>> 0x100 index 
>>> >> 0x0 length 0x8 dev=1ffecc58, pipe=80000080, buffer=1ffecd5c, 
>>> >> length=8, req=1ffeb1fc
>>> >> req=6 (0x6), type=128 (0x80), value=256 (0x100), index=0 EHCI fail 
>>> >> timeout STD_ASS reset
>>> >> 
>>> >>       USB device not responding, giving up (status=80000000)
>>> >> usb_control_msg: request: 0x1, requesttype: 0x23, value 
>>> 0x1 index 0x1 
>>> >> length 0x0
>>> >> req=1 (0x1), type=35 (0x23), value=1, index=1 Len is 0
>>> >> 2 USB Device(s) found
>>> >>        scanning bus for storage devices... 0 Storage 
>>> Device(s) found
>>> >> 
>>> >> 
>>> >> 
>>> >> Michael Trimarchi-2 wrote:
>>> >> > 
>>> >> > Hi,
>>> >> > 
>>> >> > FrancescoVT wrote:
>>> >> >> Hi,
>>> >> >>
>>> >> >> I'm developing an USB EHCI driver for ADS5121e. Now , I 
>>> completed 
>>> >> >> initialization sequence for my SOC EHCI Controller. My 
>>> scope is to 
>>> >> >> use with mass storage, but I think that ehci core layer 
>>> don't work 
>>> >> >> correctly. Do somebody use EHCI CORE layer for Mass 
>>> storage and it 
>>> >> >> was ok?
>>> >> >>   
>>> >> > Can you report exactly your problem? What happen?
>>> >> >> Thank you.
>>> >> >>   
>>> >> > Michael
>>> >> > _______________________________________________
>>> >> > U-Boot mailing list
>>> >> > U-Boot at lists.denx.de
>>> >> > http://lists.denx.de/mailman/listinfo/u-boot
>>> >> > 
>>> >> > 
>>> >> 
>>> >> --
>>> >> View this message in context: 
>>> >> http://www.nabble.com/USB-EHCI-driver-tp22598488p22599570.html
>>> >> Sent from the Uboot - Users mailing list archive at Nabble.com.
>>> >> 
>>> >> _______________________________________________
>>> >> U-Boot mailing list
>>> >> U-Boot at lists.denx.de
>>> >> http://lists.denx.de/mailman/listinfo/u-boot
>>> >> 
>>> >> 
>>> > _______________________________________________
>>> > U-Boot mailing list
>>> > U-Boot at lists.denx.de
>>> > http://lists.denx.de/mailman/listinfo/u-boot
>>> > 
>>> > 
>>> 
>>> --
>>> View this message in context: 
>>> http://www.nabble.com/USB-EHCI-driver-tp22598488p22600620.html
>>> Sent from the Uboot - Users mailing list archive at Nabble.com.
>>> 
>>> _______________________________________________
>>> U-Boot mailing list
>>> U-Boot at lists.denx.de
>>> http://lists.denx.de/mailman/listinfo/u-boot
>>> 
>>> 
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/USB-EHCI-driver-tp22598488p22605375.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

[U-Boot] USB EHCI driver

[Michael Trimarchi]

Hi,

FrancescoVT wrote:
> usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0
> length 0x40
> dev=1ffebb08, pipe=88000083, buffer=1f9a671a, length=64, req=1ffea214
> req=6 (0x6), type=128 (0x80), value=256 (0x100), index=0
> EHCI fail timeout STD_ASS reset
> usb_new_device: usb_get_descriptor() failed
>   
#define CONFIG_LEGACY_USB_INIT_SEQ

Michael

[U-Boot] USB EHCI driver

[Rendine Francesco]

Hi,

I've already tried that define, but nothing is changed...
What can I see in the USB driver to resolve issue?

Thanks.

-----Original Message-----
From: Michael Trimarchi [mailto:trimarchi at gandalf.sssup.it]
Sent: Fri 3/20/2009 9:36 AM
To: Rendine Francesco
Cc: u-boot at lists.denx.de
Subject: Re: [U-Boot] USB EHCI driver
 
Hi,

FrancescoVT wrote:
> usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0
> length 0x40
> dev=1ffebb08, pipe=88000083, buffer=1f9a671a, length=64, req=1ffea214
> req=6 (0x6), type=128 (0x80), value=256 (0x100), index=0
> EHCI fail timeout STD_ASS reset
> usb_new_device: usb_get_descriptor() failed
>   
#define CONFIG_LEGACY_USB_INIT_SEQ

Michael

[U-Boot] USB EHCI driver

[Michael Trimarchi]

Hi,

Rendine Francesco wrote:
>
> Hi,
>
> I've already tried that define, but nothing is changed...
> What can I see in the USB driver to resolve issue?
>
> Thanks.
>
> -----Original Message-----
> From: Michael Trimarchi [mailto:trimarchi at gandalf.sssup.it]
> Sent: Fri 3/20/2009 9:36 AM
> To: Rendine Francesco
> Cc: u-boot at lists.denx.de
> Subject: Re: [U-Boot] USB EHCI driver
>
> Hi,
>
> FrancescoVT wrote:
> > usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0
> > length 0x40
> > dev=1ffebb08, pipe=88000083, buffer=1f9a671a, length=64, req=1ffea214
> > req=6 (0x6), type=128 (0x80), value=256 (0x100), index=0
> > EHCI fail timeout STD_ASS reset
> > usb_new_device: usb_get_descriptor() failed
> >  
> #define CONFIG_LEGACY_USB_INIT_SEQ
>
> Michael
>
>
>
Sorry I can't help you without the board :( and now I don't have another 
board to test
to verify it. I'm working on android, and some migor issue.

Michael

[U-Boot] USB EHCI driver

[Gupta Maneesh-B18878]

Hi Francesco,

Could you make any progress?

Regards
Maneesh
 

> -----Original Message-----
> From: u-boot-bounces at lists.denx.de 
> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Michael Trimarchi
> Sent: Monday, March 23, 2009 2:46 PM
> To: Rendine Francesco
> Cc: u-boot at lists.denx.de
> Subject: Re: [U-Boot] USB EHCI driver
> 
> Hi,
> 
> Rendine Francesco wrote:
> >
> > Hi,
> >
> > I've already tried that define, but nothing is changed...
> > What can I see in the USB driver to resolve issue?
> >
> > Thanks.
> >
> > -----Original Message-----
> > From: Michael Trimarchi [mailto:trimarchi at gandalf.sssup.it]
> > Sent: Fri 3/20/2009 9:36 AM
> > To: Rendine Francesco
> > Cc: u-boot at lists.denx.de
> > Subject: Re: [U-Boot] USB EHCI driver
> >
> > Hi,
> >
> > FrancescoVT wrote:
> > > usb_control_msg: request: 0x6, requesttype: 0x80, value 
> 0x100 index 
> > > 0x0 length 0x40 dev=1ffebb08, pipe=88000083, buffer=1f9a671a, 
> > > length=64, req=1ffea214
> > > req=6 (0x6), type=128 (0x80), value=256 (0x100), index=0 
> EHCI fail 
> > > timeout STD_ASS reset
> > > usb_new_device: usb_get_descriptor() failed
> > >  
> > #define CONFIG_LEGACY_USB_INIT_SEQ
> >
> > Michael
> >
> >
> >
> Sorry I can't help you without the board :( and now I don't 
> have another board to test to verify it. I'm working on 
> android, and some migor issue.
> 
> Michael
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
> 
> 

[U-Boot] USB EHCI driver

[Michael Trimarchi]

Hi,

Gupta Maneesh-B18878 wrote:
> Hi Francesco,
>
> Could you make any progress?
>
> Regards
> Maneesh
>  
>
>   
>> -----Original Message-----
>> From: u-boot-bounces at lists.denx.de 
>> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Michael Trimarchi
>> Sent: Monday, March 23, 2009 2:46 PM
>> To: Rendine Francesco
>> Cc: u-boot at lists.denx.de
>> Subject: Re: [U-Boot] USB EHCI driver
>>
>> Hi,
>>
>> Rendine Francesco wrote:
>>     
>>> Hi,
>>>
>>> I've already tried that define, but nothing is changed...
>>> What can I see in the USB driver to resolve issue?
>>>
>>> Thanks.
>>>
>>> -----Original Message-----
>>> From: Michael Trimarchi [mailto:trimarchi at gandalf.sssup.it]
>>> Sent: Fri 3/20/2009 9:36 AM
>>> To: Rendine Francesco
>>> Cc: u-boot at lists.denx.de
>>> Subject: Re: [U-Boot] USB EHCI driver
>>>
>>> Hi,
>>>
>>> FrancescoVT wrote:
>>>       
>>>> usb_control_msg: request: 0x6, requesttype: 0x80, value 
>>>>         
>> 0x100 index 
>>     
>>>> 0x0 length 0x40 dev=1ffebb08, pipe=88000083, buffer=1f9a671a, 
>>>> length=64, req=1ffea214
>>>> req=6 (0x6), type=128 (0x80), value=256 (0x100), index=0 
>>>>         
>> EHCI fail 
>>     
>>>> timeout STD_ASS reset
>>>> usb_new_device: usb_get_descriptor() failed
>>>>  
>>>>         
>>> #define CONFIG_LEGACY_USB_INIT_SEQ
>>>
>>> Michael
>>>
>>>
>>>
>>>       
>> Sorry I can't help you without the board :( and now I don't 
>> have another board to test to verify it. I'm working on 
>> android, and some migor issue.
>>
>> Michael
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
>>
>>
>>     
>
>   
I don't ask anymore because I'm busy, BTW good question

Michael

[U-Boot] USB EHCI driver

[John Rigby]

Francesco,

Could you send what you have done so far to the list.  Someone else might be
able to pick it up and figure out what might be wrong.

Thanks
John

On Mon, Mar 23, 2009 at 2:44 AM, Rendine Francesco <
Francesco.Rendine@valueteam.com> wrote:

> Hi,
>
> I've already tried that define, but nothing is changed...
> What can I see in the USB driver to resolve issue?
>
> Thanks.
>
> -----Original Message-----
> From: Michael Trimarchi [mailto:trimarchi at gandalf.sssup.it]
> Sent: Fri 3/20/2009 9:36 AM
> To: Rendine Francesco
> Cc: u-boot at lists.denx.de
> Subject: Re: [U-Boot] USB EHCI driver
>
> Hi,
>
> FrancescoVT wrote:
> > usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0
> > length 0x40
> > dev=1ffebb08, pipe=88000083, buffer=1f9a671a, length=64, req=1ffea214
> > req=6 (0x6), type=128 (0x80), value=256 (0x100), index=0
> > EHCI fail timeout STD_ASS reset
> > usb_new_device: usb_get_descriptor() failed
> >
> #define CONFIG_LEGACY_USB_INIT_SEQ
>
> Michael
>
>
>
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
>

[U-Boot] R: USB EHCI driver

[Rendine Francesco]

Hi all,

I'm successful in provide a preliminary support to EHCI USB Freescale controller integrated on ADS5121 platform.
I'm preparing a patch to submit to u-boot mailing list.

Regards,
Francesco.


-----Messaggio originale-----
Da: Michael Trimarchi [mailto:trimarchi at gandalf.sssup.it]
Inviato: gio 4/9/2009 7:50
A: Gupta Maneesh-B18878
Cc: Rendine Francesco; u-boot at lists.denx.de
Oggetto: Re: [U-Boot] USB EHCI driver
 
Hi,

Gupta Maneesh-B18878 wrote:
> Hi Francesco,
>
> Could you make any progress?
>
> Regards
> Maneesh
>  
>
>   
>> -----Original Message-----
>> From: u-boot-bounces at lists.denx.de 
>> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Michael Trimarchi
>> Sent: Monday, March 23, 2009 2:46 PM
>> To: Rendine Francesco
>> Cc: u-boot at lists.denx.de
>> Subject: Re: [U-Boot] USB EHCI driver
>>
>> Hi,
>>
>> Rendine Francesco wrote:
>>     
>>> Hi,
>>>
>>> I've already tried that define, but nothing is changed...
>>> What can I see in the USB driver to resolve issue?
>>>
>>> Thanks.
>>>
>>> -----Original Message-----
>>> From: Michael Trimarchi [mailto:trimarchi at gandalf.sssup.it]
>>> Sent: Fri 3/20/2009 9:36 AM
>>> To: Rendine Francesco
>>> Cc: u-boot at lists.denx.de
>>> Subject: Re: [U-Boot] USB EHCI driver
>>>
>>> Hi,
>>>
>>> FrancescoVT wrote:
>>>       
>>>> usb_control_msg: request: 0x6, requesttype: 0x80, value 
>>>>         
>> 0x100 index 
>>     
>>>> 0x0 length 0x40 dev=1ffebb08, pipe=88000083, buffer=1f9a671a, 
>>>> length=64, req=1ffea214
>>>> req=6 (0x6), type=128 (0x80), value=256 (0x100), index=0 
>>>>         
>> EHCI fail 
>>     
>>>> timeout STD_ASS reset
>>>> usb_new_device: usb_get_descriptor() failed
>>>>  
>>>>         
>>> #define CONFIG_LEGACY_USB_INIT_SEQ
>>>
>>> Michael
>>>
>>>
>>>
>>>       
>> Sorry I can't help you without the board :( and now I don't 
>> have another board to test to verify it. I'm working on 
>> android, and some migor issue.
>>
>> Michael
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
>>
>>
>>     
>
>   
I don't ask anymore because I'm busy, BTW good question

Michael

[U-Boot] R: USB EHCI driver

[Prafulla Wadaskar]

Hi Francesco

Great Job!!!
I am in process doing the same for Marvell Kirkwood
Hopefully your patch will find useful for me

Regards...
Prafulla . .


> -----Original Message-----
> From: u-boot-bounces at lists.denx.de 
> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Rendine Francesco
> Sent: Tuesday, June 23, 2009 8:32 PM
> To: Michael Trimarchi; Gupta Maneesh-B18878
> Cc: u-boot at lists.denx.de
> Subject: [U-Boot] R: USB EHCI driver
> 
> Hi all,
> 
> I'm successful in provide a preliminary support to EHCI USB 
> Freescale controller integrated on ADS5121 platform.
> I'm preparing a patch to submit to u-boot mailing list.
> 
> Regards,
> Francesco.
> 
> 
> -----Messaggio originale-----
> Da: Michael Trimarchi [mailto:trimarchi at gandalf.sssup.it]
> Inviato: gio 4/9/2009 7:50
> A: Gupta Maneesh-B18878
> Cc: Rendine Francesco; u-boot at lists.denx.de
> Oggetto: Re: [U-Boot] USB EHCI driver
>  
> Hi,
> 
> Gupta Maneesh-B18878 wrote:
> > Hi Francesco,
> >
> > Could you make any progress?
> >
> > Regards
> > Maneesh
> >  
> >
> >   
> >> -----Original Message-----
> >> From: u-boot-bounces at lists.denx.de
> >> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Michael 
> Trimarchi
> >> Sent: Monday, March 23, 2009 2:46 PM
> >> To: Rendine Francesco
> >> Cc: u-boot at lists.denx.de
> >> Subject: Re: [U-Boot] USB EHCI driver
> >>
> >> Hi,
> >>
> >> Rendine Francesco wrote:
> >>     
> >>> Hi,
> >>>
> >>> I've already tried that define, but nothing is changed...
> >>> What can I see in the USB driver to resolve issue?
> >>>
> >>> Thanks.
> >>>
> >>> -----Original Message-----
> >>> From: Michael Trimarchi [mailto:trimarchi at gandalf.sssup.it]
> >>> Sent: Fri 3/20/2009 9:36 AM
> >>> To: Rendine Francesco
> >>> Cc: u-boot at lists.denx.de
> >>> Subject: Re: [U-Boot] USB EHCI driver
> >>>
> >>> Hi,
> >>>
> >>> FrancescoVT wrote:
> >>>       
> >>>> usb_control_msg: request: 0x6, requesttype: 0x80, value
> >>>>         
> >> 0x100 index
> >>     
> >>>> 0x0 length 0x40 dev=1ffebb08, pipe=88000083, buffer=1f9a671a, 
> >>>> length=64, req=1ffea214
> >>>> req=6 (0x6), type=128 (0x80), value=256 (0x100), index=0
> >>>>         
> >> EHCI fail
> >>     
> >>>> timeout STD_ASS reset
> >>>> usb_new_device: usb_get_descriptor() failed
> >>>>  
> >>>>         
> >>> #define CONFIG_LEGACY_USB_INIT_SEQ
> >>>
> >>> Michael
> >>>
> >>>
> >>>
> >>>       
> >> Sorry I can't help you without the board :( and now I don't have 
> >> another board to test to verify it. I'm working on 
> android, and some 
> >> migor issue.
> >>
> >> Michael
> >> _______________________________________________
> >> U-Boot mailing list
> >> U-Boot at lists.denx.de
> >> http://lists.denx.de/mailman/listinfo/u-boot
> >>
> >>
> >>     
> >
> >   
> I don't ask anymore because I'm busy, BTW good question
> 
> Michael
> 
> 

[U-Boot] R: USB EHCI driver

[Detlev Zundel]

Hi Francesco,

> I'm successful in provide a preliminary support to EHCI USB Freescale
> controller integrated on ADS5121 platform.  I'm preparing a patch to
> submit to u-boot mailing list.

Congratulations - I'm also looking forward to see and test the patch on
our ads5121.

Cheers
  Detlev

-- 
More than any other time in history, mankind faces a crossroads.  One
path leads  to despair  and utter  hopelessness.   The other to total
extinction.  Let us pray, we have the wisdom to choose correctly.
                                        -- Woody Allen
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de

[U-Boot] R: R: USB EHCI driver

[Rendine Francesco]

Hi,

thanks for your compliments, but I think that there is some work to do about this driver to support OTG mode and gadget mode.
For now I enabled support to host mode, and from my test does it work. 

I'm preparing the patch, and this will carry away some days because usb u-boot source code is been re-organized..
I developed my patch on u-boot 2009.03, so I have to port my job on last u-boot version.

Regards,
Francesco

-----Messaggio originale-----
Da: Detlev Zundel [mailto:dzu at denx.de]
Inviato: mer 6/24/2009 10:51
A: Rendine Francesco
Cc: Michael Trimarchi; Gupta Maneesh-B18878; u-boot at lists.denx.de
Oggetto: Re: [U-Boot] R:  USB EHCI driver
 
Hi Francesco,

> I'm successful in provide a preliminary support to EHCI USB Freescale
> controller integrated on ADS5121 platform.  I'm preparing a patch to
> submit to u-boot mailing list.

Congratulations - I'm also looking forward to see and test the patch on
our ads5121.

Cheers
  Detlev

-- 
More than any other time in history, mankind faces a crossroads.  One
path leads  to despair  and utter  hopelessness.   The other to total
extinction.  Let us pray, we have the wisdom to choose correctly.
                                        -- Woody Allen
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de

[U-Boot] R: R: USB EHCI driver

[Mike Timmons]

All,
I'm having trouble resetting my USB (virtual) root port hub following high
speed handshake on the 5121e using USB0+UTMI on the mpc5121e. If anyone has
any idea why root port hub reset typically fails, please advise. Thanks!

Francesco,

Thank you for your efforts on usb for the 5121e! I took your patch last week
and applied it to u-boot-2009.06 the patch wasn't a perfect fit for some
reason, but it was easy enough for me to extract the code from your patch
file. What version did you intend the patch for, if not u-boot-2009.06?

Regardless, I'm using a custom board based off the the ADS512101 board. I
complete your initialization step and it appears I get the 5121e registers
mapped correctly. "USB start" looks for devices, and I do see debug output
to the console when I have a USB memory stick plugged in.

I also have a USB analyzer, so I can see some action on the bus. However...

It appears I am failing to reset the root port hub after the high-speed
handshake between host and device (memory stick).

My degree of USB ignorance is a painful limitation at this point. I'm
tripping-through specs, the register set, and getting somewhat familiar with
the sequencing, but I'm grinding my gears at this point.

I attach a console log dump. A snippet of the log appears below, showing
where/why the reset fails. I also attach a screen snap of my USB analyzer
showing that some action is occurring on the wire between the host and the
device (memory stick).

This root port hub reset issue appears to be killing any subsequent device
discovery efforts. I DID try the hack of ignoring the reset failure to see
what happens. In this case I do see "2 devices" detected in the console log
(root hub plus my stick I presume), but I see no additional bus traffic on
the analyzer so I figure the reset failure is my smoking gun.


Any ideas?




console log snippet (see attached full console log dump)

hub_port_reset: resetting port 0...
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x4 index 0x1 length
0x0
req=3 (0x3), type=35 (0x23), value=4, index=1
Len is 0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length
0x4
req=0 (0x0), type=163 (0xa3), value=0, index=1
portstatus 101, change 13, 12 Mb/s
STAT_C_CONNECTION = 1 STAT_CONNECTION = 1  USB_PORT_STAT_ENABLE 0
cannot reset port 1!?
port 1 reset change
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x14 index 0x1
length 0x
0
req=1 (0x1), type=35 (0x23), value=20, index=1
Len is 0
1 USB Device(s) found
       scanning bus for storage devices... i=0
i=1
0 Storage Device(s) found
=>

FULL LOG...

usb start
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... New Device 0
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0
length 0
x8
req=6 (0x6), type=128 (0x80), value=256, index=0
USB_DT_DEVICE request
set address 1
usb_control_msg: request: 0x5, requesttype: 0x0, value 0x1 index 0x0 length
0x0
req=5 (0x5), type=0 (0x0), value=1, index=0
USB_REQ_SET_ADDRESS
Len is 0
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0
length 0
x12
req=6 (0x6), type=128 (0x80), value=256, index=0
USB_DT_DEVICE request
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 index 0x0
length 0
x9
req=6 (0x6), type=128 (0x80), value=512, index=0
USB_DT_CONFIG config
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 index 0x0
length 0
x19
req=6 (0x6), type=128 (0x80), value=512, index=0
USB_DT_CONFIG config
get_conf_no 0 Result 25, wLength 25
if 0, ep 0
##EP epmaxpacketin[1] = 2048
set configuration 1
usb_control_msg: request: 0x9, requesttype: 0x0, value 0x1 index 0x0 length
0x0
req=9 (0x9), type=0 (0x0), value=1, index=0
USB_REQ_SET_CONFIGURATION
Len is 0
new device strings: Mfr=1, Product=2, SerialNumber=0
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x300 index 0x0
length 0
xFF
req=6 (0x6), type=128 (0x80), value=768, index=0
USB_DT_STRING config
USB device number 1 default language ID 0x1
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x301 index 0x1
length 0
xFF
req=6 (0x6), type=128 (0x80), value=769, index=1
USB_DT_STRING config
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x302 index 0x1
length 0
xFF
req=6 (0x6), type=128 (0x80), value=770, index=1
USB_DT_STRING config
Manufacturer u-boot
Product      EHCI Host Controller
SerialNumber
USB hub found
usb_control_msg: request: 0x6, requesttype: 0xA0, value 0x2900 index 0x0
length
0x4
req=6 (0x6), type=160 (0xa0), value=10496, index=0
USB_DT_HUB config
usb_control_msg: request: 0x6, requesttype: 0xA0, value 0x2900 index 0x0
length
0x8
req=6 (0x6), type=160 (0xa0), value=10496, index=0
USB_DT_HUB config
1 ports detected
ganged power switching
standalone hub
global over-current protection
power on to power good time: 510ms
hub controller current requirement: 0mA
port 1 is removable
usb_control_msg: request: 0x0, requesttype: 0xA0, value 0x0 index 0x0 length
0x4
req=0 (0x0), type=160 (0xa0), value=0, index=0
get_hub_status returned status 1, change 1
local power source is lost (inactive)
no over-current condition exists
enabling power on all ports
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x8 index 0x1 length
0x0
req=3 (0x3), type=35 (0x23), value=8, index=1
Len is 0
port 1 returns 0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length
0x4
req=0 (0x0), type=163 (0xa3), value=0, index=1
Port 1 Status 101 Change 11
port 1 connection change
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length
0x4
req=0 (0x0), type=163 (0xa3), value=0, index=1
portstatus 101, change 11, 12 Mb/s
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x10 index 0x1
length 0x
0
req=1 (0x1), type=35 (0x23), value=16, index=1
Len is 0
hub_port_reset: resetting port 0...
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x4 index 0x1 length
0x0
req=3 (0x3), type=35 (0x23), value=4, index=1
Len is 0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length
0x4
req=0 (0x0), type=163 (0xa3), value=0, index=1
portstatus 101, change 13, 12 Mb/s
STAT_C_CONNECTION = 1 STAT_CONNECTION = 1  USB_PORT_STAT_ENABLE 0
cannot reset port 1!?
port 1 reset change
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x14 index 0x1
length 0x
0
req=1 (0x1), type=35 (0x23), value=20, index=1
Len is 0
1 USB Device(s) found
       scanning bus for storage devices... i=0
i=1
0 Storage Device(s) found
=>











On Wed, Jun 24, 2009 at 4:08 AM, Rendine Francesco <
Francesco.Rendine@valueteam.com> wrote:

> Hi,
>
> thanks for your compliments, but I think that there is some work to do
> about this driver to support OTG mode and gadget mode.
> For now I enabled support to host mode, and from my test does it work.
>
> I'm preparing the patch, and this will carry away some days because usb
> u-boot source code is been re-organized..
> I developed my patch on u-boot 2009.03, so I have to port my job on last
> u-boot version.
>
> Regards,
> Francesco
>
> -----Messaggio originale-----
> Da: Detlev Zundel [mailto:dzu at denx.de]
> Inviato: mer 6/24/2009 10:51
> A: Rendine Francesco
> Cc: Michael Trimarchi; Gupta Maneesh-B18878; u-boot at lists.denx.de
> Oggetto: Re: [U-Boot] R:  USB EHCI driver
>
> Hi Francesco,
>
> > I'm successful in provide a preliminary support to EHCI USB Freescale
> > controller integrated on ADS5121 platform.  I'm preparing a patch to
> > submit to u-boot mailing list.
>
> Congratulations - I'm also looking forward to see and test the patch on
> our ads5121.
>
> Cheers
>  Detlev
>
> --
> More than any other time in history, mankind faces a crossroads.  One
> path leads  to despair  and utter  hopelessness.   The other to total
> extinction.  Let us pray, we have the wisdom to choose correctly.
>                                        -- Woody Allen
> --
> DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
>
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
>

[U-Boot] R: R: USB EHCI driver

[Mike Timmons]

All,
I'm having trouble resetting my USB (virtual) root port hub following
high speed handshake on the 5121e using USB0+UTMI on the mpc5121e. If
anyone?has any idea?why root port hub reset typically fails, please
advise. Thanks!

Francesco,

Thank you for your efforts on usb for the 5121e! I took your patch
last week and applied it to u-boot-2009.06 the patch wasn't a perfect
fit for some reason, but it was easy enough for me to extract the code
from your patch file. What version did you intend the patch for, if
not u-boot-2009.06?

Regardless, I'm using a custom board based off the the ADS512101
board. I complete your initialization step and it appears I get the
5121e registers mapped correctly. "USB start" looks for devices, and I
do see debug output to the console when I have a USB memory stick
plugged in.

I also have a USB analyzer, so I can see some action on the bus. However...

It appears I am failing to reset the root port hub after the
high-speed handshake between host and device (memory stick).

My degree of USB ignorance is a painful limitation at this point. I'm
tripping-through specs, the register set, and getting somewhat
familiar with the sequencing, but I'm grinding my gears at this point.

I attach a console log dump. A snippet of the log appears below,
showing where/why the reset fails. I also attach a screen snap of my
USB analyzer showing that some action is occurring on the wire between
the host and the device (memory stick).

This root port hub reset issue appears to be killing any subsequent
device discovery efforts. I DID try the hack of ignoring the reset
failure to see what happens. In this case I do see "2 devices"
detected in the console log (root hub?plus my stick I presume), but I
see no additional bus traffic on the analyzer so I figure the reset
failure is my smoking gun.


Any ideas?

console log snippet (see attached full console log dump)

hub_port_reset: resetting port 0...
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x4 index 0x1 length 0x0
req=3 (0x3), type=35 (0x23), value=4, index=1
Len is 0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length 0x4
req=0 (0x0), type=163 (0xa3), value=0, index=1
portstatus 101, change 13, 12 Mb/s
STAT_C_CONNECTION = 1 STAT_CONNECTION = 1? USB_PORT_STAT_ENABLE 0
cannot reset port 1!?
port 1 reset change
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x14 index 0x1 length 0x
0
req=1 (0x1), type=35 (0x23), value=20, index=1
Len is 0
1 USB Device(s) found
?????? scanning bus for storage devices... i=0
i=1
0 Storage Device(s) found
=>





> On Wed, Jun 24, 2009 at 4:08 AM, Rendine Francesco <Francesco.Rendine@valueteam.com> wrote:
>>
>> Hi,
>>
>> thanks for your compliments, but I think that there is some work to do about this driver to support OTG mode and gadget mode.
>> For now I enabled support to host mode, and from my test does it work.
>>
>> I'm preparing the patch, and this will carry away some days because usb u-boot source code is been re-organized..
>> I developed my patch on u-boot 2009.03, so I have to port my job on last u-boot version.
>>
>> Regards,
>> Francesco
>>
>> -----Messaggio originale-----
>> Da: Detlev Zundel [mailto:dzu at denx.de]
>> Inviato: mer 6/24/2009 10:51
>> A: Rendine Francesco
>> Cc: Michael Trimarchi; Gupta Maneesh-B18878; u-boot at lists.denx.de
>> Oggetto: Re: [U-Boot] R: ?USB EHCI driver
>>
>> Hi Francesco,
>>
>> > I'm successful in provide a preliminary support to EHCI USB Freescale
>> > controller integrated on ADS5121 platform. ?I'm preparing a patch to
>> > submit to u-boot mailing list.
>>
>> Congratulations - I'm also looking forward to see and test the patch on
>> our ads5121.
>>
>> Cheers
>> ?Detlev
>>
>> --
>> More than any other time in history, mankind faces a crossroads. ?One
>> path leads ?to despair ?and utter ?hopelessness. ? The other to total
>> extinction. ?Let us pray, we have the wisdom to choose correctly.
>> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?-- Woody Allen
>> --
>> DENX Software Engineering GmbH, ? ? ?MD: Wolfgang Denk & Detlev Zundel
>> HRB 165235 Munich, ?Office: Kirchenstr.5, D-82194 Groebenzell, Germany
>> Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
>>
>>
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
>>
>

[U-Boot] R: R: R: USB EHCI driver

[Rendine Francesco]

Hi Mike,

my patch for USB2.0 on MPC5121e is for u-boot-2009.03. I released for that version, so it's reasonable that doesn't fit well on 2009.06.
Regard to your problem and log, as soon as I have time, I see your problem.

Regards,
Francesco.


-----Messaggio originale-----
Da: Mike Timmons [mailto:michael.joseph.timmons at gmail.com]
Inviato: lun 8/17/2009 4:04
A: Rendine Francesco; u-boot at lists.denx.de
Cc: Detlev Zundel; Mike Timmons
Oggetto: Re: [U-Boot] R: R: USB EHCI driver
 
All,
I'm having trouble resetting my USB (virtual) root port hub following
high speed handshake on the 5121e using USB0+UTMI on the mpc5121e. If
anyone?has any idea?why root port hub reset typically fails, please
advise. Thanks!

Francesco,

Thank you for your efforts on usb for the 5121e! I took your patch
last week and applied it to u-boot-2009.06 the patch wasn't a perfect
fit for some reason, but it was easy enough for me to extract the code
from your patch file. What version did you intend the patch for, if
not u-boot-2009.06?

Regardless, I'm using a custom board based off the the ADS512101
board. I complete your initialization step and it appears I get the
5121e registers mapped correctly. "USB start" looks for devices, and I
do see debug output to the console when I have a USB memory stick
plugged in.

I also have a USB analyzer, so I can see some action on the bus. However...

It appears I am failing to reset the root port hub after the
high-speed handshake between host and device (memory stick).

My degree of USB ignorance is a painful limitation at this point. I'm
tripping-through specs, the register set, and getting somewhat
familiar with the sequencing, but I'm grinding my gears at this point.

I attach a console log dump. A snippet of the log appears below,
showing where/why the reset fails. I also attach a screen snap of my
USB analyzer showing that some action is occurring on the wire between
the host and the device (memory stick).

This root port hub reset issue appears to be killing any subsequent
device discovery efforts. I DID try the hack of ignoring the reset
failure to see what happens. In this case I do see "2 devices"
detected in the console log (root hub?plus my stick I presume), but I
see no additional bus traffic on the analyzer so I figure the reset
failure is my smoking gun.


Any ideas?

console log snippet (see attached full console log dump)

hub_port_reset: resetting port 0...
usb_control_msg: request: 0x3, requesttype: 0x23, value 0x4 index 0x1 length 0x0
req=3 (0x3), type=35 (0x23), value=4, index=1
Len is 0
usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length 0x4
req=0 (0x0), type=163 (0xa3), value=0, index=1
portstatus 101, change 13, 12 Mb/s
STAT_C_CONNECTION = 1 STAT_CONNECTION = 1? USB_PORT_STAT_ENABLE 0
cannot reset port 1!?
port 1 reset change
usb_control_msg: request: 0x1, requesttype: 0x23, value 0x14 index 0x1 length 0x
0
req=1 (0x1), type=35 (0x23), value=20, index=1
Len is 0
1 USB Device(s) found
?????? scanning bus for storage devices... i=0
i=1
0 Storage Device(s) found
=>





> On Wed, Jun 24, 2009 at 4:08 AM, Rendine Francesco <Francesco.Rendine@valueteam.com> wrote:
>>
>> Hi,
>>
>> thanks for your compliments, but I think that there is some work to do about this driver to support OTG mode and gadget mode.
>> For now I enabled support to host mode, and from my test does it work.
>>
>> I'm preparing the patch, and this will carry away some days because usb u-boot source code is been re-organized..
>> I developed my patch on u-boot 2009.03, so I have to port my job on last u-boot version.
>>
>> Regards,
>> Francesco
>>
>> -----Messaggio originale-----
>> Da: Detlev Zundel [mailto:dzu at denx.de]
>> Inviato: mer 6/24/2009 10:51
>> A: Rendine Francesco
>> Cc: Michael Trimarchi; Gupta Maneesh-B18878; u-boot at lists.denx.de
>> Oggetto: Re: [U-Boot] R: ?USB EHCI driver
>>
>> Hi Francesco,
>>
>> > I'm successful in provide a preliminary support to EHCI USB Freescale
>> > controller integrated on ADS5121 platform. ?I'm preparing a patch to
>> > submit to u-boot mailing list.
>>
>> Congratulations - I'm also looking forward to see and test the patch on
>> our ads5121.
>>
>> Cheers
>> ?Detlev
>>
>> --
>> More than any other time in history, mankind faces a crossroads. ?One
>> path leads ?to despair ?and utter ?hopelessness. ? The other to total
>> extinction. ?Let us pray, we have the wisdom to choose correctly.
>> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?-- Woody Allen
>> --
>> DENX Software Engineering GmbH, ? ? ?MD: Wolfgang Denk & Detlev Zundel
>> HRB 165235 Munich, ?Office: Kirchenstr.5, D-82194 Groebenzell, Germany
>> Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
>>
>>
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
>>
>

[U-Boot] R: R: R: USB EHCI driver

[Mike Timmons]

Thanks Francesco. Does your patch for 2009.03 go over another EHCI
patch for that version? Reason being, when I download 2009.03 I don't
see most of the files your patch applies to. I still think I am
missing something. I want to try to relpicate your success by applying
your patch as you did.

Group:
is there a particular u-boot version in which substantial ehci host
support was introduced within the drivers/usb/host directory? Any
history on this will help me better understand what is or is not
working (well) at this point.


I'm fighting a root_port_hub() reset issue on the 5121e, after taking
a patch from Francesco. I wedged his patch code into 2009.06.
Basically, it looks like all the cpu-specific code needs to do is map
the specific ehci register set on a particular cpu to a structure for
the ehci code to use. In short, there is not much to Francesco's patch
by way of protocol. He kindly did the register mapping via some
initialization code for the 5121e, although the patch was not a clean
fit so I hand entered what I needed to add.

My issue is within the detection/discovery logic, where I am detecting
a high-speed device (memory stick) via high-speed handshake, but I'm
failing to reset the root port hub.

I have a USB 2.0 analyzer. I see the successful high speed handshake
with my device (memory stick), but nothing after that due to the
internal root port hub issue.




On Tue, Aug 18, 2009 at 3:01 AM, Rendine
Francesco<Francesco.Rendine@valueteam.com> wrote:
> Hi Mike,
>
> my patch for USB2.0 on MPC5121e is for u-boot-2009.03. I released for that version, so it's reasonable that doesn't fit well on 2009.06.
> Regard to your problem and log, as soon as I have time, I see your problem.
>
> Regards,
> Francesco.
>
>
> -----Messaggio originale-----
> Da: Mike Timmons [mailto:michael.joseph.timmons at gmail.com]
> Inviato: lun 8/17/2009 4:04
> A: Rendine Francesco; u-boot at lists.denx.de
> Cc: Detlev Zundel; Mike Timmons
> Oggetto: Re: [U-Boot] R: R: USB EHCI driver
>
> All,
> I'm having trouble resetting my USB (virtual) root port hub following
> high speed handshake on the 5121e using USB0+UTMI on the mpc5121e. If
> anyone?has any idea?why root port hub reset typically fails, please
> advise. Thanks!
>
> Francesco,
>
> Thank you for your efforts on usb for the 5121e! I took your patch
> last week and applied it to u-boot-2009.06 the patch wasn't a perfect
> fit for some reason, but it was easy enough for me to extract the code
> from your patch file. What version did you intend the patch for, if
> not u-boot-2009.06?
>
> Regardless, I'm using a custom board based off the the ADS512101
> board. I complete your initialization step and it appears I get the
> 5121e registers mapped correctly. "USB start" looks for devices, and I
> do see debug output to the console when I have a USB memory stick
> plugged in.
>
> I also have a USB analyzer, so I can see some action on the bus. However...
>
> It appears I am failing to reset the root port hub after the
> high-speed handshake between host and device (memory stick).
>
> My degree of USB ignorance is a painful limitation at this point. I'm
> tripping-through specs, the register set, and getting somewhat
> familiar with the sequencing, but I'm grinding my gears at this point.
>
> I attach a console log dump. A snippet of the log appears below,
> showing where/why the reset fails. I also attach a screen snap of my
> USB analyzer showing that some action is occurring on the wire between
> the host and the device (memory stick).
>
> This root port hub reset issue appears to be killing any subsequent
> device discovery efforts. I DID try the hack of ignoring the reset
> failure to see what happens. In this case I do see "2 devices"
> detected in the console log (root hub?plus my stick I presume), but I
> see no additional bus traffic on the analyzer so I figure the reset
> failure is my smoking gun.
>
>
> Any ideas?
>
> console log snippet (see attached full console log dump)
>
> hub_port_reset: resetting port 0...
> usb_control_msg: request: 0x3, requesttype: 0x23, value 0x4 index 0x1 length 0x0
> req=3 (0x3), type=35 (0x23), value=4, index=1
> Len is 0
> usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 length 0x4
> req=0 (0x0), type=163 (0xa3), value=0, index=1
> portstatus 101, change 13, 12 Mb/s
> STAT_C_CONNECTION = 1 STAT_CONNECTION = 1? USB_PORT_STAT_ENABLE 0
> cannot reset port 1!?
> port 1 reset change
> usb_control_msg: request: 0x1, requesttype: 0x23, value 0x14 index 0x1 length 0x
> 0
> req=1 (0x1), type=35 (0x23), value=20, index=1
> Len is 0
> 1 USB Device(s) found
> ?????? scanning bus for storage devices... i=0
> i=1
> 0 Storage Device(s) found
> =>
>
>
>
>
>
>> On Wed, Jun 24, 2009 at 4:08 AM, Rendine Francesco <Francesco.Rendine@valueteam.com> wrote:
>>>
>>> Hi,
>>>
>>> thanks for your compliments, but I think that there is some work to do about this driver to support OTG mode and gadget mode.
>>> For now I enabled support to host mode, and from my test does it work.
>>>
>>> I'm preparing the patch, and this will carry away some days because usb u-boot source code is been re-organized..
>>> I developed my patch on u-boot 2009.03, so I have to port my job on last u-boot version.
>>>
>>> Regards,
>>> Francesco
>>>
>>> -----Messaggio originale-----
>>> Da: Detlev Zundel [mailto:dzu at denx.de]
>>> Inviato: mer 6/24/2009 10:51
>>> A: Rendine Francesco
>>> Cc: Michael Trimarchi; Gupta Maneesh-B18878; u-boot at lists.denx.de
>>> Oggetto: Re: [U-Boot] R: ?USB EHCI driver
>>>
>>> Hi Francesco,
>>>
>>> > I'm successful in provide a preliminary support to EHCI USB Freescale
>>> > controller integrated on ADS5121 platform. ?I'm preparing a patch to
>>> > submit to u-boot mailing list.
>>>
>>> Congratulations - I'm also looking forward to see and test the patch on
>>> our ads5121.
>>>
>>> Cheers
>>> ?Detlev
>>>
>>> --
>>> More than any other time in history, mankind faces a crossroads. ?One
>>> path leads ?to despair ?and utter ?hopelessness. ? The other to total
>>> extinction. ?Let us pray, we have the wisdom to choose correctly.
>>> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?-- Woody Allen
>>> --
>>> DENX Software Engineering GmbH, ? ? ?MD: Wolfgang Denk & Detlev Zundel
>>> HRB 165235 Munich, ?Office: Kirchenstr.5, D-82194 Groebenzell, Germany
>>> Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
>>>
>>>
>>> _______________________________________________
>>> U-Boot mailing list
>>> U-Boot at lists.denx.de
>>> http://lists.denx.de/mailman/listinfo/u-boot
>>>
>>
>
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
>