Skip to content

Conversation

@GregAC
Copy link
Contributor

@GregAC GregAC commented Jul 3, 2023

Fixes #2054

@GregAC GregAC force-pushed the mstatus_rst_val branch from 04e8838 to 520f6d5 Compare July 3, 2023 16:46
Copy link
Contributor

@rswarbrick rswarbrick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor tidiness question, but this looks sensible otherwise!

mv x30, x1
mv x31, x1

csrr x1, mstatus
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No big deal, but could you write something in the commit message that explains why this change is in this commit?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah it shouldn't be in this commit! This was my quick hack to double check the reset value, must have got swept in accidentally.

Probably explains the CI fail too, seems spike and Ibex disagree on the PoR values. Something to fix but not for this PR if ditching this line fixes the CI problem.

@GregAC GregAC force-pushed the mstatus_rst_val branch from 520f6d5 to db6a1d4 Compare July 4, 2023 09:02
@GregAC GregAC added this pull request to the merge queue Jul 4, 2023
Merged via the queue into lowRISC:master with commit 96988c6 Jul 4, 2023
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.

Unexpected PoR value of mstatus

3 participants