On 15/05/13 15:30, Felipe Balbi wrote:
Hi,
On Wed, May 15, 2013 at 03:15:44PM +0100, Ben Dooks wrote:
It seems the board is very picky about what it will play host to
as neither of the mini-b to A adapters I have work. I am using
a mini B to mini B cable to run the card reader.
I have still
* Ben Dooks | 2013-05-07 22:06:33 [+0200]:
We are using an OMAP5432 ES2.0 on an UEVM board
and running into issues with the dwc3 usb.
Sorry, I can't help at all. I don't have the board and I never had one.
I had ES1.0 but I never got dwc3 to work.
Sebastian
--
To unsubscribe from this list:
On 08/05/13 17:45, Sebastian Andrzej Siewior wrote:
* Ben Dooks | 2013-05-07 22:06:33 [+0200]:
We are using an OMAP5432 ES2.0 on an UEVM board
and running into issues with the dwc3 usb.
Sorry, I can't help at all. I don't have the board and I never had one.
I had ES1.0 but I never got dwc3
Hi,
On Wed, May 08, 2013 at 05:52:50PM +0200, Ben Dooks wrote:
On 08/05/13 17:45, Sebastian Andrzej Siewior wrote:
* Ben Dooks | 2013-05-07 22:06:33 [+0200]:
We are using an OMAP5432 ES2.0 on an UEVM board
and running into issues with the dwc3 usb.
Sorry, I can't help at all. I don't
On 08/05/13 18:02, Felipe Balbi wrote:
Hi,
On Wed, May 08, 2013 at 05:52:50PM +0200, Ben Dooks wrote:
On 08/05/13 17:45, Sebastian Andrzej Siewior wrote:
* Ben Dooks | 2013-05-07 22:06:33 [+0200]:
We are using an OMAP5432 ES2.0 on an UEVM board
and running into issues with the dwc3 usb.
We are using an OMAP5432 ES2.0 on an UEVM board
and running into issues with the dwc3 usb.
The first issue is that the xhci reset code stops the
entire core from working after it is executed. We have
commented the xhci reset code from issuing the CMD_RESET
and this has allowed us to get the XHCI
