AnsweredAssumed Answered

BF525 Linux kernel cannot use USB, while U-Boot can perfectly

Question asked by gyohng on Jan 28, 2012
Latest reply on Nov 15, 2012 by dpenev

Hello,

 

I get the following errors from Linux kernel, and USB doesn't work (Blackfin/MUSB). This is a custom BF525-0.2 board.

 

usb 1-1: device descriptor read/64, error -110

usb 1-1: device descriptor read/64, error -110

usb 1-1: new high-speed USB device number 3 using musb-hdrc

usb 1-1: device descriptor read/64, error -110

usb 1-1: device descriptor read/64, error -110

usb 1-1: new high-speed USB device number 4 using musb-hdrc

usb 1-1: device not accepting address 4, error -110

usb 1-1: new high-speed USB device number 5 using musb-hdrc

usb 1-1: device not accepting address 5, error -110

hub 1-0:1.0: unable to enumerate USB device on port 1

 

What is strange - U-Boot can recognize, enumerate and boot kernel from USB. My u-boot line is

"usb start;fatload usb 0 0x1000000 /uImage;bootm 0x1000000"

 

After doing a soft reboot by typing "reboot" on the linux console, U-Boot can again without any problems enumerate the devices and load Linux.

 

Please advise, what I can try change to fix the above problem. I tried changing many USB parameters in the kernel configuration somehow without getting anywhere. The kernel is taken from the last git trunk. Apparently, there shouldn't be any hardware fault, since U-Boot is operating the same USB stick perfectly.

 

If I remember properly, somehow I succeeded initializing USB in the past on the same board with using earlier version of Linux and loading usb support as a set of modules. This time I had to compile it into the kernel, since USB core as modules apparently is not supported in the latest trunk (some sort of dependency type, which makes impossible to load it as a module). However otherwise comparing kernel configuration I couldn't find any differences in how the port is configured.

 

I apologize for bothering you guys, as it is probably some stupid mistake on my side that I overlooked. Just I wonder, if anybody can suggest why this could happen, when there is no apparent hardware fault. Please let me know, if I should provide any other information.

 

Thanks,

George.

Outcomes