Hi,
I've built the kernel again. In previous compilations. I forgot enabling "Inventra HDRC" controller and selecting in "USB Gadget Support" section. So, my current kernel configuration for MUSB OTG is the next:
--- USB support
<*> Support for Host-side USB
[ ] USB verbose debug messages
[ ] USB announce new devices
*** Miscellaneous USB options ***
[ ] USB device filesystem (DEPRECATED)
[*] USB device class-devices (DEPRECATED)
[ ] Dynamic USB minor allocation
[ ] Rely on OTG Targeted Peripherals List
[ ] Disable external hubs
< > DesignWare USB3 DRD Core Support
< > USB Monitor
< > Support WUSB Cable Based Association (CBA)
*** USB Host Controller Drivers ***
< > Cypress C67x00 HCD support
< > OXU210HP HCD support
< > ISP116X HCD support
< > ISP 1760 HCD support
< > ISP1362 HCD support
<*> OHCI HCD support
< > SL811HS HCD support
< > R8A66597 HCD support
<*> Inventra Highspeed Dual Role Controller (TI, ADI, ...)
*** Platform Glue Layer ***
<*> DA8xx/OMAP-L1x
[ ] Enable Scheduling of Interrupt Endpoint (EXPERIMENTAL)
[*] Disable DMA (always use PIO)
.......................................................................
--- USB Gadget Support
[ ] Debugging messages (DEVELOPMENT)
[ ] Debugging information files (DEVELOPMENT)
(2) Maximum VBUS Power usage (2-500 mA)
(2) Number of storage pipeline buffers
<*> USB Peripheral Controller (Inventra HDRC USB Peripheral (TI, ADI, ...)) --->
<*> USB Gadget Drivers (Mass Storage Gadget) --->
Now, then I plug a Mass Storage Device (i.e a pen drive) in MUSB I can see the next in the console:
root@172.16.3.100:~# da8xx_musb_interrupt 518: VBUS error workaround (delay coming)
hub 2-0:1.0: over-current condition on port 1
da8xx_musb_interrupt 518: VBUS error workaround (delay coming)
hub 2-0:1.0: over-current condition on port 1
da8xx_musb_interrupt 518: VBUS error workaround (delay coming)
hub 2-0:1.0: over-current condition on port 1
da8xx_musb_interrupt 518: VBUS error workaround (delay coming)
It seems like it was a port supply power, but I don´t know why. Also I checked to configure the Maximum VBUS Power usage with value (400), but the problem keeps.