- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We are using the FX3 through the GPIF II Synchronous Slave FIFO Interface connected to an FPGA.
The PKTEND# signal is used to force ZLP to end a transaction.
We noticed that transfers fail in case ZLP is followed very quickly (for example, within one microframe or 125 μs) by another data packet on the burst-enabled USB IN endpoint operating at Super Speed (as described in KBA90259).
So we have implemented the workaround from KBA90259 (150 us delay between ZLP and next data packet) and this error situation did not occur anymore.
However, now we have a similar error that occurs in case ZLP is followed very quickly by a ERDY packet.
How can we prevent/solve this in the FX3?
And why is the FX3 sending the ERDY anyway? As far as we know the ZX3 was not in the flow control state.
The attachment visualizes the problem. The USB analyzer detects an unexpected ‘ERDY transaction’ at timestamp 0:05.290.608. The ZLP is present at timestamp 0:05.290.607
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Daniel,
As mentioned in the Tech Support case you created, we could not see NRDY signal before the ERDY. Can you please verify this in your actual trace?
Regards,
- Madhu Sudhan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, but I can't find any NRDYs at all, and generally it does not seem to cause any problems. Might be our trace software simply does not show them? Or perhaps the FX3 fails to generate them?