[test] Replace AES alert with status read #28855
Open
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.
This test needs to read a CSR from the AES block.
dif_aes_alert_forcewas chosen because the instruction that writes to theALERT_TESTCSR comes close to the beginning of the function and makes the crash dump accurateHowever triggering an alert will be problematic once OTTF starts catching alerts triggered by tests.
Switch to
dif_aes_get_statusinstead which I have confirmed does the CSR access within two instructions fromaes_csr_access.Cross reference with 3250128 which changed from
_get_statusto_alert_forcepresumably because the CSR access was generated further away at the time.