Refactoring AXI to support protocol variants (AXI-Lite, AXI-S, ACE, ACE-Lite) #251
Conversation
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
mkorbel1
reviewed
Aug 28, 2025
Contributor
mkorbel1
left a comment
mkorbel1
left a comment
There was a problem hiding this comment.
Looking great!
Question to think about: do we want to consider using PairInterface and make address/data channels as subInterfaces? Might make BFM etc. easier.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description & Motivation
Adding support for other common AMBA interfaces that are mostly derivatives of AXI. In some cases (ACE), this involves enhancing the BFM.
Related Issue(s)
N/A
Testing
Adding unit tests using both existing and new BFMs.
Backwards-compatibility
The changes to AXI itself should be fully backwards compatible.
Documentation
Yes, included.