-
Notifications
You must be signed in to change notification settings - Fork 746
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
[prim_count] Register err_o to avoid potential CDC issues downstream #24125
Conversation
This is related to lowRISC#24119. Signed-off-by: Pirmin Vogel <vogelpi@lowrisc.org>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess this will slightly change which cycle the signal appears at, but maybe we only expect this to happen when someone injects an error (so we don't really care about the timings). Is that correct?
CHANGE AUTHORIZED: hw/ip/prim/rtl/prim_count.sv |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I think this will mostly break DV or FPV if anything.
The error condition itself is treated as asynchronous in general.
CHANGE AUTHORIZED: hw/ip/prim/rtl/prim_count.sv |
You may want to double check this with the corresponding FPV TB: |
Thanks for the pointers @msfschaffner and @rswarbrick , FPV looks fine:
and
|
This looks good from a CI perspective, too. There are some FPGA test failures but the failing tests are known to be flaky or currently broken USB tests:
|
With lowRISC#24125, we added a register to the error output of all prim_count instances. This adds an additional delay until errors become actually visible via CSRs (e.g. main_sm_state, err_code). This commit adds a corresponding wait statement to take this into account. This resolves lowRISC#24226. Signed-off-by: Pirmin Vogel <vogelpi@lowrisc.org>
With #24125, we added a register to the error output of all prim_count instances. This adds an additional delay until errors become actually visible via CSRs (e.g. main_sm_state, err_code). This commit adds a corresponding wait statement to take this into account. This resolves #24226. Signed-off-by: Pirmin Vogel <vogelpi@lowrisc.org>
With lowRISC#24125, we added a register to the error output of all prim_count instances. This adds an additional delay until errors become actually visible via CSRs (e.g. main_sm_state, err_code). This commit adds a corresponding wait statement to take this into account. This resolves lowRISC#24226. Signed-off-by: Pirmin Vogel <vogelpi@lowrisc.org>
With lowRISC#24125, we added a register to the error output of all prim_count instances. This adds an additional delay until errors become actually visible via CSRs (e.g. main_sm_state, err_code). This commit adds a corresponding wait statement to take this into account. This resolves lowRISC#24226. This is a cherry pick of commit a43f5a3 to branch earlgrey_1.0.0. Signed-off-by: Pirmin Vogel <vogelpi@lowrisc.org>
With #24125, we added a register to the error output of all prim_count instances. This adds an additional delay until errors become actually visible via CSRs (e.g. main_sm_state, err_code). This commit adds a corresponding wait statement to take this into account. This resolves #24226. This is a cherry pick of commit a43f5a3 to branch earlgrey_1.0.0. Signed-off-by: Pirmin Vogel <vogelpi@lowrisc.org>
This is related to #24119.