Dvteclipse code preprocessing simple operation method recommended

The dvteclipse tool provides the ability to preprocess code.

On the official website, the code preprocessing is also introduced:

Https://Preprocessed_Files_Support.html

Here, the preprocessing of the code using the ep3 command is taken as an example for explanation.

The engineering structure is as follows:

Test.svp: source files that need to be preprocessed with the ep3 command

Test.sv: file after conversion using ep3 command

Makefile: Use the ep3 command to preprocess the test.svp file

Dvt code preprocessing, the key is the file of default.build

Dvt_pverilog_ext_map: indicates file suffix before preprocessing and file suffix after preprocessing

Dvt_pverilog_ext_path_map: Indicates the location of the preprocessed file and the location of the file after preprocessing. The tool will automatically match the files with the same name but different file suffixes in the two directories.

Dvt_pverilog_run_on_save: Indicates the run to be executed when the preprocessed file is saved

After configuring the default.build file, rebuild the project. To open the preprocessed file, you need the right mouse button and select Open With->PVerilog Language Editor.

If you do not have this option, select Other and select PVerilog Language Editor in the interface.

At this point, the code area of ​​test.svp becomes the following interface. In the lower left corner, there are [p], [g], Compare. Represents source files, generated files, and file comparisons.

Generate file interface:

Comparison interface:

At this point, modify the source file, in the lower left corner, select [p]test.svp to switch to the source file. After saving, it will automatically run the set run-ep3 and run in the default.build to preprocess the source file and generate a new file.

The run of ep3 is actually executing the make command.

The above is the dvt file preprocessing introduction, in fact, is to configure the run parameter, and then for the preprocessed file, automatically run the run, get the generated file, and then the tool will source the source file and the generated file, corresponding.

The above run parameters are written relatively simple. Both the source file and the generated file are in the same directory, and the file is fixed. If the file is not fixed and the source file and the generated file are not in the same directory, you need to write more complicated run parameters.

Such as the following run parameters. The files selected in dvt can be automatically preprocessed and generated to the specified location. Can identify three files to be preprocessed: .svp, vfp, vp.

${selected_resource_loc}: built-in variable for dvt, absolute path to selected file

${selected_resource_name}: built-in variable of dvt, file name of selected file

First, get the source file directory and the generated file directory, extract the file suffix, determine the source file type, and then call the ep3 command to preprocess the source file using the verilog-mode plugin of emacd.

In this way, whenever the source file is saved, the run is automatically triggered, and the source file is preprocessed to obtain the destination file.