SGMII core: resolve problems with packet transmission #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a draft PR to resolve problems with packet transmission of the SGMII core. I will use this to track progress and mark observations.
Current actions:
/T/
and/R/
sequence indicating the end of a packet.TXD
as in hardware, the issue can be reproduced in simulation.Observations:
0x55
, the intended output of the PCS transmit should only contain 6 times0x55
as the start-of-packet code group/S/
is replaced with0x55
at the PCS receive.TX_EN
is asserted while the PCS receive code group process is inIDLE_DISPARITY_WRONG
orIDLE_DISPARITY_OK
, another octet of the preamble is missing as the system still needs to move throughIDLE_IB
.Possible solution: add a queue for values coming from
TXD
that gets emptied whenTX_OSET.indicate
is issued, regardless of what the value ofTX_EN
is? This is thought-in-process.