-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in AXI4 Xbar with unused fields #3548
Comments
tymcauley
added a commit
to tymcauley/rocket-chip
that referenced
this issue
Dec 24, 2023
tymcauley
added a commit
to tymcauley/rocket-chip
that referenced
this issue
Dec 24, 2023
tymcauley
added a commit
to tymcauley/rocket-chip
that referenced
this issue
Jan 29, 2024
tymcauley
added a commit
to tymcauley/rocket-chip
that referenced
this issue
Feb 15, 2024
Resolved by #3549. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Type of issue: bug report
Impact: no functional change
Development Phase: proposal
Other information
When constructing an AXI4 Xbar where some master/slave ports have extra fields (such as
AMBACorrupt
), but others don't, the new:<>=
connectable operators throw the following errors:It looks like this was resolved in the TileLink Xbar by adding
.waiveAll
to these operators, and I can confirm that this resolves the hardware elaboration error for me.If the current behavior is a bug, please provide the steps to reproduce the problem:
This change will reproduce the error:
Then try to emit FIRRTL for the
AMBAUnitTestConfig
.Please tell us about your environment:
master
: 74d65caWhat is the use case for changing the behavior?
If you have an AXI4 crossbar that is driven by two masters, one with the
AMBACorruptField
, and one without, then you'll get this elaboration error.The text was updated successfully, but these errors were encountered: