RX Buffer timestamp bug
In the actual logic of RX Buffer timestamp is stored in two consecutive clock cycles.
Image following situation: Timestamp value :0x00000000FFFFFFFF, is reached at the same time as lower word is stored. 0xFFFFFFFF will be stored. If the timestamp tick is 1 clock cycle, in the next clock cycle 0x0000000100000000 will the value of external timestamp- Upper word 0x00000001 will be stored resulting in invalid timestamp of frame arrival: 0x00000001FFFFFFFF.
This should be fixed. The question is whether we can assume that timestamp will be always incremented by 1. In that case we can monitor only the change in LSB of Upper word.