06-24-2021, 07:01 AM
Hi @ufsahu,
For JTAG booting, you don't need a special stimuli file. Although if you simulate an application in RTL (e.g. using Questasim) the pulp-runtime/pulp-sdk creates a stimuli file for the testbench (I believe in build/pulpissimo/vectors). However, for JTAG booting we usually just use OpenOCD and GDB to directly load an ELF binary into PULPissimo's main memory. This binary can be found in the build directory. So the general steps are to connect to use OpenOCD to connect to the debug module within PULPissimo via JTAG, then locally connect to OpenOCD with GDB and load the binary (which in the background will instruct OpenOCD to write the binary Data to L2 memory using the risc-v jtag debug protocol. The steps are documented in the FPGA section in the PULPissimo readme on github.
Best,
Manuel
For JTAG booting, you don't need a special stimuli file. Although if you simulate an application in RTL (e.g. using Questasim) the pulp-runtime/pulp-sdk creates a stimuli file for the testbench (I believe in build/pulpissimo/vectors). However, for JTAG booting we usually just use OpenOCD and GDB to directly load an ELF binary into PULPissimo's main memory. This binary can be found in the build directory. So the general steps are to connect to use OpenOCD to connect to the debug module within PULPissimo via JTAG, then locally connect to OpenOCD with GDB and load the binary (which in the background will instruct OpenOCD to write the binary Data to L2 memory using the risc-v jtag debug protocol. The steps are documented in the FPGA section in the PULPissimo readme on github.
Best,
Manuel