[U-Boot] [PATCH] Enable usb ehci support for p2020ds board

[Felix Radensky <felix@embedded-sol.com>]

Hu Mingkai-B21284 wrote:
>  
>
>   
>> -----Original Message-----
>> From: u-boot-bounces at lists.denx.de 
>> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Felix Radensky
>> Sent: Monday, September 14, 2009 3:50 PM
>> To: Zang Roy-R61911
>> Cc: U-Boot-Denx; Zhang Junjie-B18070; Kumar Gala
>> Subject: Re: [U-Boot] [PATCH] Enable usb ehci support for 
>> p2020ds board
>>
>> Hi,
>>
>> This is what I get on MPC8536DS:
>>
>> U-Boot 2009.08-rc3 (Aug 26 2009 - 18:18:31)
>>
>> CPU:   8536E, Version: 1.0, (0x803f0090)
>> Core:  E500, Version: 3.0, (0x80210030)
>> Clock Configuration:
>>        CPU0:1249.988 MHz,
>>        CCB:499.995 MHz,
>>        DDR:249.998 MHz (499.995 MT/s data rate) 
>> (Synchronous), LBC:31.250 MHz
>> L1:    D-cache 32 kB enabled
>>        I-cache 32 kB enabled
>> Board: MPC8536DS Sys ID: 0x15, Sys Ver: 0x10, FPGA Ver: 0x13, vBank: 0
>> I2C:   ready
>> DRAM:  Initializing....    DDR: 512 MB (DDR2, 64-bit, CL=4, ECC off)
>> Top of RAM usable for U-Boot at: 20000000 Reserving 800k for 
>> U-Boot at: 1ff30000 Reserving 1032k for malloc() at: 1fe2e000 
>> Reserving 80 Bytes for Board Info at: 1fe2dfb0 Reserving 76 
>> Bytes for Global Data at: 1fe2df64 Stack Pointer at: 1fe2df48 
>> New Stack Pointer is: 1fe2df48 Now running in RAM - U-Boot 
>> at: 1ff30000
>> FLASH: 128 MB
>> L2:    512 KB enabled
>> NAND:  4096 MiB
>> Invalid ID (ff ff ff ff)
>>
>>     PCIE3 connected to Slot3 as Root Complex (base address ffe0b000)
>>                Scanning PCI bus 01
>>         01  00  8086  10b9  0200  00
>>     PCIE3 on bus 00 - 01
>>
>>     PCIE1 connected to Slot1 as Root Complex (base address ffe0a000)
>>     PCIE1 on bus 02 - 02
>>
>>     PCIE2 connected to Slot 2 as Root Complex (base address ffe09000)
>>     PCIE2 on bus 03 - 03
>>
>>     PCI: 32 bit, 66 MHz, async, host, arbiter (base address ffe08000)
>>                Scanning PCI bus 04
>> PCI on bus 04 - 04
>> Video: No radeon video card found!
>> U-Boot relocated to 1ff30000
>> MMC:  FSL_ESDHC: 0
>> Net:   e1000: 00:1b:21:1e:2d:2a
>> eTSEC1, eTSEC3, e1000#0
>> Warning: e1000#0 MAC addresses don't match:
>> Address in SROM is         00:1b:21:1e:2d:2a
>> Address in environment is  04:00:00:00:00:0c
>>
>> Hit any key to stop autoboot:  0
>> => usb reset
>> (Re)start USB...
>> USB:   Register 10011 NbrPorts 1
>> USB EHCI 1.00
>> scanning bus for devices... 2 USB Device(s) found
>>        scanning bus for storage devices... Device NOT ready
>>    Request Sense returned 00 00 00
>> 0 Storage Device(s) found
>> => usb info
>> 1: Hub,  USB Revision 2.0
>>  - u-boot EHCI Host Controller
>>  - Class: Hub
>>  - PacketSize: 64  Configurations: 1
>>  - Vendor: 0x0000  Product 0x0000 Version 1.0
>>    Configuration: 1
>>    - Interfaces: 1 Self Powered 0mA
>>      Interface: 0
>>      - Alternate Setting 0, Endpoints: 1
>>      - Class Hub
>>      - Endpoint 1 In Interrupt MaxPacket 2048 Interval 0ms
>>
>> 2: Mass Storage,  USB Revision 2.0
>>  - SanDisk Corporation Cruzer Mini 200435130107dcd07f5f
>>  - Class: (from Interface) Mass Storage
>>  - PacketSize: 64  Configurations: 1
>>  - Vendor: 0x0781  Product 0x5150 Version 0.32
>>    Configuration: 1
>>    - Interfaces: 1 Bus Powered 200mA
>>      Interface: 0
>>      - Alternate Setting 0, Endpoints: 2
>>      - Class Mass Storage, Transp. SCSI, Bulk only
>>      - Endpoint 1 In Bulk MaxPacket 512
>>      - Endpoint 1 Out Bulk MaxPacket 512
>>
>> => fatls usb 0:1
>> Device NOT ready
>>    Request Sense returned 00 00 00
>> ** Can't read from device 0 **
>>
>> ** Unable to use usb 0:1 for fatls **
>>
>>     
>
> Hi Felix,
>
> I tested this on my 8536DS board, it works well.
>
> I noticed that when scan the USB, the device is not ready, so does the
> board supply
> the power to USB stick? I run into this problem sometimes.
>   

Yes, USB stick is powered on, the green led on the stick is on.
>  
> And the CPU version you used is 1.0, so your board version should less
> than B2.
> I'm not sure whether this affects the results.
>   

I've tested another USB stick with this board, and was recognized properly.
Also, the problematic stick works fine with Linux, so I still suspect 
there's a
problem in u-boot  EHCI driver. Can you test your board with smaller/older
devices, the one that has problems is 512MB Sandisk Cruizer Mini.

Thanks.

Felix.