Open Dennishor123 opened 1 year ago
You should execute "make -f Makefile.verilator" for compilation before "make -f Makefile.verilator run." The build and simulation example in the README was broken and has been fixed. Sorry for the inconvenience.
Hey @shioyadan,
I just tried the below cmd and I'm having the following issue while running with Verilator:
docker run -it --rm -v ./:/test/ -w /test/ aignacio/rtldev bash -c 'cd Processor/Src && make -f Makefile.verilator.mk'
Hello,
I'm not entirely sure what the specific issue is, but it seems to relate to a known problem in newer versions of Verilator, as detailed in the following discussion: https://github.com/verilator/verilator/issues/5139
This issue has been reported multiple times, and you may be able to resolve it by downgrading to an older version from the 4.x series of Verilator.
im trying to run make -f Makefile.verilator.mk run and i got this error: ../Project/Verilator/obj_dir/VMain_Zynq_Wrapper \ MAX_TEST_CYCLES=100000 \ TEST_CODE=Verification/TestCode/Asm/FP ENABLE_PC_GOAL=1 SHOW_SERIAL_OUT=1 make: ../Project/Verilator/obj_dir/VMain_Zynq_Wrapper: No such file or directory make: *** [Makefile.verilator.mk:93: run] Error 127 im wondering where does the /Project/Verilator/obj_dir/VMain_Zynq_Wrapper comes from as i couldnt find it in this github, thanks a lot