2011-01-06 13:51:48     BF526 MUSB fails with high-speed devices.

Document created by Aaronwu Employee on Sep 25, 2013
Version 1Show Document
  • View in full screen mode

2011-01-06 13:51:48     BF526 MUSB fails with high-speed devices.

Felix Lazarev (UNITED STATES)

Message: 97233   

 

Hello,

 

I'm using  2010R1-RC2 version of u-boot. The config is derived from BF527-Ezkit, with disabled network, nand and video. The SCLK=75MHz, CCLK=300MHz. The u-boot enumerates fullspeed devices properly, while highspeed device fails to reply to usb_get_descriptor. Further debugging showed that actual failure happens in ctrlreq_setup_phase,  where "wait_until_ep0_ready" timeouts. The TXCSR register keeps value 0x0a, which means that setup packet was never sent. Please note that fullspeed device works fine. any ideas?

 

 

 

here is the debug log for failed device:

 

 

 

New Device 1

usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0 length 0x40

usb_new_device: usb_get_descriptor() failed

 

QuoteReplyEditDelete

 

 

2011-01-06 15:26:53     Re: BF526 MUSB fails with high-speed devices.

Mike Frysinger (UNITED STATES)

Message: 97234   

 

what silicon rev exactly are you using, and what silicon rev exactly did you compile u-boot for ?

 

better yet, just post the boot output from u-boot itself.

QuoteReplyEditDelete

 

 

2011-01-06 18:04:55     Re: BF526 MUSB fails with high-speed devices.

Felix Lazarev (UNITED STATES)

Message: 97237   

 

silicon rev 0.1, compiled for 0.1

 

if i'm forcing MUSB to fullspeed (adding  power &=~MUSB_POWER_HSENAB; in usb_lowlevel_init() ) everything is working fine.

 

the output in the previous message is from u-boot with DEBUG=1 and MUSB_DEBUG.

QuoteReplyEditDelete

 

 

2011-01-06 18:06:25     Re: BF526 MUSB fails with high-speed devices.

Felix Lazarev (UNITED STATES)

Message: 97238   

 

another interesting note: in FS mode by the time u-boot gets to query device descriptor FRAME counter is about 0x655, however in faulty HS mode at that time FRAME counter is 1!! it's like MUSB failed to initialize properly.

Attachments

    Outcomes