Closed aisfyhhh closed 3 weeks ago
Hey @aisfyhhh, pls check inline.
I am a beginner in NoC and I am more familiar with HDL languages. I downloaded the run_dir folder according to the Quickstart regression using Git Bash. I don't quite understand the purpose of the files in the folder. Are the files in the run_dir folder the results of the testbench execution?
These files are generated from the execution of all tests, within that you have the generated verilator executable model, the waveforms and some log files. If the test execution succeeded, you should have waveforms for all tests.
What do the suffixes coffee and vanilla represent? If I only want to learn the complete architecture of NoC, can I only focus on the src and tb folders?
The suffixes are some pre-defined configurations for the NoC, more info here. If you want to learn, I suggest checking the simple config (vanilla) waveforms and the RTL in src
.
Hello, @aignacio, I have learned a lot from this project. But now I have two questions about the testbench. 1. After running the regression tests for the NoC, I got FF....F and the container cannot exit. Does the "F" mean the test failed, and the "." means the test passed? I noticed that some folders don't have dump.fst files in them. I haven't made any changes to the project's code, and I have provided the container with sufficient resources.
Hey @aisfyhhh, I'm happy that you found this project useful!
❯ docker run --rm --name ravenoc_run -v $(pwd):/ravenoc -w /ravenoc aignacio/ravenoc tox -- -rP -k test_ravenoc_basic.py
I am a beginner in NoC and I am more familiar with HDL languages. I downloaded the run_dir folder according to the Quickstart regression using Git Bash. I don't quite understand the purpose of the files in the folder. Are the files in the run_dir folder the results of the testbench execution? What do the suffixes coffee and vanilla represent? If I only want to learn the complete architecture of NoC, can I only focus on the src and tb folders?