Skip to content

Resolve no-implicit-clock error with AXI4 monitors #3728

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

Merged
merged 1 commit into from
Mar 18, 2025

Conversation

tymcauley
Copy link
Contributor

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

Related issue: None

Type of change: bug report

Impact: no functional change

Development Phase: implementation

Release Notes

Resolve build error when using AXI4 monitors.

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
@tymcauley
Copy link
Contributor Author

Thanks for approving @jerryz123! Can we merge this now?

@jerryz123 jerryz123 merged commit 1a8dae9 into chipsalliance:dev Mar 18, 2025
28 checks passed
@tymcauley tymcauley deleted the fix-axi4-monitors branch March 18, 2025 18:40
@tymcauley
Copy link
Contributor Author

Thanks!

@tymcauley tymcauley mentioned this pull request Mar 23, 2025
16 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants