Bug Description
The bug is triggered when the command strobe is executed at the same time as a byte is received and written
to the RX FIFO. The result is that the last received byte is always written to the RX FIFO. There are two
situations where this extra byte is undesired and will cause problems:
? If the SFLUSHRX strobe is executed during reception of a frame, one would expect the FIFO to be
empty afterwards. However, because of the bug, there could still be one byte in the FIFO, which, if not
dealt with, would be interpreted as the length byte of the next received frame.
? If the SRXON, SRFOFF or STXON strobes are issued during reception of a frame, after the frame has
been rejected, one extra byte could appear in the RX FIFO with no warning (before rejection or for
accepted frames, there will be an RX_FRM_ABORTED exception). The consequences are the same
as for SFLUSHRX.?
?