Resolve no-implicit-clock error with AXI4 monitors#3728
Merged
jerryz123 merged 1 commit intochipsalliance:devfrom Mar 18, 2025
Merged
Resolve no-implicit-clock error with AXI4 monitors#3728jerryz123 merged 1 commit intochipsalliance:devfrom
jerryz123 merged 1 commit intochipsalliance:devfrom
Conversation
If a user enables AXI4 Monitors (using `AXI4MonitorBuilder`), they'll get a no-implicit-clock error at this point, which isn't easy to track down. Chipyard worked around a similar problem with TileLink Monitors here: ucb-bar/chipyard#1868
jerryz123
approved these changes
Mar 17, 2025
Contributor
Author
|
Thanks for approving @jerryz123! Can we merge this now? |
Contributor
Author
|
Thanks! |
16 tasks
savnastou
pushed a commit
to savnastou/rocket-chip
that referenced
this pull request
Mar 20, 2026
Resolve no-implicit-clock error with AXI4 monitors
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
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.
If a user enables AXI4 Monitors (using
AXI4MonitorBuilder), they'll get a no-implicit-clock error at this point, which isn't easy to track down. Chipyard worked around a similar problem with TileLink Monitors here: ucb-bar/chipyard#1868Related issue: None
Type of change: bug report
Impact: no functional change
Development Phase: implementation
Release Notes
Resolve build error when using AXI4 monitors.