rename missing vcs/verilator names | fix ci path
This commit is contained in:
@@ -253,7 +253,7 @@ jobs:
|
||||
- riscv-tools-installed-v1-{{ checksum "../riscv-tools.hash" }}
|
||||
- restore_cache:
|
||||
keys:
|
||||
- verilator-installed-v3-{{ checksum "sims/verisim/verilator.mk" }}
|
||||
- verilator-installed-v3-{{ checksum "sims/verilator/verilator.mk" }}
|
||||
- run:
|
||||
name: Building the blockdevrocketchip subproject using Verilator
|
||||
command: .circleci/do-rtl-build.sh blockdevrocketchip
|
||||
|
||||
@@ -39,7 +39,7 @@ else
|
||||
copy $LOCAL_RISCV_DIR/ $SERVER:$REMOTE_RISCV_DIR
|
||||
fi
|
||||
|
||||
# enter the verisim directory and build the specific config on remote server
|
||||
# enter the verilator directory and build the specific config on remote server
|
||||
run "make -C $REMOTE_SIM_DIR clean"
|
||||
run "export RISCV=\"$TOOLS_DIR\"; export LD_LIBRARY_PATH=\"$LD_LIB_DIR\"; export VERILATOR_ROOT=$REMOTE_VERILATOR_DIR/install/share/verilator; make -C $REMOTE_SIM_DIR VERILATOR_INSTALL_DIR=$REMOTE_VERILATOR_DIR JAVA_ARGS=\"-Xmx8G -Xss8M\" ${mapping[$1]}"
|
||||
run "rm -rf $REMOTE_CHIPYARD_DIR/project"
|
||||
|
||||
@@ -227,7 +227,7 @@ Now with all of that done, we can go ahead and run our simulation.
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
cd verisim
|
||||
cd verilator
|
||||
make CONFIG=PWMConfig
|
||||
./simulator-example-PWMConfig ../tests/pwm.riscv
|
||||
|
||||
|
||||
@@ -81,14 +81,14 @@ Toolchains
|
||||
Sims
|
||||
-------------------------------------------
|
||||
|
||||
**verisim (Verilator wrapper)**
|
||||
**verilator (Verilator wrapper)**
|
||||
Verilator is an open source Verilog simulator.
|
||||
The ``verisim`` directory provides wrappers which construct Verilator-based simulators from relevant generated RTL, allowing for execution of test RISC-V programs on the simulator (including vcd waveform files).
|
||||
The ``verilator`` directory provides wrappers which construct Verilator-based simulators from relevant generated RTL, allowing for execution of test RISC-V programs on the simulator (including vcd waveform files).
|
||||
See :ref:`Verilator` for more information.
|
||||
|
||||
**vsim (VCS wrapper)**
|
||||
**vcs (VCS wrapper)**
|
||||
VCS is a proprietary Verilog simulator.
|
||||
Assuming the user has valid VCS licenses and installations, the ``vsim`` directory provides wrappers which construct VCS-based simulators from relevant generated RTL, allowing for execution of test RISC-V programs on the simulator (including vcd/vpd waveform files).
|
||||
Assuming the user has valid VCS licenses and installations, the ``vcs`` directory provides wrappers which construct VCS-based simulators from relevant generated RTL, allowing for execution of test RISC-V programs on the simulator (including vcd/vpd waveform files).
|
||||
See :ref:`VCS` for more information.
|
||||
|
||||
**FireSim**
|
||||
|
||||
@@ -15,9 +15,9 @@ The following instructions assume at least one of these simulators is installed.
|
||||
Verilator/VCS Flows
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
Verilator is an open-source RTL simulator.
|
||||
We run Verilator simulations from within the ``sims/verisim`` directory which provides the necessary ``Makefile`` to both install and run Verilator simulations.
|
||||
We run Verilator simulations from within the ``sims/verilator`` directory which provides the necessary ``Makefile`` to both install and run Verilator simulations.
|
||||
On the other hand, VCS is a proprietary RTL simulator.
|
||||
We run VCS simulations from within the ``sims/vsim`` directory.
|
||||
We run VCS simulations from within the ``sims/vcs`` directory.
|
||||
Assuming VCS is already installed on the machine running simulations (and is found on our ``PATH``), then this guide is the same for both Verilator and VCS.
|
||||
|
||||
First, we will start by entering the Verilator or VCS directory:
|
||||
@@ -25,12 +25,12 @@ First, we will start by entering the Verilator or VCS directory:
|
||||
.. code-block:: shell
|
||||
|
||||
# Enter Verilator directory
|
||||
cd sims/verisim
|
||||
cd sims/verilator
|
||||
|
||||
# OR
|
||||
|
||||
# Enter VCS directory
|
||||
cd sims/vsim
|
||||
cd sims/vcs
|
||||
|
||||
In order to construct the simulator with our custom design, we run the following command within the simulator directory:
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ The Chipyard framework can download, build, and execute simulations using Verila
|
||||
|
||||
To run a simulation using Verilator, perform the following steps:
|
||||
|
||||
To compile the example design, run ``make`` in the ``sims/verisim`` directory.
|
||||
To compile the example design, run ``make`` in the ``sims/verilator`` directory.
|
||||
This will elaborate the ``DefaultRocketConfig`` in the example project.
|
||||
|
||||
An executable called ``simulator-example-DefaultRocketConfig`` will be produced.
|
||||
@@ -47,7 +47,7 @@ To run a simulation using VCS, perform the following steps:
|
||||
|
||||
Make sure that the VCS simulator is on your ``PATH``.
|
||||
|
||||
To compile the example design, run make in the ``sims/vsim`` directory.
|
||||
To compile the example design, run make in the ``sims/vcs`` directory.
|
||||
This will elaborate the ``DefaultRocketConfig`` in the example project.
|
||||
|
||||
An executable called ``simulator-example-DefaultRocketConfig`` will be produced.
|
||||
|
||||
@@ -1,31 +0,0 @@
|
||||
#!/bin/bash
|
||||
|
||||
# NOTE: TEMPORARY UNTIL CI IS ONLINE
|
||||
|
||||
# Run by just giving the test to run (run-bmark-tests | run-asm-tests)
|
||||
# Runs in vsim and verisim
|
||||
|
||||
set -ex
|
||||
set -euo pipefail
|
||||
|
||||
cd sims/vsim/
|
||||
|
||||
make SUB_PROJECT=rocketchip CONFIG=DefaultConfig
|
||||
make SUB_PROJECT=rocketchip CONFIG=DefaultConfig $1
|
||||
make SUB_PROJECT=boom CONFIG=BoomConfig
|
||||
make SUB_PROJECT=boom CONFIG=BoomConfig $1
|
||||
make SUB_PROJECT=example CONFIG=DefaultRocketConfig
|
||||
make SUB_PROJECT=example CONFIG=DefaultRocketConfig $1
|
||||
make SUB_PROJECT=boomexample CONFIG=DefaultBoomConfig
|
||||
make SUB_PROJECT=boomexample CONFIG=DefaultBoomConfig $1
|
||||
|
||||
cd ../verisim/
|
||||
|
||||
make SUB_PROJECT=rocketchip CONFIG=DefaultConfig
|
||||
make SUB_PROJECT=rocketchip CONFIG=DefaultConfig $1
|
||||
make SUB_PROJECT=boom CONFIG=BoomConfig
|
||||
make SUB_PROJECT=boom CONFIG=BoomConfig $1
|
||||
make SUB_PROJECT=example CONFIG=DefaultRocketConfig
|
||||
make SUB_PROJECT=example CONFIG=DefaultRocketConfig $1
|
||||
make SUB_PROJECT=boomexample CONFIG=DefaultBoomConfig
|
||||
make SUB_PROJECT=boomexample CONFIG=DefaultBoomConfig $1
|
||||
@@ -92,7 +92,7 @@ $(sim_debug): $(model_mk_debug)
|
||||
$(MAKE) VM_PARALLEL_BUILDS=1 -C $(build_dir)/$(long_name).debug -f V$(VLOG_MODEL).mk
|
||||
|
||||
#########################################################################################
|
||||
# create a verisim vpd rule
|
||||
# create a verilator vpd rule
|
||||
#########################################################################################
|
||||
$(output_dir)/%.vpd: $(output_dir)/% $(sim_debug)
|
||||
rm -f $@.vcd && mkfifo $@.vcd
|
||||
|
||||
Reference in New Issue
Block a user