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.
Installing LiteX and Testing VexRiscv SoC
Before installing the LiteX framework, you should enter a Python virtual environment to prevent potential package conflicts when installing LiteX dependencies. The
make cpu
command will check whether LiteX is installed.Adding Commands to
Makefile
for VexRiscv SoC TestingTwo commands added to the
Makefile
to test the VexRiscv SoCmake cpu
:This command checks if the LiteX toolchain is installed, then synthesizes the SoC and flashes the SoC design to the board. For SoC settings, please refer to: CPU.mk#L1-L6
make cpu-test
:This command compiles the code in
cpu/bare-program
to test the CPU. It prints messages via UART. Thelitex_term
tool requires specifying the host port. The default port setting in theMakefile
is/dev/ttyUSB0
. To specify the port connected to your development board, run the command.litex_term
used to load the binary program to the board and monitor the messages from UART.