Rule 5 of the AXI stream protocol checker ensures that tdata is valid when tvalid is asserted.
I am wondering if that should also be the case when not all bytes are valid (i.e. tkeep /= "1111").
For example the following trace results in an error:
# 62490000 ps - master:rule 5 - ERROR - Not unknown check failed for tdata when tvalid is high - Got ----_----_----_----_----_----_1111_0000.
The workaround is trivial, but I like setting unused byte lanes to '-' to easily see downstream issues.
Is the current behavior of the checker intentional or just an oversight?
Rule 5 of the AXI stream protocol checker ensures that
tdatais valid whentvalidis asserted.I am wondering if that should also be the case when not all bytes are valid (i.e.
tkeep /= "1111").For example the following trace results in an error:
# 62490000 ps - master:rule 5 - ERROR - Not unknown check failed for tdata when tvalid is high - Got ----_----_----_----_----_----_1111_0000.The workaround is trivial, but I like setting unused byte lanes to '-' to easily see downstream issues.
Is the current behavior of the checker intentional or just an oversight?