Method and device for generating verification platform, electronic equipment and storage medium

Abstract

A method and device for generating an initial verification platform, a method for generating a target verification platform, an electronic device, and a storage medium. The method for generating the initial verification platform comprises: reading a template file from a template library; and establishing a common layer and a function layer of each first verification component based on the template file to obtain a plurality of first verification components. The function layer is inherited from the common layer, the common layer includes a common sub-component shared by the corresponding first verification component and the first verification components other than the corresponding first verification component in the plurality of first verification components, and the function layer includes a function sub-component of the corresponding first verification component, and the function sub-component is provided with a configurable parameter. The method for generating the initial verification platform can be used to dynamically generate a target verification platform for implementing a specific function, thereby reducing the repetitive work caused by manually rewriting the code, saving the verification time, and improving the verification reliability.

Description

Technical Field

[0001] Embodiments of this disclosure relate to a method and apparatus for generating a verification platform, an electronic device, and a storage medium. Background Technology

[0002] In the field of IC design, mainstream chip design increasingly favors System-on-Chip (SoC) designs that utilize reusable IP cores (Intellectual Property Cores, also known as IP modules). An IP core refers to a mature design of a circuit module within a chip that has independent functionality. Chip speed and quality are key focuses in chip development; therefore, functional verification of the chip and its IP cores is a crucial step in the chip development process to ensure both. Summary of the Invention

[0003] This disclosure provides at least one embodiment of a method for generating an initial verification platform, wherein the initial verification platform includes multiple verification components, the multiple verification components include multiple first verification components, and each of the multiple first verification components includes a common layer and a functional layer. The method for generating the initial verification platform includes: reading a template file from a template library; and based on the template file, establishing the common layer and the functional layer of each first verification component to obtain the multiple first verification components, wherein the functional layer of each first verification component inherits from the common layer, the common layer of each first verification component includes a common sub-component shared by the corresponding first verification component and the first verification components other than the corresponding first verification component among the multiple first verification components, and the functional layer of each first verification component includes a functional sub-component of the corresponding first verification component, the functional sub-component being configured with configurable parameters.

[0004] For example, the method for generating an initial verification platform provided in at least one embodiment of this disclosure further includes: generating the initial verification platform based on the inheritance relationship between the plurality of verification components.

[0005] For example, in the method for generating an initial verification platform provided in at least one embodiment of this disclosure, the inheritance relationship includes a first inheritance relationship, and the plurality of verification components include a parent verification component and a child verification component having the first inheritance relationship. The child verification component inherits the attributes of the parent verification component from the parent verification component based on the first inheritance relationship.

[0006] For example, in the method for generating an initial verification platform provided in at least one embodiment of this disclosure, each first verification component further includes a user layer, and the method for generating the initial verification platform further includes: establishing the user layer, wherein the user layer inherits from the functional layer, and the user layer reserves a custom configuration part for users to perform custom configuration.

[0007] For example, in the method for generating an initial verification platform provided in at least one embodiment of this disclosure, each first verification component further includes a base layer, and the method for generating the initial verification platform further includes: establishing the base layer, wherein the common layer inherits from the base layer, and the base layer is provided with base sub-components corresponding to the first verification components.

[0008] For example, in the method for generating an initial verification platform provided in at least one embodiment of this disclosure, the plurality of verification components further includes a second verification component that is different from the first verification component, and the method for generating the initial verification platform further includes: establishing the second verification component; and generating the initial verification platform based on the inheritance relationship between the plurality of first verification components and the second verification component.

[0009] For example, in the method for generating an initial verification platform provided in at least one embodiment of this disclosure, the initial verification platform includes a plurality of verification modules, each of the plurality of verification modules includes at least one first verification component among the plurality of first verification components, and the method for generating the initial verification platform further includes: performing visualization processing on the configurable parameters in the functional sub-components of the at least one first verification component to obtain a visualization interface corresponding to each verification module.

[0010] At least one embodiment of this disclosure also provides a method for generating a target verification platform. The method for generating a target verification platform includes: obtaining a parameter configuration table corresponding to the target verification platform; and using the parameter configuration table to set an initial verification platform generated according to the initial verification platform generation method provided in at least one embodiment of this disclosure, so as to generate the target verification platform.

[0011] For example, in the method for generating a target verification platform provided in at least one embodiment of this disclosure, the parameter configuration table includes target parameters corresponding to the plurality of first verification components. The method of setting the initial verification platform using the parameter configuration table to generate the target verification platform includes: setting configurable parameters in the functional sub-components of the plurality of first verification components using the target parameters to obtain a plurality of target first verification components of the target verification platform.

[0012] For example, in the method for generating a target verification platform provided in at least one embodiment of this disclosure, the plurality of verification components further include a second verification component that is different from the first verification component. The initial verification platform is set using the parameter configuration table to generate the target verification platform. The method further includes generating the target verification platform based on the inheritance relationship between the plurality of target first verification components and the second verification component.

[0013] For example, in the method for generating a target verification platform provided in at least one embodiment of this disclosure, the initial verification platform includes multiple verification modules, each of the multiple verification modules includes at least one first verification component among the multiple first verification components, and a visual interface is set for each verification module. The visual interface has configurable parameters in the functional sub-components of the at least one first verification component in the corresponding verification module. The step of obtaining the parameter configuration table corresponding to the target verification platform includes: using the visual interface to collect the parameters set by the user on the visual interface to obtain the target parameters corresponding to the multiple first verification components; and obtaining the parameter configuration table based on the target parameters.

[0014] At least one embodiment of this disclosure also provides an apparatus for generating an initial verification platform, wherein the initial verification platform includes multiple verification components, the multiple verification components include multiple first verification components, and each of the multiple first verification components includes a common layer and a functional layer. The apparatus for generating the initial verification platform includes: a reading module configured to read template files from a template library; and a building module configured to build the common layer and the functional layer of each first verification component based on the template files, to obtain the multiple first verification components; wherein the functional layer of each first verification component inherits from the common layer, the common layer of each first verification component includes a common sub-component shared by the corresponding first verification component and the first verification components other than the corresponding first verification component among the multiple first verification components, and the functional layer of each first verification component includes a functional sub-component of the corresponding first verification component, the functional sub-component being provided with configurable parameters.

[0015] For example, the apparatus for generating an initial verification platform provided in at least one embodiment of this disclosure further includes: a first generation module configured to generate the initial verification platform based on the inheritance relationship between the plurality of verification components.

[0016] At least one embodiment of this disclosure also provides a target verification platform generation apparatus, which includes: an acquisition module configured to acquire a parameter configuration table corresponding to the target verification platform; and a second generation module configured to use the parameter configuration table to set an initial verification platform generated by the generation method provided in at least one embodiment of this disclosure, so as to generate the target verification platform.

[0017] At least one embodiment of this disclosure also provides an electronic device. The electronic device includes: a processor; and a memory including one or more computer program modules; wherein the one or more computer program modules are stored in the memory and configured to be executed by the processor, and the one or more computer program modules are used to implement the method for generating an initial verification platform provided in any embodiment of this disclosure or the method for generating a target verification platform provided in any embodiment of this disclosure.

[0018] At least one embodiment of this disclosure also provides a storage medium storing non-transitory computer-readable instructions, which, when executed by a computer, implement the method for generating an initial verification platform provided in any embodiment of this disclosure or the method for generating a target verification platform provided in any embodiment of this disclosure. Attached Figure Description

[0019] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings of the embodiments will be briefly described below. Obviously, the drawings described below only relate to some embodiments of this disclosure and are not intended to limit this disclosure.

[0020] Figure 1A This is a schematic diagram of the structure of a UVM verification platform;

[0021] Figure 1B for Figure 1A A schematic diagram of the tree structure of the UVM validation platform;

[0022] Figure 2 An exemplary flowchart of a method for generating an initial verification platform provided in at least one embodiment of this disclosure;

[0023] Figure 3 A schematic diagram illustrating an example of a first verification component provided for at least one embodiment of this disclosure;

[0024] Figure 4 A schematic diagram illustrating an example of a visual interface for a plurality of verification modules provided in at least one embodiment of this disclosure;

[0025] Figure 5 An exemplary flowchart illustrating a method for generating a target verification platform provided in at least one embodiment of this disclosure;

[0026] Figure 6 Another exemplary flowchart of a method for generating a target verification platform provided in at least one embodiment of this disclosure;

[0027] Figure 7A This is a schematic diagram of an example of implementing Function 1 in a UVM verification platform;

[0028] Figure 7B A schematic diagram illustrating an example of how an initial verification platform generated using the method provided in at least one embodiment of this disclosure implements function 1;

[0029] Figure 8A This is a schematic diagram of another example of implementing Function 1 in a UVM verification platform;

[0030] Figure 8B A schematic diagram illustrating another example of implementing function 1 using an initial verification platform generated by the method provided in at least one embodiment of this disclosure;

[0031] Figure 9A This is a schematic diagram of an example of implementing function 2 in a UVM verification platform;

[0032] Figure 9B A schematic diagram illustrating an example of implementing function 2 using an initial verification platform generated by the method provided in at least one embodiment of this disclosure;

[0033] Figure 10 A schematic block diagram of an apparatus for generating an initial verification platform provided for at least one embodiment of the present disclosure;

[0034] Figure 11 A schematic block diagram of a target verification platform generation apparatus provided for at least one embodiment of the present disclosure;

[0035] Figure 12 A schematic block diagram of an electronic device provided for at least one embodiment of this disclosure;

[0036] Figure 13 A schematic block diagram of another electronic device provided for at least one embodiment of this disclosure; and

[0037] Figure 14 This is a schematic diagram of a storage medium provided for at least one embodiment of the present disclosure. Detailed Implementation

[0038] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the described embodiments of this disclosure without creative effort are within the scope of protection of this disclosure.

[0039] Unless otherwise defined, the technical or scientific terms used in this disclosure shall have the ordinary meaning understood by one of ordinary skill in the art to which this disclosure pertains. The terms “first,” “second,” and similar terms used in this disclosure do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Similarly, the terms “an,” “a,” or “the,” and similar terms do not indicate a quantity limitation, but rather indicate the presence of at least one. The terms “including,” “comprising,” or “containing,” and similar terms mean that the element or object preceding the word encompasses the elements or objects listed following the word and their equivalents, without excluding other elements or objects. The terms “connected,” “linked,” or similar terms are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. The terms “upper,” “lower,” “left,” and “right,” etc., are used only to indicate relative positional relationships, and these relative positional relationships may change accordingly when the absolute position of the described objects changes.

[0040] The present disclosure will now be described through several specific embodiments. To keep the following description of the embodiments of the present disclosure clear and concise, detailed descriptions of known functions and components may be omitted. When any component of the embodiments of the present disclosure appears in more than one drawing, the component is represented by the same or similar reference numerals in each drawing.

[0041] As chip performance improves and chip designs become increasingly larger, the reliance on verification grows ever stronger. UVM (Universal Verification Methodology) verification platforms are widely used in chip verification to functionally verify the chips under test and their IP cores. UVM verification is a mainstream verification method that provides a reusable, hierarchical verification platform framework. It features clear hierarchy, flexibility, ease of use, and scalability, and has become the standard for chip industry verification.

[0042] For example, the verification environment for a Device Under Test (DUT, such as an integrated circuit, chip, or IP) can be built hierarchically according to specific programming languages ​​or based on a UVM and Virtual Machine Monitor (VMM) for a specific programming language, following syntax requirements. For instance, each DUT interface requires a separate verification environment. Different verification environments are created depending on the specific DUT, and then the environment is connected to the DUT at the top level of the verification layer. Once the environment is established, it can be applied to the RTL (Real-Time Level) of the same interface using software or scripts, and then the verification environment can be manipulated through scripts. For example, when a new DUT requires a new verification environment, the verification environment script needs to be rewritten.

[0043] Figure 1A This is a schematic diagram of the structure of a UVM verification platform.

[0044] For example, such as Figure 1A As shown, the UVM validation platform can include the following validation components: validation top-level 110 (testtop), environments 120 / 121 / 122, input agent 130 (in_agent), output agent 140 (out_agent), monitor 131 / 141 (monitor), driver 132 (driver), sequencer 133 (sequence), reference model 150 (referencemodel), scoreboard 160, etc. For example, to ensure the versatility of the UVM validation platform, functional validation is broken down into separate sub-processes in UVM validation, and different sub-processes can be implemented using different validation components. Therefore, when establishing validation environments 120 (or 121 or 122, etc.) for different DUTs, validation components can be selected from the UVM validation platform to perform the corresponding sub-process validation.

[0045] For example, the top-level verification layer 110 is used to encapsulate environments 120 / 121 / 122 for functional verification of the DUT (environment 120 is used as an example below). In addition, the top-level verification layer 110 may also encapsulate an instantiated DUT and connect the DUT's interface to the virtual interface of environment 120 so that the various verification components in environment 120 can interact with the DUT (e.g., data transmission).

[0046] For example, input agent 130 and output agent 140 are used to layer and connect some verification components. Input agent 130 may encapsulate monitor 131 and driver 132, and output agent 140 may encapsulate monitor 141. Driver 132 can be used to request excitation signals from sequencer 133 and drive the excitation signals to the ports of DUT according to the bus protocol. Monitor 131 can be used to monitor the excitation signals driven on DUT and send the monitored excitation signals to reference model 150. Reference model 150 can be used to perform the same functions as DUT. Scoreboard 160 can be used to compare the data sent by reference model 150 and monitor 141 respectively, obtain the comparison result, and determine whether DUT is working correctly based on the comparison result. Monitor 241 is used to monitor the response signal generated by DUT in response to the excitation signal and send the response signal to scoreboard 160.

[0047] For example, according to Figure 1A The encapsulation method of each verification component of the UVM verification platform is such that each verification component is divided into different levels, and therefore can be represented by a tree structure. Figure 1B for Figure 1A A schematic diagram of the tree structure of the UVM verification platform.

[0048] For example, such as Figure 1B As shown, the top-level verification component 110 can serve as the root of the tree structure, while other verification components, based on different encapsulation methods, can serve as nodes at different levels within the tree structure. Figure 1B In the tree structure shown, the parent node (e.g., the top-level verification 110) can manage the connected child nodes (e.g., the environment 120) to achieve orderly management of verification components and avoid omissions and errors. Figure 1A The functions and encapsulation methods of each verification component have been described in detail, so they will not be repeated here.

[0049] For example, based on Figure 1A or Figure 1B The UVM verification platform in this context involves verification personnel manually writing code to implement specific functions for the Device Under Test (DUT), which then instantiates the target verification platform. The target verification platform interacts with the DUT through interface signal proxies and applies test stimuli to the DUT for corresponding functional verification. For example, specifically for IP modules, after the design of an IP module is completed, IP module verification personnel can manually write specific code based on the IP module's functions and interface signals to instantiate the UVM verification platform, serving as the target verification platform for the IP module, and then using the target verification platform to perform corresponding functional verification on the IP module.

[0050] Therefore, generating the target verification platform requires writing code by hand. Hand-written code is highly specialized, making it difficult to migrate between modules and resulting in a significant waste of time and effort. Alternatively, code can be generated via scripts; however, script-generated code is mostly command-line interactive, leading to inconvenience. As the number of functions requiring verification increases, the code becomes essentially unusable. Furthermore, script-generated code is static, meaning that any modifications require manual rewriting, resulting in a large amount of repetitive work and preventing automated verification.

[0051] This disclosure provides at least one embodiment of a method for generating an initial verification platform. The initial verification platform includes multiple verification components, each of which includes multiple first verification components. Each first verification component includes a shared layer and a functional layer. The method for generating the initial verification platform includes: reading template files from a template library; and based on the template files, establishing a shared layer and a functional layer for each first verification component to obtain multiple first verification components. The functional layer of each first verification component inherits from the shared layer. The shared layer of each first verification component includes a shared sub-component shared by the corresponding first verification component and other first verification components among the multiple first verification components. The functional layer of each first verification component includes a functional sub-component of the corresponding first verification component, and the functional sub-component is configured with configurable parameters.

[0052] At least one embodiment of this disclosure also provides a method for generating a target verification platform. The method for generating a target verification platform includes: obtaining a parameter configuration table corresponding to the target verification platform; and using the parameter configuration table to set the initial verification platform generated by the initial verification platform generation method provided in at least one embodiment of this disclosure to generate the target verification platform.

[0053] At least one embodiment of this disclosure also provides an apparatus for generating an initial verification platform, an apparatus for generating a target verification platform, an electronic device, and a storage medium.

[0054] The method, apparatus, device, and storage medium provided in at least one embodiment of this disclosure, by layering the verification components and reserving configurable parameters in the functional layer, separates the common parts from the parts that need to be customized by the user. This allows the user to configure the configurable parameters to modify the initial verification platform, thereby enabling the dynamic generation of a target verification platform for implementing specific functions. This reduces repetitive work caused by manually rewriting code, saves verification time, and improves verification reliability.

[0055] It should be noted that the "initial verification platform" in this disclosure can also be called the "general verification platform" and the "target verification platform" can also be called the "dedicated verification platform". Other naming methods can also be selected according to actual needs, and the embodiments of this disclosure do not limit this. In addition, the purpose and function of the "initial verification platform" and the "target verification platform" are not limited by the naming method. For details, please refer to the description in this disclosure.

[0056] At least one embodiment of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that the same reference numerals will be used to refer to the same elements described in different drawings.

[0057] Figure 2 An exemplary flowchart of a method for generating an initial verification platform provided for at least one embodiment of this disclosure.

[0058] For example, such as Figure 2 As shown, at least one embodiment of this disclosure provides a method for generating an initial verification platform. The initial verification platform includes multiple verification components, each of which includes multiple first verification components. Each first verification component includes a common layer and a functional layer. For example, the method for generating the initial verification platform includes the following steps S110 to S120.

[0059] Step S110: Read the template file from the template library;

[0060] Step S120: Based on the template file, establish the common layer and functional layer of each first verification component to obtain multiple first verification components.

[0061] For example, embodiments of this disclosure utilize a selected programming language to generate an initial verification platform; in step S110, a suitable type can be selected from the template library provided by the programming language as a template library, and the template file is the code file required to generate the initial verification platform in the template library, for example, it can be a reusable part of the code required to generate the initial verification platform.

[0062] In some examples, the initial verification platform can be the UVM verification platform; correspondingly, the programming language can be SV (SystemVerilog), Python, etc.; for example, when the programming language is Python, the template library can be the jinja2 library, Mako library, or Genshi library, etc. It should be noted that the selection of verification platform, programming language and template library is not limited to the above description, and other selections can be made as needed. The embodiments of this disclosure do not limit this.

[0063] For example, in step S120, the common layer of each first verification component includes a common sub-component shared by the corresponding first verification component and other first verification components; the functional layer of each first verification component includes the functional sub-component of the corresponding first verification component, and in particular, the functional sub-component is configured with configurable parameters. For example, taking the driver in the UVM verification platform as the first verification component, the common layer of the driver can be represented by pseudocode as base_drver, and the functional layer of the driver can be represented by pseudocode as {{name}}_shadow_drver, where {{name}} is an example of a configurable parameter, and the user can replace or modify "name" according to actual needs.

[0064] In some examples, the inheritance relationship includes a first inheritance relationship. For instance, multiple validation components may include a parent validation component and a child validation component that have a first inheritance relationship, with the child validation component inheriting properties from the parent validation component based on the first inheritance relationship.

[0065] For example, the functional layer of each first verification component inherits from the shared layer. That is, the functional layer is a child verification component, and the shared layer is a parent verification component. The functional layer can inherit the attributes of the shared layer from the shared layer based on the first inheritance relationship. For example, taking the driver in the UVM verification platform as the first verification component, an example of pseudocode for the inheritance relationship between the functional layer and the shared layer can be {{name}}_shadow_drver extends base_drver, where "extends" represents the first inheritance relationship.

[0066] In some examples, the method for generating the initial verification platform may also include step S130:

[0067] Step S130: Generate an initial verification platform based on the inheritance relationship between multiple verification components.

[0068] For example, in step S130, multiple verification components have corresponding inheritance relationships (e.g., first inheritance relationship) with each other; in the process of establishing each verification component of the initial verification platform, it is also necessary to establish inheritance relationships between multiple verification components to generate the initial verification platform. For example, taking the initial verification platform as... Figure 1A or Figure 1B Taking the UVM verification platform shown as an example, multiple verification components can be divided into different levels based on their encapsulation methods, serving as nodes at different levels in a tree structure, with corresponding inheritance relationships between parent and child nodes.

[0069] For example, in some examples, multiple verification components may also include a second verification component that is different from the first verification component. For instance, taking the initial verification platform as a UVM verification platform, the second verification component may be a reference model, used to receive stimulus signals to perform the same function as the DUT. For instance, when the second verification component is a reference model, it may not include a shared layer or a functional layer.

[0070] For example, the method for generating an initial verification platform provided in this embodiment further includes: establishing a second verification component; and generating an initial verification platform based on the inheritance relationship between multiple first verification components and second verification components. For example, taking the initial verification platform as... Figure 1A or Figure 1B Taking the UVM verification platform shown as an example, the second verification component is, for example, reference model 150, which inherits from environment 120. For example, in step S130, based on the inheritance relationship between multiple first verification components as shown in the example above, and based on the inheritance relationship between the second verification component and the corresponding first verification component as shown in the example above, an initial verification platform can be generated.

[0071] Figure 3 This is a schematic diagram illustrating an example of a first verification component provided for at least one embodiment of this disclosure. For example, it can be achieved through... Figure 2 The initial verification platform generation method in the middle is established Figure 3 The first verification component in the process.

[0072] For example, such as Figure 3 As shown, each first verification component includes a shared layer and a functional layer. For example, the shared layer contains common sub-components that can be completely shared between different first verification components. These common sub-components can be obtained, for example, through a template file. For example, the common sub-components in the shared layer of each first verification component are completely identical, and no configurable parameters need to be set, thus avoiding the problem of manually copying the common sub-components when creating each first verification component.

[0073] For example, the functional layer includes functional sub-components corresponding to the first verification component. These sub-components can be used to implement specific functions or to instantiate and connect various functional parts, such as stimulus-driven or response collection functions. For instance, the functional sub-components can be configured with configurable parameters, allowing users to modify them and making the functional layer highly modifiable. Furthermore, the other parts of the functional sub-components, besides the configurable parameters, can also be obtained through template files, thus enabling the dynamic generation of target functional layers to implement specific functions.

[0074] For example, in some examples, the shared subcomponent can be the code required to build the shared layer, and the functional subcomponent can be the code required to build the functional layer. The embodiments of this disclosure do not limit the specific form of the shared subcomponent or the functional subcomponent.

[0075] For example, such as Figure 3 As shown, each first verification component may also include a base layer. For example, the base layer may contain corresponding base sub-components for each first verification component. For instance, taking the initial verification platform as a UVM verification platform, the base sub-components may be base sub-components based on the UVM standard, such as uvm_driver and uvm_monitor.

[0076] For example, such as Figure 3 As shown, each first verification component may also include a user layer. For example, the user layer may have a reserved custom configuration section for users to customize their configurations. For instance, users can add the necessary code to the user layer as needed; since this code is difficult to integrate into template files, users can customize the configuration within the user layer. Furthermore, separating user-defined code from template files can improve the versatility and reusability of template files. For example, taking the initial verification platform as the UVM verification platform, the user layer can be used to handle the verification of top-level features or the differentiated characteristics between different DUTs, such as whether a C-model or Verification IP (VIP) is required, and includes a filelist, test cases, or regression configuration required for verification. In addition, users can add the necessary code to the user layer through custom configuration, thereby adding new functionalities.

[0077] For example, the method for generating the initial verification platform provided in this disclosure embodiment may further include: establishing a base layer (when each first verification component includes a base layer), and establishing a user layer (when each first verification component includes a user layer). For example, as Figure 3As shown, the shared layer can inherit from the base layer, meaning there is a first inheritance relationship between the shared layer and the base layer; the user layer can inherit from the functional layer, meaning there is a first inheritance relationship between the user layer and the functional layer. For example, taking the driver in the UVM verification platform as the first verification component, the base layer of the driver can be represented by pseudocode as uvm_drver, and the user layer of the driver can be represented by pseudocode as user_drver; an example of pseudocode for the inheritance relationship between the shared layer and the base layer can be base_drver extends uvm_drver, and an example of pseudocode for the inheritance relationship between the user layer and the functional layer can be user_drver extends {{name}}_shadow_drver, where "extends" represents the first inheritance relationship.

[0078] The method for generating an initial verification platform provided in at least one embodiment of this disclosure, by layering verification components and reserving configurable parameters in the functional layer, separates the common parts from the parts that need to be customized by the user. This allows the user to modify the initial verification platform by configuring the configurable parameters, thereby enabling the dynamic generation of a target verification platform for implementing specific functions. This reduces repetitive work caused by manually rewriting code, saves verification time, and improves verification reliability.

[0079] In some examples, the initial verification platform includes multiple verification modules, each verification module including at least one of multiple first verification components of the initial verification platform. For example, the method for generating the initial verification platform further includes: visualizing the configurable parameters in the functional sub-components of at least one first verification component to obtain a visual interface corresponding to each verification module.

[0080] For example, since each first verification component of each verification module includes a functional layer, and the functional sub-components in the functional layer are set with configurable parameters, the configurable parameters of each verification module can be visualized to obtain a visual interface corresponding to each verification module.

[0081] Figure 4 This is a schematic diagram of an example of a visualization interface for a plurality of verification modules provided in at least one embodiment of the present disclosure.

[0082] For example, such as Figure 4 As shown, the initial verification platform is... Figure 1A or Figure 1BTaking the UVM validation platform shown as an example, the initial validation platform can include multiple validation modules: a top-level module, an environment module, an agent module, and a scoreboard module. For example, the top-level module includes a first validation component (i.e., validation top-level 110), the environment module includes a first validation component (i.e., environment 120), and the scoreboard module includes a first validation component (i.e., scoreboard 160). When the agent module corresponds to the input agent, the environment module includes four first validation components (i.e., input agent 130, monitor 131, driver 132, sequencer 133). When the agent module corresponds to the output agent, the environment module includes two first validation components (i.e., output agent 140, monitor 141).

[0083] For example, such as Figure 4 As shown, taking the top-level module as an example, the top-level module includes configurable parameter 01, configurable parameter 02, configurable parameter 03, etc., and a visual interface for the top-level module is obtained after visualization processing. For example, users can use the visual interface of the top-level module to select "yes" or "no" for configurable parameter 01, configurable parameter 02, configurable parameter 03, etc., to select which specific parameters need to be included in the top-level module, thereby obtaining an instantiated top-level module.

[0084] For example, such as Figure 4 As shown, taking the proxy module as an example, the proxy module includes configurable parameters 11, 12, 13, etc., and a visual interface for the proxy module is obtained after visualization processing. For example, users can input the required parameters in the blank spaces of configurable parameters 11, 12, 13, etc. through the visual interface of the proxy module, thereby obtaining the instantiated proxy module. For example, specifically, taking the driver's functional layer {{name}}_shadow_drver as an example, where {{name}} is configurable parameter 12, users can input the required parameter "test_if_1" to replace "{{name}}" in the blank space of configurable parameter 12 through the visual interface, and the driver's functional layer is then instantiated as the target functional layer test_if_1_shadow_drver.

[0085] For example, such as Figure 4 As shown, users can also create new verification modules according to their actual needs to obtain corresponding visual interfaces and set parameters for the verification modules that need to be instantiated. For example, when a new DUT needs to be verified, a new verification environment needs to be created, so an environment module can be created; another example is when... Figure 4 When the proxy module corresponds to the input proxy, a proxy module corresponding to the output proxy also needs to be created, so a new proxy module can be created.

[0086] For example, such as Figure 4 As shown, the visualization interface also includes a "Generate" button. For example, after the user has set all parameters on the visualization interfaces of all verification modules, a parameter configuration table for a specific function can be obtained in the background. The parameter configuration table includes target parameters corresponding to multiple first verification components. For example, the user can click the "Generate" button to use the parameter configuration table to set the initial verification platform, thereby instantiating the initial verification platform into a target verification platform for implementing a specific function. For example, the "Generate" button can be implemented using code generation tools such as "Code Gen," and the embodiments of this disclosure do not limit this.

[0087] For example, such as Figure 4 The visual interface shown can be a graphical user interface (GUI) developed using a visual development tool. For example, the visual development tool can be a tool such as tkinter, pyqt, pyside, or wxpython in the Python language, or awt or swing in the Java language, or FLTK, QT, or MFC in the C++ language. Other programming languages ​​and other visual development tools can also be selected according to actual needs. The embodiments of this disclosure do not limit this.

[0088] It should be noted that, Figure 4 The visualization interface of the multiple verification modules shown is only an example. The multiple verification modules can be divided into other types according to actual needs, and other configuration methods can be used to set the visualization interface according to actual needs. The embodiments disclosed herein do not limit this.

[0089] For example, in the initial verification platform generation method provided in this disclosure embodiment, by setting up a visual interface for multiple verification modules, users can directly configure configurable parameters on the visual interface without writing code in the code editing interface, thus improving operational convenience. Furthermore, by setting up such... Figure 4 The "Generate" button shown allows users to generate a target verification platform for specific functions with a single click after configuring all parameters in the visual interface, thus further achieving automated verification.

[0090] Figure 5 An exemplary flowchart illustrates a method for generating a target verification platform provided in at least one embodiment of this disclosure. For example, it can be achieved through... Figure 2 The initial verification platform is instantiated using the method for generating the initial verification platform in the code to obtain... Figure 5 The target verification platform in the middle.

[0091] For example, a target verification platform is used to verify specific functions of a target DUT, and the method for generating the target verification platform includes the following steps S210 to S220.

[0092] Step S210: Obtain the parameter configuration table corresponding to the target verification platform;

[0093] Step S220: Use the parameter configuration table to set the initial verification platform generated by the initial verification platform generation method to generate the target verification platform.

[0094] For example, in step S210, the parameter configuration table includes target parameters corresponding to multiple first verification components. In some examples, the parameter configuration table corresponding to the target verification platform can be obtained using the visual interface of multiple verification modules in the initial verification platform. For example, step S210 may include: collecting parameters set by the user on the visual interface to obtain target parameters corresponding to multiple first verification components; and obtaining the parameter configuration table based on the target parameters.

[0095] For example, in step S220, configurable parameters in the functional sub-components of multiple first verification components can be set using target parameters to obtain multiple target first verification components of the target verification platform. In some examples, the initial verification platform can be configured using parameter configuration tables obtained from the visual interface of multiple verification modules in the initial verification platform, thereby instantiating the initial verification platform into a target verification platform for implementing specific functions.

[0096] For example, with Figure 4 Taking the visual interface shown as an example, all parameters set by the user on the visual interface can be collected to obtain target parameters corresponding to multiple first verification components; based on these target parameters, a parameter configuration table for specific functions can be obtained in the background. For example, such as Figure 4 As shown, after obtaining the parameter configuration table, users can click the "Generate" button to use the parameter configuration table to set up the initial verification platform, thereby dynamically generating a target verification platform for implementing specific functions.

[0097] For example, in some examples, multiple verification components may also include a second verification component that is different from the first verification component. For instance, taking the initial verification platform as a UVM verification platform, the second verification component may be a reference model, used to receive stimulus signals to perform the same function as the DUT. For example, when the second verification component is a reference model, it may not contain a shared layer or a functional layer; accordingly, the second verification component can be directly used to generate the target verification platform without setting configurable parameters.

[0098] For example, step S220 may further include: generating a target verification platform based on the inheritance relationship between multiple target first verification components and second verification components. For example, the inheritance relationship between multiple target first verification components and second verification components is the same as the inheritance relationship between multiple first verification components and second verification components in the initial verification platform.

[0099] For example, taking the initial verification platform as Figure 1A or Figure 1B Taking the UVM verification platform shown as an example, the second verification component is, for example, reference model 150, which inherits from environment 120. For example, in step S220, based on, for example Figure 2 The inheritance relationships between the multiple first verification components described in step S130, and the inheritance relationships between the second verification component and the corresponding first verification component, can generate the target verification platform.

[0100] Figure 6 Another exemplary flowchart of a method for generating a target verification platform provided in at least one embodiment of this disclosure. For example, in Figure 6 China utilizes, for example Figure 4 The visual interface shown is used to generate the target verification platform.

[0101] For example, such as Figure 6 As shown, in S1, the visualization interface is launched. For example, the homepage of the visualization interface can be used to input the name of the verification module whose parameters need to be configured, and then the parameter configuration interface of that verification module will be entered. For example, in S2, using... Figure 4 The visual interface shown collects configurable parameters set by the user on the visual interface, thereby obtaining target parameters corresponding to multiple first verification components. For example, in S3, based on these target parameters, a parameter configuration table for a specific function can be obtained in the background. For example, after obtaining the parameter configuration table, in S4, the initial verification platform is configured using the parameter configuration table (e.g., by clicking on...). Figure 4 (This can be achieved by clicking the "Generate" button shown). For example, in S5, after setting the initial verification platform using the parameter configuration table, a target verification platform for implementing specific functions can be dynamically generated.

[0102] For example, the specific process of executing the initial verification platform generation method and the target verification platform generation method provided in the embodiments of this disclosure is detailed in [link to documentation]. Figures 2-5 The description in the text will not be repeated here.

[0103] For example, using Figures 2-6 The provided methods for generating the initial verification platform and the target verification platform can be used to perform corresponding functional verification on the DUT. The following uses... Figures 7A to 9BFor example, several specific examples are described using an initial verification platform generated by the method provided in at least one embodiment of the present disclosure to implement different verification functions.

[0104] Figure 7A This is a schematic diagram of an example of implementing Function 1 in a UVM verification platform; Figure 7B This is a schematic diagram illustrating an example of how an initial verification platform generated using the method provided in at least one embodiment of this disclosure implements function 1. For example, function 1 may be a function of an invalid cycle drive X implemented in the driver verification component, or it may be other functions implemented in the driver verification component, and the embodiments of this disclosure do not limit this.

[0105] For example, such as Figure 7A As shown, in the UVM verification platform, function 1 is implemented in drivers A and B using corresponding function codes. For example, the difference between the function codes in drivers A and B lies in the variable identifier names; that is, the variable corresponding to driver A is a_if.a_data, and the variable corresponding to driver B is b_if.b_data. Therefore, the corresponding function codes need to be manually entered in drivers A and B respectively.

[0106] For example, such as Figure 7B As shown, the initial verification platform generated using the method provided in this embodiment of the disclosure includes a driver as the first verification component. Its functional layer includes functional sub-components (e.g., functional code) for implementing function 1. For example, the driver's functional sub-components are configured with configurable parameters. <if>", is used to represent the identifier name of variables in the functional code; users only need to specify the configurable parameters" <if>Replace "a" or "b" with the identifier name corresponding to driver A or driver B. For example, further, the verification platform can automatically generate function codes corresponding to driver A or driver B respectively through functional sub-components, and then dynamically generate target verification platforms for implementing function 1 corresponding to driver A and driver B respectively.

[0107] Figure 8A This is a schematic diagram of another example of implementing Function 1 in a UVM verification platform; Figure 8B This is a schematic diagram illustrating another example of implementing function 1 using an initial verification platform generated by the method provided in at least one embodiment of this disclosure. For example, Figure 8A UVM verification platform and Figure 7A same, Figure 8B verification platform and Figure 7B The similarities are the same, and the similarities will not be repeated here.

[0108] For example, such as Figure 8A As shown, in the UVM verification platform, in order to change the driver "X" of function 1 to the driver "rand", the corresponding function code needs to be manually entered in driver A and driver B respectively, and "drive X" in the function code needs to be manually changed to "drive rand".

[0109] For example, such as Figure 8B As shown, in the initial verification platform generated using the method provided in this embodiment, the "X" in the functional subcomponent of the driver can also be set as a configurable parameter. The user only needs to replace the configurable parameter "X" with "rand" and set the configurable parameter "...". <if>Replace "a" or "b" with the identifier name corresponding to driver A or driver B. For example, further, the verification platform can automatically generate function codes corresponding to driver A or driver B respectively through functional sub-components, and then dynamically generate target verification platforms for implementing function 1 corresponding to driver A and driver B respectively.

[0110] For example, such as Figure 7B and Figure 8B As shown, by configuring configurable parameters to modify the initial verification platform, a target verification platform for implementing function 1 can be dynamically generated, thereby reducing... Figure 7A and Figure 8A This eliminates the repetitive work of manually rewriting code, saves verification time, and improves verification reliability. For example, users can also utilize... Figure 4 The visual interface shown allows users to configure configurable parameters in functional sub-components without having to write code in the code editor, thus improving ease of use.

[0111] Figure 9A This is a schematic diagram of an example of implementing function 2 in a UVM verification platform; Figure 9B This is a schematic diagram illustrating an example of implementing function 2 using an initial verification platform generated by the method provided in at least one embodiment of this disclosure. For example, function 2 could be the function of verifying a performance counter in an environment verification component, or it could be other functions implemented in the environment verification component, which are not limited by the embodiments of this disclosure.

[0112] For example, such as Figure 9A As shown, in the UVM verification platform, to implement Function 2 in Environment A, Environment B, ..., Environment C respectively, it is necessary to set up corresponding Function 2 agents and corresponding Function 2 functional units in Environment A, Environment B, ..., Environment C respectively. For example, the Function 2 agent contains the code required to build the agent verification component, and the Function 2 functional unit contains a large amount of functional code used to implement Function 2.

[0113] For example, such as Figure 9A As shown, in order to establish A_Function2 Agent and A_Function2 Functional Unit in Environment A, B_Function2 Agent and B_Function2 Functional Unit in Environment B, ..., and C_Function2 Agent and C_Function2 Functional Unit in Environment C, the corresponding codes need to be manually entered in Environment A, Environment B, ..., Environment C respectively.

[0114] For example, such as Figure 9B As shown, using the initial verification platform provided in this embodiment of the disclosure, the environment serves as the first verification component of the initial verification platform, and its functional layer includes functional sub-component 1 and functional sub-component 2 for implementing function 2; functional sub-component 1 contains the code required to establish the agent of function 2, and functional sub-component 2 contains the code required to establish the functional unit of function 2.

[0115] For example, such as Figure 9B As shown, users only need to modify the configurable parameters in functional subcomponent 1 and functional subcomponent 2. For example, further, the verification platform can automatically generate A_Function 2 Agent, B_Function 2 Agent, ..., and C_Function 2 Agent through functional subcomponent 1, and automatically generate A_Function 2 Functional Unit, B_Function 2 Functional Unit, ..., and C_Function 2 Functional Unit through functional subcomponent 2. Functional subcomponent 1 and functional subcomponent 2 have been instantiated in environment A, environment B, ..., environment C respectively, and thus can dynamically generate target verification platforms for implementing function 2 corresponding to environment A, environment B, ..., environment C respectively.

[0116] For example, such as Figure 9B As shown, by configuring configurable parameters to modify the initial verification platform, a target verification platform for verifying function 2 can be dynamically generated, thereby reducing... Figure 9A This eliminates the repetitive work of manually entering the corresponding codes in environments A, B, ..., C, saving verification time and improving verification reliability. For example, users can also utilize... Figure 4 The visual interface shown allows users to configure configurable parameters in functional subcomponents 1 and 2 without having to write code in the code editor, thus improving ease of use.

[0117] It should be noted that, Figures 7A to 9B The initial verification platform generated using the method provided in at least one embodiment of this disclosure to implement different verification functions is merely an example. Other verification functions can also be selected to implement them according to actual needs, and the embodiments of this disclosure do not limit this. Furthermore, the specific processes of the initial verification platform generation method and the target verification platform generation method provided in the embodiments of this disclosure are detailed in [link to relevant documentation]. Figures 2-5 The description in the text will not be repeated here.

[0118] The method for generating an initial verification platform and a method for generating a target verification platform provided in at least one embodiment of this disclosure, by layering the verification components and reserving configurable parameters in the functional layer, separates the common parts from the parts that need to be customized by the user. This allows the user to modify the initial verification platform by configuring the configurable parameters, thereby enabling the dynamic generation of a target verification platform for implementing specific functions. This reduces the repetitive work caused by manually rewriting code, saves verification time, and improves verification reliability.

[0119] Figure 10 This is a schematic block diagram of an apparatus for generating an initial verification platform according to at least one embodiment of the present disclosure. For example, the initial verification platform includes multiple verification components, which include multiple first verification components, each of which includes a common layer and a functional layer.

[0120] For example, such as Figure 10 As shown, the initial verification platform generation device 200 includes a reading module 210, a building module 220, and a first generation module 230.

[0121] For example, reading module 210 is configured to read template files from a template library. That is, reading module 210 can be configured to perform, for example... Figure 2 The step S110 is shown.

[0122] For example, the creation module 220 is configured to create a common layer and a functional layer for each first verification component based on a template file, resulting in multiple first verification components. For instance, the functional layer of each first verification component inherits from the common layer. The common layer of each first verification component includes common sub-components shared by the corresponding first verification component and other first verification components (excluding the corresponding first verification component). The functional layer of each first verification component includes functional sub-components of the corresponding first verification component, and these functional sub-components have configurable parameters. That is, the creation module 220 can be configured to perform, for example... Figure 2 The step S120 shown.

[0123] For example, the first generation module 230 is configured to generate an initial verification platform based on the inheritance relationship between multiple verification components. That is, the first generation module 230 can be configured to perform, for example... Figure 2 The step S130 shown.

[0124] Figure 11 This is a schematic block diagram of a target verification platform generation apparatus provided for at least one embodiment of the present disclosure.

[0125] For example, such as Figure 11 As shown, the target verification platform generation device 300 includes an acquisition module 310 and a second generation module 320.

[0126] For example, the acquisition module 310 is configured to acquire the parameter configuration table corresponding to the target verification platform. That is, the acquisition module 310 can be configured to perform, for example... Figure 5 Step S210 is shown.

[0127] For example, the second generation module 320 is configured to use a parameter configuration table to set parameters according to, for example... Figure 2 The generation method shown generates an initial verification platform to generate the target verification platform. That is, the second generation module 320 can be configured to perform, for example... Figure 5 The step S220 is shown.

[0128] Due to the above description, for example Figure 2 The method for generating the initial verification platform shown and, for example... Figure 5 The process of generating the target verification platform shown has already described in detail the operation of the initial verification platform generation device 200 and the target verification platform generation device 300. Therefore, for the sake of brevity, it will not be repeated here. Relevant details can be found in Figure 1 above. Figure 9B The description.

[0129] It should be noted that, in Figure 10 The initial verification platform generation device 200 shown and Figure 11 In the target verification platform generation apparatus 300 shown, each of the aforementioned modules can be configured as software, hardware, firmware, or any combination thereof to perform a specific function. For example, these modules may correspond to dedicated integrated circuits, pure software code, or modules combining software and hardware. As an example, see [reference needed]. Figure 10 and Figure 11 The device described may be a PC computer, tablet device, personal digital assistant, smartphone, web application or other device capable of executing program instructions, but is not limited thereto.

[0130] Furthermore, although the initial verification platform generation apparatus 200 and the target verification platform generation apparatus 300 are described above as being divided into modules for performing corresponding processes respectively, it is clear to those skilled in the art that the processes performed by each module can also be performed without any specific module division in the apparatus or without clear boundaries between the modules. In addition, the above references... Figure 10 The initial verification platform generation device 200 described and Figure 11 The target verification platform generation device 300 described is not limited to the modules described above, but may also include other modules (e.g., writing module, control module, etc.) as needed, or the above modules may be combined.

[0131] At least one embodiment of this disclosure also provides an electronic device including a processor and a memory; the memory includes one or more computer program modules; the one or more computer program modules are stored in the memory and configured to be executed by the processor, and the one or more computer program modules include a method for generating an initial verification platform or a method for generating a target verification platform provided by the embodiments of this disclosure described above.

[0132] Figure 12 A schematic block diagram of an electronic device provided for at least one embodiment of the present disclosure.

[0133] For example, such as Figure 12 As shown, the electronic device 400 includes a processor 410 and a memory 420. For example, the memory 420 is used to store non-transitory computer-readable instructions (e.g., one or more computer program modules). The processor 410 is used to execute the non-transitory computer-readable instructions, which, when executed by the processor 410, can perform one or more steps of the method for generating an initial verification platform or a target verification platform as described above. The memory 420 and the processor 410 can be interconnected via a bus system and / or other forms of connection mechanisms (not shown).

[0134] For example, processor 410 may be a central processing unit (CPU), a digital signal processor (DSP), or other processing unit with data processing and / or program execution capabilities, such as a field-programmable gate array (FPGA); for example, the central processing unit (CPU) may be an x86 or ARM architecture. Processor 410 may be a general-purpose processor or a special-purpose processor, capable of controlling other components in electronic device 400 to perform desired functions.

[0135] For example, memory 420 may include any combination of one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory. Non-volatile memory may include, for example, read-only memory (ROM), hard disk, erasable programmable read-only memory (EPROM), portable compact disc read-only memory (CD-ROM), USB memory, flash memory, etc. One or more computer program modules may be stored on the computer-readable storage medium, and processor 410 may run one or more computer program modules to implement various functions of electronic device 400. Various application programs and various data, as well as various data used and / or generated by the application programs, may also be stored in the computer-readable storage medium.

[0136] It should be noted that, in the embodiments of this disclosure, the specific functions and technical effects of the electronic device 400 can be referred to the description above of the method for generating the initial verification platform and the method for generating the target verification platform provided in at least one embodiment of this disclosure, and will not be repeated here.

[0137] Figure 13 A schematic block diagram of another electronic device provided for at least one embodiment of the present disclosure.

[0138] For example, such as Figure 13 As shown, the electronic device 500 is, for example, suitable for implementing the method for generating an initial verification platform or a method for generating a target verification platform provided in the embodiments of this disclosure. It should be noted that... Figure 13 The illustrated electronic device 500 is merely an example and does not impose any limitation on the functionality and scope of use of the embodiments disclosed herein.

[0139] For example, such as Figure 13 As shown, electronic device 500 may include a processing unit (e.g., central processing unit, graphics processor, etc.) 51, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 52 or a program loaded from storage device 58 into random access memory (RAM) 53. RAM 53 also stores various programs and data required for caching the operation of electronic device 500 in a system simulation. Processing unit 51, ROM 52, and RAM 53 are interconnected via bus 54. Input / output (I / O) interface 55 is also connected to bus 54. Typically, the following devices can be connected to I / O interface 55: input devices 56 including, for example, touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 57 including, for example, liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 58 including, for example, magnetic tape, hard disk, etc.; and communication devices 59. Communication device 59 allows electronic device 500 to communicate wirelessly or wiredly with other electronic devices to exchange data.

[0140] Although Figure 13 An electronic device 500 with various devices is shown, but it should be understood that it is not required to implement or have all of the devices shown, and the electronic device 500 may alternatively implement or have more or fewer devices.

[0141] For detailed descriptions and technical effects of the electronic device 500, please refer to the above descriptions of the methods for generating the initial verification platform or the target verification platform; these will not be repeated here.

[0142] Figure 14 This is a schematic diagram of a storage medium provided for at least one embodiment of the present disclosure.

[0143] For example, such as Figure 14 As shown, storage medium 600 stores non-transitory computer-readable instructions 610. For example, when the non-transitory computer-readable instructions 610 are executed by a computer, one or more steps in the method for generating an initial verification platform or a method for generating a target verification platform as described above are performed.

[0144] For example, this storage medium 600 can be applied to Figure 12 In the illustrated electronic device 400, for example, storage medium 600 can be memory 420 within the electronic device 400. For example, a description of storage medium 600 can be found here. Figure 12 The corresponding description of the memory 420 in the illustrated electronic device 400 will not be repeated here.

[0145] The following points need to be clarified regarding this disclosure:

[0146] (1) The accompanying drawings of the embodiments of this disclosure only involve the structures involved in the embodiments of this disclosure. Other structures can be referred to the general design.

[0147] (2) Where there is no conflict, features of the same embodiment and different embodiments of this disclosure can be combined with each other.

[0148] The above are merely specific embodiments of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.< / if> < / if> < / if>

Claims

1. A method for generating an initial verification platform, wherein, The initial verification platform includes multiple verification components, which in turn include multiple first verification components. Each of the multiple first verification components includes a common layer and a functional layer. The method for generating the initial verification platform includes: Read template files from the template library; Based on the template file, the common layer and the functional layer of each first verification component are established to obtain the plurality of first verification components. The functional layer of each first verification component is inherited from the common layer. The common layer of each first verification component includes a common sub-component, which is a component shared by the corresponding first verification component and other first verification components among the plurality of first verification components. The functional layer of each first verification component includes a corresponding functional sub-component of the first verification component, and the functional sub-component is configured with configurable parameters.

2. The method for generating the initial verification platform according to claim 1 further includes: The initial verification platform is generated based on the inheritance relationship between the multiple verification components.

3. The method for generating the initial verification platform according to claim 2, wherein, The inheritance relationship includes a first inheritance relationship, and the plurality of verification components include a parent verification component and a child verification component having the first inheritance relationship. The child verification component inherits the attributes of the parent verification component from the parent verification component based on the first inheritance relationship.

4. The method for generating the initial verification platform according to claim 1, wherein, Each of the first verification components also includes a user layer. The method for generating the initial verification platform further includes: Establish the user layer, The user layer inherits from the functional layer, and the user layer has a reserved custom configuration section for users to customize their configurations.

5. The method for generating the initial verification platform according to claim 1, wherein, Each of the first verification components also includes a base layer. The method for generating the initial verification platform further includes: Establish the aforementioned base layer, The common layer inherits from the base layer, and the base layer contains basic sub-components corresponding to the first verification component.

6. The method for generating the initial verification platform according to claim 1, wherein, The plurality of verification components also includes a second verification component that is different from the first verification component. The method for generating the initial verification platform further includes: Establish the second verification component; The initial verification platform is generated based on the inheritance relationship between the plurality of first verification components and the second verification components.

7. The method for generating the initial verification platform according to claim 1, wherein, The initial verification platform includes multiple verification modules, and each of the multiple verification modules includes at least one of the multiple first verification components. The method for generating the initial verification platform further includes: The configurable parameters in the functional sub-components of the at least one first verification component are visualized to obtain a visualization interface corresponding to each verification module.

8. A method for generating a target verification platform, comprising: Obtain the parameter configuration table corresponding to the target verification platform; The initial verification platform generated by the initial verification platform generation method according to any one of claims 1-7 is set using the parameter configuration table to generate the target verification platform.

9. The method for generating a target verification platform according to claim 8, wherein, The parameter configuration table includes target parameters corresponding to the plurality of first verification components. The initial verification platform is configured using the parameter configuration table to generate the target verification platform, including: By using the target parameters to set the configurable parameters in the functional sub-components of the plurality of first verification components, a plurality of target first verification components of the target verification platform are obtained.

10. The method for generating a target verification platform according to claim 9, wherein, The plurality of verification components also includes a second verification component that is different from the first verification component. The method of setting up the initial verification platform using the parameter configuration table to generate the target verification platform further includes: The target verification platform is generated based on the inheritance relationship between the multiple target first verification components and the second verification components.

11. The method for generating a target verification platform according to claim 8, wherein, The initial verification platform includes multiple verification modules, and each of the multiple verification modules includes at least one of the multiple first verification components. Each verification module is provided with a visual interface, which displays configurable parameters from the functional sub-components of at least one first verification component in the corresponding verification module. The step of obtaining the parameter configuration table corresponding to the target verification platform includes: The user sets parameters on the visualization interface to obtain target parameters corresponding to the plurality of first verification components. Based on the target parameters, the parameter configuration table is obtained.

12. An apparatus for generating an initial verification platform, wherein, The initial verification platform includes multiple verification components, which in turn include multiple first verification components. Each of the multiple first verification components includes a common layer and a functional layer. The device for generating the initial verification platform includes: The read module is configured to read template files from the template library; A module is established and configured to build the common layer and the functional layer of each first verification component based on the template file, so as to obtain the plurality of first verification components; The functional layer of each first verification component is inherited from the common layer. The common layer of each first verification component includes a common sub-component, which is a component shared by the corresponding first verification component and other first verification components among the plurality of first verification components. The functional layer of each first verification component includes a corresponding functional sub-component of the first verification component, and the functional sub-component is configured with configurable parameters.

13. The apparatus for generating the initial verification platform according to claim 12, further comprising: The first generation module is configured to generate the initial verification platform based on the inheritance relationship between the multiple verification components.

14. An apparatus for generating a target verification platform, comprising: The acquisition module is configured to acquire the parameter configuration table corresponding to the target verification platform; The second generation module is configured to use the parameter configuration table to set the initial verification platform generated by the generation method according to any one of claims 1-7, so as to generate the target verification platform.

15. An electronic device comprising: processor; Memory, including one or more computer program modules; The one or more computer program modules are stored in the memory and configured to be executed by the processor, and the one or more computer program modules are used to implement the method for generating the initial verification platform according to any one of claims 1-7 or the method for generating the target verification platform according to any one of claims 8-11.

16. A storage medium storing non-transitory computer-readable instructions that, when executed by a computer, implement the method for generating an initial verification platform according to any one of claims 1-7 or the method for generating a target verification platform according to any one of claims 8-11.

Images