> From: Matthijs Kooijman [mailto:matth...@stdin.nl]
> Sent: Wednesday, May 08, 2013 2:02 PM
>
> I'm running into an issue with the dwc2 driver. When I power on my board
> with an usb device (mass storage in this case) connected, the hardware
> is returning transaction errors (e.g., triggering channel halted +
> xacterr interrupts) for every transfer scheduled, starting with the
> first ones.
>
> This condition stays even through a reboot, though a power cycle cures
> the condition (provided I remove the USB device for the boot). If I
> insert the USB device after the board has booted and the driver has
> loaded, everything works as expected, also after a reboot (with the
> device still plugged in).
>
> This leads me to suspect there is some issue when the time between the
> first hardware initialization and the first host channel start is too
> small or something like that? Any ideas?
>
> Also, is there any fixed list of what could cause a transaction error,
> or is this just a catchall meaning "Something went wrong"?
Hi Matthijs,
I will see if I can find some time this week to try and reproduce this.
Here is the description of XactErr from the databook (bit 7 of HCINTn):
7 Transaction Error (XactErr)
Indicates one of the following errors occurred on the USB.
* CRC check failure
* Timeout
* Bit stuff error
* False EOP
In Scatter/Gather DMA mode, the interrupt due to this bit is not set.
--
Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
