Add support for the Sentinel RISC-V CPU. #2174
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.
Self-expanatory. Sentinel is my RISC-V CPU in a sea of RISC-V CPUs :D.
I assume before merging, this requires litex-hub/pythondata-auto#40 to be merged, and making a
pythondata-cpu-sentinel
repository that LiteX can reference. Naturally, CI won't pass until then either :).Sentinel is written in Amaranth and requires Python 3.11 and up. Because LiteX users aren't guaranteed to have Python 3.11 installed, I delegate Verilog code generation to a PEP-723-compatible script. Consequently, users will need to install a PEP-723-compatible tool like pipx or pdm. Either of these tools will install Python 3.11 and Sentinel's dependencies into a virtual environment long enough to pass generated Verilog back to LiteX via stdout.