Re: [U-Boot] Fastboot and MUSB driver on OMAP3

2015-01-18 Thread Paul Kocialkowski
> > > The SET_ADDRESS request is received just fine, it then sets > > > musb->ep0_state = MUSB_EP0_STAGE_STATUSIN; but no IRQ arrives to trigger > > > another call to musb_g_ep0_irq. Eventually, the host just sends back > > > another SET_REQUEST. Looking at dmesg on the host (Device not responding

Re: [U-Boot] Fastboot and MUSB driver on OMAP3

2015-01-15 Thread Paul Kocialkowski
> > The SET_ADDRESS request is received just fine, it then sets > > musb->ep0_state = MUSB_EP0_STAGE_STATUSIN; but no IRQ arrives to trigger > > another call to musb_g_ep0_irq. Eventually, the host just sends back > > another SET_REQUEST. Looking at dmesg on the host (Device not responding > > to s

Re: [U-Boot] Fastboot and MUSB driver on OMAP3

2014-12-24 Thread Paul Kocialkowski
> The SET_ADDRESS request is received just fine, it then sets > musb->ep0_state = MUSB_EP0_STAGE_STATUSIN; but no IRQ arrives to trigger > another call to musb_g_ep0_irq. Eventually, the host just sends back > another SET_REQUEST. Looking at dmesg on the host (Device not responding > to set address

Re: [U-Boot] Fastboot and MUSB driver on OMAP3

2014-12-15 Thread Paul Kocialkowski
> On the host side, I get the following messages from dmesg: > > [11281.565099] usb 3-1: new high-speed USB device number 39 using xhci_hcd > [11283.178280] usb 3-1: Device not responding to set address. > [11283.378663] usb 3-1: Device not responding to set address. > [11283.579739] usb 3-1: devi

[U-Boot] Fastboot and MUSB driver on OMAP3

2014-12-13 Thread Paul Kocialkowski
I've been looking at getting fastboot working on my LG Optimus Black (P970), codename sniper, port. I found out that the BeagleBoard code is using that too, so I copied the required config options: #define CONFIG_MUSB_GADGET #define CONFIG_USB_MUSB_OMAP2PLUS #define CONFIG_MUSB_PIO_ONLY #define CO