Skip to content
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

Added assertions for LSU split_q and trigger_match_0_i #708

Merged

Conversation

silabs-oysteink
Copy link
Contributor

split_q should always be 0 when a new LSU instruction enters EX (currently passes)
trigger_match_0_i should remain stable when an LSU instruction is in EX but not yet allowed to progress to WB (currently fails)

Suppressing LSU valid_0_i on trigger_match_0_i could cause the split_q flag to reset to zero before the last part of an LSU was allowed to go from EX to WB. This could cause an address change and change of the trigger match value.

Updated setting/resetting of split_q to take trigger matches into account.

Added assertions to check that split_q is always 0 when a new LSU instruction enters the EX stage and that the trigger match flag is stable while an LSU instruction remains in EX.

Signed-off-by: Oystein Knauserud <[email protected]>

ed files:
…l be issued later.

Signed-off-by: Oystein Knauserud <[email protected]>

er match flag is stable while an LSU instruction remains in EX.

Signed-off-by: Oystein Knauserud <[email protected]>

ed files:
@silabs-oysteink silabs-oysteink changed the title Added assertinons for LSU split_q and trigger_match_0_i Added assertions for LSU split_q and trigger_match_0_i Nov 30, 2022
@Silabs-ArjanB Silabs-ArjanB added the Component:RTL For issues in the RTL (e.g. for files in the rtl directory) label Nov 30, 2022
@Silabs-ArjanB Silabs-ArjanB merged commit da004ce into openhwgroup:master Nov 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component:RTL For issues in the RTL (e.g. for files in the rtl directory)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants