Disclosure of Invention
Aiming at the problems in the prior art, the invention provides a software automation generation server flow design method based on software and hardware collaborative simulation.
In order to achieve the technical purpose, the invention provides a software automation generation Tansor flow frame design based on software and hardware collaborative simulation verification, the required Transactor IP can be automatically generated through parameter configuration of a user on the software side, and the problem that the required Transactor cannot be automatically configured based on an emulator and can be successfully inserted into any layer in a DUT (device under test) in the software and hardware collaborative simulation verification mode process can be solved. The method comprises the following specific steps:
the software automatic generation server process design method based on software and hardware collaborative simulation comprises the following specific steps:
step one, establishing a project in compiling software;
step two, configuring the environments of the design dut to be tested and the transactor;
generating a transactor.
Analyzing the design to be tested dut through rtl analysis software, and generating a hierarchical path file hierarchy.
Selecting a bottom Up mode in the netlist analysis software to synthesize the design to be tested dut in parallel, and generating a dut.
Sixthly, generating an interface file hs _ pull _ scimi _ to _ top.json with scimi information by using a script and netlist analysis software based on the files obtained in the third step, the fourth step and the fifth step;
step seven, generating a dut _ with _ supervisor.edf netlist file by using netlist analysis software based on the hs _ pull _ supervisor _ to _ top.json netlist file and the dut.edf netlist file, and then combining the dut _ with _ supervisor.edf netlist file and the responder.edf netlist file to generate a dut _ aggregated _ vectors.edf file;
and step eight, completing the transactor insertion process frame.
Specifically, the second step at least comprises setting an engineering type, a top-level module, a comprehensive tool, a dut file path, an instantiated transactor type and a name, and obtaining a transactor name.
Further, the third step is specifically: inputting a command name in compiling software, and generating a xactor _ src folder under a project file, wherein the xactor _ src folder contains a command name.
Further, the fourth step is specifically: and inputting command analyze (), and generating a hierarchy path file of hierarchy.
Further, the fifth step is specifically: setting a synthesis mode as bottom Up, inputting a transformer _ name _ stub.v file and a design source file to be tested dut.v, generating a dut.edf netlist file, and merging all netlist files after synthesis is finished.
Further, the sixth step specifically comprises: generating a test _ src folder by using a script and netlist analysis software according to a dut.edf netlist file, a hierarchy.txt hierarchical path file and a xactor _ src folder, wherein the test _ src folder at least comprises a needed transactor information file and an interface file hs _ pull _ sci _ to _ top.json with scimi information generated by the script;
further, the test _ src folder includes an hs _ xactors.f list file, and the required transactor information file is included in the hs _ xactors.f list file.
Further, the third step obtains a transaction.
Further, when the transaction
From the above description, it can be seen that the present invention has the following advantages:
1. transactors can be inserted into any layer in the DUT at the EDIF level, and the design confidentiality is better improved.
2. All the Transactor flow frames can be generated, and the required IP can be automatically generated from the lib library under the installation catalog by transmitting the name and the configuration information of the Transactor.
3. The automatic generation flow frame of the Transactor can be suitable for multi-chip verification after Partition fragmentation of the FPGA.
Detailed Description
With reference to fig. 1, a specific embodiment of the present invention is described in detail, but the present invention is not limited in any way by the claims.
As shown in fig. 1, the software automation generation process method based on software and hardware co-simulation specifically includes the following steps:
the software automatic generation affair server flow design method based on software and hardware co-simulation includes the following steps:
step one, creating a project test in compiling software (Vivado, synplify and other compiling software can be adopted);
step two, configuring the environment of the design to be tested dut and the transactor, including setting an engineering type, a top layer module, a comprehensive tool, a dut file path, an instantiated transactor type and name and the like, to obtain a transactor name, and instantiating a plurality of transactor types and names, namely obtaining a plurality of transactor names;
step three, generating a transactor. Edf netlist file of each transactor name through compiling software, and specifically comprising the following steps:
inputting command name in compiling software, and generating a factor _ src folder under a project file, where the factor _ src folder contains a factor name.edf file, a factor name _ stub.v file, and a configuration file config.txt, and when there are multiple factor names, the factor _ src folder contains multiple folders, each folder corresponds to a factor name, and contains a factor name.edf file, a factor name _ stub.v file, and a configuration file config.txt file, and the file structures are as follows:
test
|——xactor_src
|——name1
txt (information describing user settings)
I-name 1_ stub.v (Transactor Port information only. V File)
| name1.Edf (Transactor netlist file)
|——name2
|——config.txt
|——name2_stub.v
|——name2.edf
Analyzing the design to be tested dut through rtl analysis software, and generating a hierarchy path file hierarchy.
Inputting command analyze (), and generating a hierarchy path file;
fifthly, selecting a bottom Up mode in netlist analysis software (such as veridic software) to synthesize the design to be tested in parallel to generate a dut.
Setting a synthesis mode as bottom Up, inputting a transformer _ name _ stub.v file and a design source file to be tested dut.v, generating a dut.edf netlist file, and merging all netlist files after synthesis is finished;
step six, generating an interface file hs _ pull _ science _ to _ top.json with science information by using a script and netlist analysis software based on the files obtained in the step three, the step four and the step five; the method comprises the following specific steps:
according to the dual.edf netlist file, the hierarchy path file and the xactor _ src folder, a script (such as python) and netlist analysis software are used to generate a test _ src folder, the test _ src folder at least comprises an hs _ xactor.f list file and an interface file hs _ pull _ scheme _ to _ top.jjson generated by the script and provided with scheme (standard collaborative simulation modeling interface) information, a needed transactor information file is contained in the hs _ xactor.f list file, and the file structure is as follows:
test
|——test.src
i-hs _ vectors.f. (containing the list of vectors files required)
Json (interface file containing science information)
|——xactor_src
|——name
|——config.txt
|——name_stub.v
|——name.edf
Step seven, generating a du _ with _ score.edf netlist file by using netlist analysis software based on the hs _ pull _ score _ to _ top.json netlist file and the du.edf netlist file, then merging the du _ with _ score.edf netlist file and the transactor.edf netlist file to generate a du _ aggregated _ vectors.edf file, wherein the file structure is as follows:
test
|——test.backend
|——edf
| -dut _ merged _ vectors.edf (complete netlist file of completed dut insert vector)
|——test.src
|——hs_xactors.f
|——hs_pull_scemi_to_top.json
|——xactor_src
|——name
|——config.txt
|——name_stub.v
|——name.edf
And step eight, completing the transactor insertion process frame.
When the invention is implemented, when the obtained netlist file is the transaction.
Based on the FLOW method, it can be seen that:
1. when analyzing the DUT layer information, hierarchy files of all layers can be generated, so that a user can select to insert a transformer at any layer, namely, the effect of inserting a transformer at any layer in a DUT (device under test) at an EDIF (netlist level file) level can be realized, and the design confidentiality is better improved;
2. after the configuration step of the transactors is completed, each Transactor name generates an independent folder which can contain the needed Transactor file and is beneficial to multiplexing and instantiating of the subsequent steps, so that flow frames of all the transactors can be generated, and the needed IP can be automatically generated from the installation catalog by transmitting the name and configuration information of the Transactor;
3. the automatic generation flow frame of the Transactor can be suitable for multi-chip verification after Partition fragmentation of the FPGA.
Therefore, in summary, the invention has the following advantages:
1. transactors can be inserted into any layer in the DUT at the EDIF level, and the design confidentiality is better improved.
2. All the Transactor flow frames can be generated, and the required IP can be automatically generated from the lib library under the installation catalog by transmitting the name and the configuration information of the Transactor.
3. The automatic generation flow frame of the Transactor can be suitable for multi-chip verification after Partition fragmentation of the FPGA.
It should be understood that the detailed description of the invention is merely illustrative of the invention and is not intended to limit the invention to the specific embodiments described. It will be appreciated by those skilled in the art that the present invention may be modified or substituted equally as well to achieve the same technical result; as long as the use requirements are met, the method is within the protection scope of the invention.