Intra-frame control characters #169
-
|
In axis_baser_rx_64.v... from our inspection and simulation, any xgmii frame that has a control character in the middle will cause a bad frame error. Was this by design? Is it safe to assume that we will never see these gaps? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
My reading of the spec is that frames cannot contain any control characters, only data, and frames have to be sent contiguously without any gaps. As such, any control characters inside a frame is a protocol violation. I suppose I could have misread something though. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you - our reading of the specs left us thinking that it's not specifically excluded, but if nobody is complaining of this actually happening, that's a good indication that it's at least very rare. Thank you also @alexforencich for making these verilog libraries available - the quality is incredible. Much appreciated! |
Beta Was this translation helpful? Give feedback.
-
|
I just took a quick look at the spec, and I think figures 49-16 and 49-17 are pretty clear that nothing other than data is allowed inside of a frame. When transferring a frame, anything other than data or terminate characters results in moving to an error state (TX_E or RX_E). |
Beta Was this translation helpful? Give feedback.
-
|
Indeed, you are correct. Thank you! |
Beta Was this translation helpful? Give feedback.
I just took a quick look at the spec, and I think figures 49-16 and 49-17 are pretty clear that nothing other than data is allowed inside of a frame. When transferring a frame, anything other than data or terminate characters results in moving to an error state (TX_E or RX_E).