-
Notifications
You must be signed in to change notification settings - Fork 101
en fpga post synth simulation
Reoma Matsuo edited this page May 8, 2020
·
5 revisions
This page describes the procedure to run post-synthesis simulation for FPGA.
This simulation may be helpful for debugging when RSD runs correctly on the functional simulation but an FPGA.
- See Development Environment and setup the development environment for
Post-synthesis Simulation For FPGA
. - See Environment Variables and setup the environment variables for
Post-synthesis Simulation For FPGA
. - (Optional) Install Synplify.
- Open Processor/Src/Makefile.vivado.mk specify the
TEST_CODE
andMAX_TEST_CYCLES
variables-
TEST_CODE
is the path of code.hex to be simulated with -
MAX_TEST_CYCLES
is the maximum number of cycles to be simulated
-
- Go to Processor/Src and simply run below commands according to the purpose
make -f Makefile.vivado.mk post-[synthesis|implementation][-timing]
- For example, to run post-synthesis functional simulation,
make -f Makefile.vivado.mk post-synthesis
- Or to run post-implementation timing simulation,
make -f Makefile.vivado.mk post-implementation-timing
- For example, to run post-synthesis functional simulation,
- If simulation does not launch correctly, please remove Vivado project by below command and try again
make -f Makefile.vivado.mk post-synthesis-clean
- Open Processor/Project/Synplify/ver2017-03.prj on Synplify.
- In Synplify, select "Zedboard_post_synthesis" in the opened project and click "Run".
- If the synthesis ran successfully, rsd.vm is generated in Project/Synplify/Zedboard_post_synthesis/.
- Run below command
make post-synthesis
- Run below command
make post-synthesis-run
- If you want to launch GUI simulation, run below command
make post-synthesis-run-gui
- You can dump Kanata log by executing below command
make post-synthesis-kanata
- If simulation does not launch correctly, please remove Vivado project by below command and try again
make post-synthesis-clean
-
Open Processor/Src/Makefiles/CoreSources.inc.mk and add new source file name in this file, according to the file type.
- if you want to add new module file, append to
TYPES
variableMODULES = \ Main_Zynq_Wrapper.sv \ Main_Zynq.sv \ Core.sv \ ...
- The below table summarizes variables for each file type
File Type Variable in CoreSources.inc.mk Package TYPES Module / Interface MODULES Test Module TEST_MODULES Header File HEADERS - if you want to add new module file, append to
- Launch Synplify and add your new files into the project.