[test] Ignore bus integrity alert for scrambled SRAM test #28567
+42
−23
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
When we expect ECC errors we have to ignore the fatal bus integrity alerts from Ibex otherwise the chip will repeatedly be interrupted. Signed-off-by: James Wainwright <[email protected]>
jwnrt
requested review from
a team,
pamaury and
rprakas-gsc
and removed request for
a team
AlexJones0
approved these changes
Oct 24, 2025
Comment on lines
+286
to
+289
| // This is not done on CW305/CW310 FPGAs because interrupts for ECC errors are | ||
| // only triggered when the SecureIbex parameter is enabled. This parameter is | ||
| // disabled for these boards due to resource constraints. On CW340 and the | ||
| // other targets, this parameter is enabled. |
There was a problem hiding this comment.
Put this comment on the expect_ecc_errors function?
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.
When we expect ECC errors we have to ignore the fatal bus integrity alerts from Ibex otherwise the chip will repeatedly be interrupted.
This was missed by CI because the CW310 does not enable
SecureIbexand the CW340 tests are not being run properly on this branch.