Repository navigation
Support APB5 data user signals (PWUSER, PRUSER) - #39
Merged
Merged
Conversation
Signed-off-by: Huang Rui <vowstar@gmail.com>
Signed-off-by: Huang Rui <vowstar@gmail.com>
Signed-off-by: Huang Rui <vowstar@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
APB5 peripherals use PWUSER and PRUSER to carry sideband data with each data
byte.
What this changes
transport.data_user_bits_per_bytedata_user_widthNCL_APB5_DATA_USER_WIDTHHow you checked it
Protocol simulation covers 8, 16 and 32 bit endpoints in one and two clock
domains, partial strobes, narrow splits, errors, timeouts and AXI4 traffic.
Negative controls swap neighbouring groups or keep groups for masked bytes, and
the tests catch both. The bypass fix has its own regression.
Closes: #4