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

Hardwire CHERI to enable #90

Merged
merged 1 commit into from
May 23, 2024
Merged

Conversation

marnovandermaas
Copy link
Contributor

Removing a debug feature from the main branch.

@HU90m HU90m merged commit 21f4c1a into lowRISC:main May 23, 2024
2 checks passed
@nbdd0121
Copy link
Contributor

Instead of hardwiring it to disable, I wonder if we can have the rp2040 firmware communicating this information. It's still useful to have this ability in some form.

@GregAC
Copy link
Contributor

GregAC commented May 23, 2024

Instead of hardwiring it to disable, I wonder if we can have the rp2040 firmware communicating this information. It's still useful to have this ability in some form.

I am wondering if we can put it under control of Ibex with some kind of reset controller. Then the bit could be included in the flash metadata. The bootloader would remain running in CHERIoT mode but it could load a plain rv32imc binary and then instruct Ibex to reboot in non-CHERIoT mode.

However definitely a post hackathon activity!

@marnovandermaas
Copy link
Contributor Author

Interesting, we would also have to have a non-CHERI bootloader that is automatically selected in legacy mode.

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.

4 participants