Provide only one way to run simulation

[JeanRochCoulon]

README.md how to run a simulation by executing Makefile commands, for instance 'make verilate'. This way does not work because additional variables need to be setup before executing these commands, for instance TARGET=cv64a6_imafdc_sv39. Many GitHub issues request support as #1489. This PR removes the getting start related to these commands to keep the way which is support that is to say using cva6.py command.

@MikeOpenHWGroup @zarubaf can you approve ?

[hhhsiang]

@JeanRochCoulon, is there any documentation or README available that explains how to use cva6.py for running simulations? Specifically, if I want to test a single instruction like rv64ui-v-add, what command should I use, in which directory should I run these commands, and what initial settings or environment paths need to be configured? Your assistance is greatly appreciated!

[JeanRochCoulon]

Recommandations are in README.md of CVA6 repository. Have you read it before ?
If you would like to run rv64ui-v-add, modify the smoke-tests.sh script in that sense. cva6.py --help produces the user manual.

[zarubaf]

👍

[hhhsiang]

Recommandations are in README.md of CVA6 repository. Have you read it before ? If you would like to run rv64ui-v-add, modify the smoke-tests.sh script in that sense. cva6.py --help produces the user manual.

@JeanRochCoulon, I had previously read the README.md, but it wasn't as explicit in explaining how to do it as shown in the screenshot below:

However, I have a better understanding now. If I want to test any specific instruction, I can simply add it to the smoke-tests.sh script and then execute it, correct? Like the following example:

Additionally, I'm a bit unsure about your statement:

cva6.py --help produces the user manual.

I tried running both cva6.py --help and make cva6.py --help, but nothing happened:

[JeanRochCoulon]

Indeed cva6.py --help produces the list of options (maybe the words "User manual" was to much in relaitn to this list).

[hhhsiang]

@JeanRochCoulon, I apologize for bothering you again.

If I wish to obtain a .vcd file by verilator or VCS for debugging purposes, how can I achieve that? The smoke-tests.sh script does not seem to generate it, and I couldn't find any information about this in the README.md.

[JeanRochCoulon]

@zchamski Can you help on this point ?