UVM-based register access management system and electronic equipment

By introducing general management components and other components into the UVM verification environment, universal access management of registers is solved, and the universality and reusability of register access management in the UVM verification environment is simplified and the verification process is reduced.

CN118917269APending Publication Date: 2024-11-08YISIXIN TECH SHANGHAI CO LTD
View PDF 0 Cites 2 Cited by

Patent Information

Application Number
CN202310505888.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-06
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In a standard UVM verification environment, register access management has different forms of transaction components and is difficult to unify and constrain, resulting in the universality limitation of the verification environment and increasing the repeated workload and error risk of verification engineers.

Method used

Provide a UVM-based register access management system, including general management components, follower components, driver components, bus management components, transaction management components and monitor components, through which common access management of target registers is achieved, generation and verification of general access to target registers General transactions, reduce duplicate encoding, and improve system universality and reusability.

Benefits of technology

The verification environment code for register access is simplified, the risk of errors introduced by repeated encoding is reduced, the learning cost of verification engineers is reduced, and the reusability and reliability of the verification platform is improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118917269A_ABST
    Figure CN118917269A_ABST
Patent Text Reader

Abstract

The invention relates to a UVM-based register access management system and electronic equipment, and the system comprises a general management assembly which is used for configuring system parameters of the system and generating a corresponding general transaction according to a target operation command of a target register; the follower component is used for acquiring and transmitting a general transaction; the driving component is used for generating first driving information according to the general transaction; the bus management component is used for determining a target bus according to the system parameters and connecting and driving the target bus according to the first driving information; the transaction management component is used for determining a corresponding response result after the access to the target register is completed; and the monitor component is used for monitoring the target bus, collecting the first driving information and the response result, and determining a combined result of the first driving information and the response result. According to the embodiment of the invention, the universality of register access management can be improved, the code quantity of a verification environment is simplified, and the repeated workload of verification engineers during development is reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a register access management system and electronic device based on UVM. Background Art

[0002] In the standard Universal Verification Methodology (UVM) verification environment, register access is usually managed using a register model. Although UVM has used common components to help verification engineers implement functions such as register description, access command control management, and command format type conversion, there is still a problem that transaction-like components with different forms and difficulty in constraining exist based on different scenarios. Summary of the invention

[0003] In view of this, the present disclosure proposes a technical solution for a register access management system and an electronic device based on UVM.

[0004] According to one aspect of the present disclosure, a register access management system based on UVM is provided, comprising: a general management component, used to configure system parameters of the system, and generate corresponding general transactions according to target operation commands for target registers, wherein the general transactions are data and information transmitted between different components of the system; a follower component, used to obtain and transfer the general transactions; a driver component, used to generate first driver information according to the general transactions, wherein the first driver information is used to drive a target bus to access a predefined address of the target register; a bus management component, used to determine the target bus according to the system parameters, and to connect and drive the target bus according to the first driver information; a transaction management component, used to determine the corresponding response result after completing the access to the target register; a monitor component, used to monitor the target bus, collect the first driver information and the response result, and determine a merged result of the first driver information and the response result, wherein the merged result is used to return to the general management component for result verification.

[0005] In one possible implementation, the general management component includes: a sequence sub-component and a conversion sub-component; the sequence sub-component is used to obtain the target operation command, send the target operation command to the conversion sub-component, and control the general management component to enter a response waiting state; the conversion sub-component is used to convert the target operation command into the general transaction, and send the general transaction to the sequence sub-component.

[0006] In a possible implementation, the follower component is used to obtain the general transaction from the sequence subcomponent and send the general transaction to the driver component.

[0007] In one possible implementation, the driver component includes: a user input subcomponent; the user input subcomponent is used to obtain a user access command, wherein the user access command is used to access an undefined address of the target register; the driver component is used to generate second driver information according to the user access command, wherein the second driver information is used to drive the target bus to access the undefined address; the bus management component is used to connect and drive the target bus according to the second driver information.

[0008] In a possible implementation, the bus management component is used to configure the required bus interface based on the chip architecture corresponding to the target register.

[0009] In a possible implementation, the general management component also includes: a prediction subcomponent; the monitor component is used to send the merge result to the prediction subcomponent based on UVM transaction-level modeling; the prediction subcomponent is used to verify the result according to the merge result and generate response information corresponding to the access to the target register.

[0010] In a possible implementation, the follower component is used to obtain the response information from the prediction sub-component and send the response information to the sequence sub-component; the sequence sub-component is used to control the general management component to end the response waiting state according to the response information.

[0011] In a possible implementation, the driver component further includes: a synchronous broadcast subcomponent, which is used to obtain the merged result based on the UVM transaction level modeling, and broadcast the merged result to the corresponding verification environment.

[0012] According to one aspect of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to call the instructions stored in the memory to run the above system.

[0013] According to one aspect of the present disclosure, a computer-readable storage medium is provided, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the above system is run.

[0014] According to the register access management system based on UVM of the embodiment of the present disclosure, the system parameters can be configured by using the general management component, so that the adjustment of the system can be realized, and the versatility and reusability of the system can be increased. The general management component can generate corresponding general transactions according to the target operation command of the target register, so as to standardize and unify the description of the register, the control management of the access command, the command, etc. The follower component can obtain the general transaction and pass the general transaction to the driver component. The driver component can generate the first drive information according to the general transaction; the bus management component connects and drives the target bus according to the first drive information, which can reduce the duplication of the verification engineer. After completing the access to the target register, the transaction management component determines the corresponding response result; the monitor component monitors the target bus, collects the first drive information and the response result, and determines the merged result of the first drive information and the response result. The merged result can be used to return to the general management component for result verification, thereby realizing the entire access to the target register and the result verification process, simplifying and standardizing the verification environment code of the register access, reducing the risk of introducing errors due to repeated coding, and reducing the learning cost of the verification engineer.

[0015] It should be understood that the above general description and the following detailed description are exemplary and explanatory only and do not limit the present disclosure. Other features and aspects of the present disclosure will become clear from the following detailed description of exemplary embodiments with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The drawings herein are incorporated into the specification and constitute a part of the specification. These drawings illustrate embodiments consistent with the present disclosure and are used to illustrate the technical solutions of the present disclosure together with the specification.

[0017] Figure 1 A schematic diagram showing a register address mapping according to an embodiment of the present disclosure;

[0018] Figure 2 A block diagram of a register access management system based on UVM according to an embodiment of the present disclosure is shown;

[0019] Figure 3 A structural schematic diagram of a self-built ring bus structure according to an embodiment of the present disclosure is shown;

[0020] Figure 4 A block diagram of an electronic device according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0021] Various exemplary embodiments, features and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. The same reference numerals in the accompanying drawings represent elements with the same or similar functions. Although various aspects of the embodiments are shown in the accompanying drawings, the drawings are not necessarily drawn to scale unless otherwise specified.

[0022] The word “exemplary” is used exclusively herein to mean “serving as an example, example, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.

[0023] The term "and / or" herein is only a description of the association relationship of the associated objects, indicating that there may be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the term "at least one" herein represents any combination of at least two of any one or more of a plurality of. For example, including at least one of A, B, and C can represent including any one or more elements selected from the set consisting of A, B, and C.

[0024] In addition, in order to better illustrate the present disclosure, numerous specific details are given in the following specific embodiments. It should be understood by those skilled in the art that the present disclosure can also be implemented without certain specific details. In some examples, methods, means, components and circuits well known to those skilled in the art are not described in detail in order to highlight the subject matter of the present disclosure.

[0025] Universal Verification Methodology (UVM) is the most popular verification methodology in current chip verification. In the UVM verification environment of standard, register model (register model) is usually used to manage register access. Based on this method, the verification engineer needs to prepare in advance the System Verilog file (RAL) for describing registers derived from the uvm_reg_block class, and the converter (adapter) derived from the uvm_adapter class. Wherein, the converter is used for the type uvm_reg_item used for register access in the UVM verification environment of standard, and the transaction (transaction) class derived from the uvm_sequence_item class is converted, and the transaction class derived from the uvm_sequence_item class is generally the type customized according to the constraints such as the difference of verification platform, the difference of register interface type.

[0026] In the prior art, although the standard UVM verification environment has implemented the functions of register description, access command control management, command format type conversion, etc. through common components, the transaction class derived from the uvm_sequence_item class still has the problem of different forms and difficulty in unified constraints in different application scenarios, resulting in limitations in the versatility of the UVM verification environment.

[0027] On the other hand, because when register access is performed, the program code of actual driving information depends on the corresponding bus type, corresponding to the difference of interface components (interface) in the UVM verification environment. Therefore, the verification platform based on UVM needs to complete the full set of component development from converter to driver (driver), monitor (monitor), thereby causing a large amount of program codes with the same functions in different application environments, increasing the handwritten code amount of verification engineers, and increasing the risk of making mistakes when setting up the verification environment.

[0028] When designing a complex system on chip (SOC), users with different identities such as the central processing unit (CPU) and HOST have different address divisions, and are mounted on registers of different modules on different buses according to different requirements such as high speed and low speed. Therefore, based on the complex design structure of SOC, it is necessary to configure simple, scalable and reliable components on the user side to assist verification engineers in completing the work of register access management.

[0029] Figure 1 A schematic diagram of register address mapping according to an embodiment of the present disclosure is shown. Figure 1 As shown, the CPU can convert the CPU access command into the corresponding bus command through the corresponding CPU address mapping table, and access the on-chip address space through the corresponding system bus, such as the AXI bus; similarly, the HOST / PICE can convert the HOST / PICE access command into the corresponding bus command through the corresponding HOST / PICE address mapping table, and then access the same address space on the chip to be verified. Subsystem 1 and subsystem 2 are mounted on the system bus respectively, where subsystem 2 is connected to N sub-devices in the ring through the main device in the ring and the ring bus structure. Each sub-device in the ring is an independent module, namely, sub-device 0 in the ring, sub-device 1 in the ring, sub-device 2 in the ring to sub-device N in the ring.

[0030] With the above Figure 1 For example, Figure 1 As shown, for the in-ring sub-devices 0 to N in subsystem 2, it is necessary to access and test the registers in the corresponding module-level verification environment (Unit Test, UT), and perform expected functional results based on the values ​​of the registers. Similarly, for subsystems 1 and 2, it is necessary to perform the above-mentioned behaviors in the corresponding integration-level verification environment (Intergration Test, IT); for the system-level verification environment (System Test, ST) corresponding to the CPU and HOST / PICE, it is also necessary to perform the above-mentioned behaviors.

[0031] Therefore, when the verification engineers responsible for the integrated verification environment and the system-level verification environment need to reuse the related functions of register access that have been defined in the module-level verification environment, the verification engineers responsible for UT need to be forward-looking in the construction of the entire verification platform and design UT on the basis of facilitating the functional reuse of IT and ST. However, in actual work, the verification engineers responsible for UT have less relevant work experience than the verification engineers responsible for IT and ST, and it is difficult for them to accurately and comprehensively consider the functional reuse requirements of the entire verification platform.

[0032] The present disclosure embodiment provides a register access management system based on UVM, which can be applied to a UVM-based verification platform to achieve universal management of register access to a design under test (DUT). The register access management system based on UVM provided by the present disclosure embodiment is described in detail below.

[0033] Figure 2 A block diagram of a register access management system based on UVM according to an embodiment of the present disclosure is shown. Figure 2 As shown, the system 200 includes:

[0034] The general management component 201 is used to configure the system parameters of the system 200 and generate corresponding general transactions according to the target operation commands on the target registers, wherein the general transactions are data and information transmitted between different components of the system 200.

[0035] The follower component 202 is used to obtain and transmit the general transaction.

[0036] The driving component 203 is used to generate first driving information according to the general transaction, wherein the first driving information is used to drive the target bus to access a predefined address of the target register.

[0037] The bus management component 204 is used to determine the target bus according to the system parameters, and to connect and drive the target bus according to the first driving information.

[0038] The transaction management component 205 is used to determine the corresponding response result after completing the access to the target register.

[0039] The monitor component 206 is used to monitor the target bus, collect the first drive information and the response result, and determine the merged result of the first drive information and the response result, wherein the merged result is used to return to the general management component 201 for result verification.

[0040] System 200 can be based on a ring bus structure, for example, a self-built ring bus structure composed of an AXI (Advanced eXtensible Interface) bus, a self-built HPI (Host Port Interface) high-speed bus, and a CSR (Configuration and Status Register) bus for directly accessing sub-devices, to achieve universal access management of the target registers of the DUT.

[0041] Figure 3 FIG. 2 is a schematic diagram showing a structure of a self-built ring bus structure according to an embodiment of the present disclosure. Figure 3 As shown, the system bus is connected to the HPI ring bus through the master device. The HPI ring bus can be composed of a self-built HPI high-speed bus and a CSR bus.

[0042] When accessing the target register, the register access command can be transmitted to the master device through the system bus, and the master device is connected to slave device 1, slave device 2, slave device 3 to slave device N through the HPI ring bus. The master device can transmit the register access command to slave device 1 through the HPI ring bus. After receiving the register access command, slave device 1 can determine whether the address of the target register to be accessed matches the register address included on slave device 1 according to the register access command.

[0043] If the address of the target register matches the register address included in slave device 1, the corresponding register on slave device 1 can be accessed, and the access result is returned to the master device through the HPI ring bus, through device 2, device 3 to device N, and then transmitted to the system bus through the master device.

[0044] If the address of the target register does not match the register address corresponding to slave device 1, slave device 1 can transmit the register access command to slave device 2 via the HPI ring bus. After receiving the register access command, slave device 2 can determine whether the address of the target register matches the register address included in slave device 2 according to the register access command, and so on.

[0045] Based on the above ring bus structure, the general management component 201 can obtain the target operation command for the target register of the DUT from the UVM-based verification platform, and convert the target operation command from different forms of uvm_reg_item types to the general transaction of the system 200. Among them, the target operation command can be a command for accessing the target register, as well as a read operation and / or a write operation; the general transaction is a transaction class preset by the system 200, which can be used for transmission between different components of the system 200. The specific form and content of the target operation command and the general transaction can refer to the implementation of the transaction class of the UVM-based verification platform in the relevant technology, and the present disclosure does not make specific limitations on this.

[0046] The general management component 201 can also configure the system parameters of the system 200 based on user needs, thereby increasing the versatility and reusability of the system 200, and enabling verification engineers of UT, IT, and ST to reuse the same test case. The manner in which the general management component 201 configures the system parameters can refer to the implementation methods in the relevant technology, and the present disclosure does not specifically limit this.

[0047] Exemplarily, the general management component 201 can configure system parameters through the Config_reg_model function. Specifically, the Config_reg_model function can include program commands for defining variables related to system parameters such as top_path, slave_map, base_address, and reg_ctrl.

[0048] Wherein, top_path is a string type variable, which can be used to represent the program path from the top layer of the UVM-based verification platform to the system 200; and can be used to perform backdoor access to the target register on the DUT.

[0049] Slave_map is an associative array type variable, which can be indexed by the starting address of each slave device's address segment and constructed with the device identifier (slave_id) of each slave device as the value. It can be used in specific bus protocol application scenarios, such as Advanced High-performance Bus (AHB) or HPI high-speed bus, to provide the converter with the address of the target register to find the corresponding slave device identifier (slave_id).

[0050] base_address is a numeric type variable, which can be used to represent the base address of the address segment to which the entire register block (reg block) of the target register currently belongs.

[0051] reg_ctrl is a structure that can be used to configure the bus interface related parameters of the system 200. For example, the interface_select parameter can select the target bus to be used to access the target register; the burst_en parameter can control the driver component 203 to issue the driver continuously; the use_vip parameter can control the driver component 203 to use VIP instead of driver driver; the post_en parameter can control whether the general management component 201 needs to wait for the RTL response before completing the current access to the target register.

[0052] The general management component 201 will be described in detail later in conjunction with possible implementations of the present disclosure, and will not be elaborated here.

[0053] The follower component 202 is derived from the uvm_sequencer class of the standard UVM verification environment, connects the driver component 203 and the general management component 201, and can be used to receive and transmit general transactions. UVM provides an inverted method of use, allowing a verification engineer to specify the follower component 202 to which the general management component 201 belongs through program code. During the operation of the system 200, the driver component 203 will continue to wait for the follower component 202 to transmit the general transaction. The follower component 202 will be described in detail later in conjunction with the possible implementation of the present disclosure, and will not be repeated here.

[0054] The driver component 203 is derived from the uvm_driver class of the standard UVM verification environment. The general transaction from the follower component 202 can be obtained through the get_next_item function, and the corresponding first driving information is generated according to the general transaction, and then the bus management component 204 is driven to connect to the target bus and access the target register. The specific form and content of the first driving information depends on the type of target bus to be driven. The implementation method in the relevant technology can be referred to, and the present disclosure does not make specific limitations on this. The driver component 203 will be described in detail later in conjunction with the possible implementation methods of the present disclosure, and will not be repeated here.

[0055] The bus management component 204 is used to implement the communication between the system 200 and the DUT, and the chip verification platform based on the UVM verification environment. The bus management component 204 can determine the target bus that needs to be driven when accessing the target register this time according to the system parameters, and can connect and drive the target bus according to the first drive information. Usually, the bus management component 204 is maintained by a senior verification engineer or a verification engineer responsible for ST.

[0056] The member variables of the transaction management component 205 can be a set of self-defined variables used to describe the register operation behavior, which can cooperate with the converter and driver component 203 to complete the generation and driving of the stimulus. Specifically, the transaction management component 205 can be used to determine the corresponding response result after completing the access to the target register. Usually, the transaction management component 205 is maintained by a senior verification engineer or a verification engineer responsible for ST.

[0057] In the process of accessing the target register, the bus management component 204 may access the wrong register address after driving the bus, and return the wrong response result; or, after accessing the register address, only the corresponding response result is returned, and it is impossible to directly determine whether the response result comes from the target register. Therefore, the target bus can be monitored in real time by the monitor component 206, and the first drive information and the response result can be collected, so as to achieve the matching of the first drive information and the response result. The monitor component 206 can also be used to merge and encapsulate the first drive information and the response result, and return the merged result to the general management component 201 for result verification. The monitor component 206 is derived from the uvm_monitor class of the standard UVM verification environment.

[0058] According to the register access management system based on UVM of the embodiment of the present disclosure, the system parameters can be configured by using the general management component, so that the system can be adjusted to increase the versatility and reusability of the system. The general management component can generate corresponding general transactions according to the target operation command of the target register, so as to standardize and unify the description of the register, the control management of the access command, the command, etc. The follower component can obtain the general transaction and pass the general transaction to the driver component. The driver component can generate the first drive information according to the general transaction; the bus management component connects and drives the target bus according to the first drive information, which can reduce the duplication of verification engineers. After completing the access to the target register, the transaction management component determines the corresponding response result; the monitor component monitors the target bus, collects the first drive information and the response result, and determines the merged result of the first drive information and the response result. The merged result can be used to return to the general management component for result verification, thereby realizing the entire access to the target register and the result verification process, simplifying and standardizing the verification environment code of register access, reducing the risk of introducing errors due to repeated coding, and reducing the learning cost of verification engineers.

[0059] In one possible implementation, the general management component 201 includes: a sequence sub-component and a conversion sub-component; the sequence sub-component is used to obtain the target operation command, send the target operation command to the conversion sub-component, and control the general management component 201 to enter a response waiting state; the conversion sub-component is used to convert the target operation command into a general transaction, and send the general transaction to the sequence sub-component.

[0060] With the above Figure 2 For example, Figure 2 As shown, the general management component 201 includes: a sequence sub-component 2011 and a conversion sub-component 2012.

[0061] Specifically, the sequence subcomponent 2011 is derived from the uvm_sequence class of the standard UVM verification environment, and can obtain the target operation command in the UVM-based verification platform through the task do_read / do_write function based on the UVM read and write method, and transmit the target operation command to the conversion subcomponent 2012.

[0062] The conversion subcomponent 2012 is derived from the uvm_adapter class of the standard UVM verification environment, and can convert the target operation command into a corresponding general transaction, and return the general transaction to the sequence subcomponent 2011. The general management component 201 may include a plurality of different conversion subcomponents for realizing the mutual conversion between transaction classes of various different forms. According to the configuration of the system parameters, the corresponding conversion subcomponent 2012 can be determined in the plurality of conversion subcomponents when the target register is currently accessed.

[0063] After the sequence subcomponent 2011 forwards the general transaction to the driver component 203, it can control the general management component 201 to suspend based on the system parameters, enter the response waiting state, wait for the access to the target register to end, and then obtain the next target operation command.

[0064] According to the user's usage requirements, the general management component 201 can be used to modify the system parameters so that the sequence sub-component 2011 will not control the general management component 201 to enter the response waiting state. When the sequence sub-component 2011 forwards the general transaction to the driver component 203, there is no need to wait for the access to the target register to end, and the next target operation command can be directly obtained.

[0065] Exemplarily, the aforementioned post_en variable can be used to determine whether the general management component 201 enters the response waiting state before the access to the target register ends. When post_en=0 is set, before the access to the target register ends, the sequence subcomponent 2011 can control the general management component 201 to enter the response waiting state; when post_en=1 is set, before the access to the target register ends, the sequence subcomponent 2011 can control the general management component 201 not to enter the response waiting state and directly obtain the next target operation command.

[0066] Exemplarily, when constructing the system 200, the provides_response member variable in the conversion subcomponent 2012 can be set to 1, so that after completing the forwarding of the general transaction, the sequence subcomponent 2011 controls the general management component 201 to enter the response waiting state, and the sequence subcomponent 2011 itself will not generate the corresponding response information for controlling the general management component 201 to end the response waiting state. Only after the external response information is input, can the general management component 201 be controlled to end the response waiting state.

[0067] In a possible implementation, the follower component 202 is used to obtain the general transaction from the sequencer component and send the general transaction to the driver component.

[0068] With the above Figure 2 For example, Figure 2 As shown, the follower component 202 is an intermediate node between the general management component 201 and the driver component 203, and is used to transfer the general transaction from the general management component to the driver component 203. Specifically, the verification engineer specifies the corresponding follower component 202 for the sequence subcomponent 2011 through the corresponding program code, so that the follower component 202 can be used to obtain the general transaction from the sequence subcomponent 2011 and send the general transaction to the driver component 203.

[0069] In one possible implementation, the driver component 203 includes: a user input subcomponent; a user input subcomponent, used to obtain a user access command, wherein the user access command is used to access an undefined address of a target register; the driver component 203, used to generate second driver information according to the user access command, wherein the second driver information is used to drive the target bus to access the undefined address; and a bus management component 204, used to connect and drive the target bus according to the second driver information.

[0070] With the above Figure 2 For example, Figure 2 As shown, the driver component 203 also includes a user input subcomponent 2031. The general management component 201 includes a predefined register group, which can be used to store the predefined address of the target register. Using the general management component 201 and the target operation command, only the predefined address of the target register can be accessed. In some application scenarios, it is necessary to access the undefined address of the target register to achieve special usage requirements. Among them, the undefined address can be a meaningless address in the target register. At this time, the user can input the user access command through the user input subcomponent 2031. The specific form and content of the user access command can refer to the implementation method in the relevant technology, and the present disclosure does not make specific limitations on this.

[0071] In addition, the user can also access the predefined address of the target register freely according to actual usage requirements by bypassing the general management component 201 through a user access command.

[0072] After the driver component 203 obtains the user access command through the user input subcomponent 2031, it can generate the corresponding second driver information according to the user access command. The specific form and content of the second driver information depends on the type of target bus to be driven, and can refer to the implementation method in the relevant technology, which is not specifically limited in this disclosure. The bus management component 204 can connect and drive the target bus according to the second driver information, so as to access the target register.

[0073] By generating the first driving information or the second driving information through the driving component 203 and controlling the bus management component 204 to connect and drive the corresponding target bus, the repetitive workload of the verification engineer can be reduced and the usage threshold can be lowered, and the verification engineer does not need to master the driving method of each bus.

[0074] Exemplarily, the driver component 203 may generate corresponding first driver information or second driver information according to the general transaction through the drv_hpi_trans method, control the bus management component to connect and drive the HPI high-speed bus, and access the target register.

[0075] In a possible implementation, the bus management component 204 is used to configure the required bus interface based on the chip architecture corresponding to the target register.

[0076] The bus management component 204 is of interface type, and can be used to implement communication between the system 200 and the DUT based on the interface component in the standard UVM verification environment. Specifically, based on the chip architecture corresponding to the target register, the bus management component 204 can be used to configure the required bus interface, and based on the system parameters, the corresponding target bus is selected in the configured bus interface for connection.

[0077] For example, Figure 2 As shown, based on the chip architecture corresponding to the target register, the corresponding bus interfaces hpi_interface, csr_interface and axi_interface are configured in the bus management component 204. And according to the interface_select parameter in the aforementioned system parameters, the target bus required to access the target register is selected from the hpi_interface, csr_interface and axi_interface bus interfaces.

[0078] In a possible implementation, the general management component 201 also includes: a prediction subcomponent; a monitor component 206, which is used to send the merge result to the prediction subcomponent based on UVM transaction-level modeling; and a prediction subcomponent, which is used to verify the result according to the merge result and generate response information corresponding to the access to the target register.

[0079] With the above Figure 2 For example, Figure 2 As shown, the general management component 201 also includes a prediction subcomponent 2013. The prediction subcomponent 2013 is derived from the uvm_reg_predictor of the standard UVM verification environment and is connected to the monitor component 206. After the monitor component 206 determines the merging result, it can transmit the merging result to the prediction subcomponent 2013 based on the UVM transaction level modeling (TLM). After the prediction subcomponent 2013 receives the merging result, the result verification can be performed according to the merging result. Among them, the specific process of the result verification can refer to the implementation method in the relevant technology, such as the result expectation of the target register, the expected value of the register model is updated, etc., and the present disclosure does not make specific limitations on this.

[0080] Exemplarily, the prediction subcomponent 2013 is connected to the monitor component 206 through the uvm_analysis_port method. After the prediction subcomponent 2013 is started, the sequence information corresponding to the general transaction in the driver component 203 can be copied, the sequence information can be matched with the merged result from the monitor component 206, and then the super.write(item) method can be called to predict the result of the target register.

[0081] After completing the result verification, the prediction subcomponent 2013 can generate response information corresponding to the access target register.

[0082] In a possible implementation, the follower component 202 is used to obtain response information from the prediction subcomponent and send the response information to the sequence subcomponent; the sequence subcomponent is used to control the general management component 201 to end the response waiting state according to the response information.

[0083] The follower component 202 can also be used to obtain response information from the prediction subcomponent 2013, and based on UVM transaction level modeling (TLM), send the response information to the sequence subcomponent 2011. After receiving the response information, the sequence subcomponent 2011 can control the general management component 201 to end the waiting response state and obtain the next target operation command.

[0084] Exemplarily, after completing the result verification, the prediction subcomponent 2013 can call the sqr.put(item) method so that the sequence subcomponent 2011 can obtain the corresponding response information from the follower component 202, thereby controlling the general management component 201 to end the waiting response state.

[0085] After the sequence subcomponent obtains the response information, the merged result can be converted into the uvm_reg_item type again through the conversion subcomponent 2012, and returned to the UVM-based verification platform through the read method, ending the complete target register access and result verification process.

[0086] In a possible implementation, the driver component 203 further includes: a synchronous broadcast subcomponent, which is used to obtain the merged result based on UVM transaction level modeling, and broadcast the merged result to the corresponding verification environment.

[0087] With the above Figure 2 For example, Figure 2 As shown, driver component 203 also includes synchronous broadcast subcomponent 2032. After driver component 203 completes the driving of target bus by the first driving information or the second driving information, it can suspend the completion of waiting for result verification. After result verification is completed, synchronous broadcast subcomponent 2032 can synchronously obtain the merging result from prediction subcomponent 2013 based on UVM transaction level modeling (TLM), and the relevant information of this access to target register. Meanwhile, synchronous broadcast subcomponent 2032 can be based on UVM transaction level modeling (TLM), and the relevant information of the merging result and this access to target register is broadcasted in the form of uvm_reg_item type to the verification platform based on UVM. The user can call the content broadcasted by synchronous broadcast subcomponent 2032 in the target register access process.

[0088] According to the UVM-based register access management system of the embodiment of the present disclosure, the system parameters can be configured using the general management component, so that the system can be adjusted and the versatility and reusability of the system can be increased. The general management component can generate corresponding general transactions based on the target operation command of the target register, thereby standardizing and unifying the description of the register, the control management of the access command, and the command. The follower component can obtain the general transaction and pass the general transaction to the driver component. The driver component can generate the first drive information based on the general transaction; the bus management component connects and drives the target bus based on the first drive information, which can reduce the duplication of verification engineers. After completing the access to the target register, the transaction management component determines the corresponding response result; the monitor component monitors the target bus, collects the first drive information and the response result, and determines the merged result of the first drive information and the response result. The merged result can be used to return to the general management component for result verification, thereby realizing the entire access to the target register and the result verification process, simplifying and standardizing the verification environment code for register access, reducing the risk of introducing errors due to repeated coding, and reducing the learning cost of verification engineers; and being able to broadcast the merged result obtained from the target register access while completing the automatic result verification, so as to facilitate certain special verification environments that need to perform specific functions when certain register accesses occur.

[0089] In addition, the present disclosure also provides a UVM-based register access management electronic device, a computer-readable storage medium, and a program, all of which can be used to implement any UVM-based register access management system provided by the present disclosure. The corresponding technical solutions and descriptions are referred to in the corresponding records of the method part and will not be repeated here.

[0090] The embodiment of the present disclosure also provides a computer-readable storage medium on which computer program instructions are stored, and the computer program instructions implement the above method when executed by a processor. The computer-readable storage medium can be a volatile or non-volatile computer-readable storage medium.

[0091] The embodiment of the present disclosure further proposes an electronic device, comprising: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to call the instructions stored in the memory to run the above-mentioned system 200.

[0092] The embodiment of the present disclosure also provides a computer program product, including a computer-readable code, or a non-volatile computer-readable storage medium carrying the computer-readable code. When the computer-readable code runs in a processor of an electronic device, the processor in the electronic device runs the above-mentioned system 200.

[0093] Figure 4 A block diagram of an electronic device according to an embodiment of the present disclosure is shown. Figure 4 , the electronic device 1900 can be provided as a server or a terminal device. Figure 4 , the electronic device 1900 includes a processing component 1922, which further includes one or more processors, and a memory resource represented by a memory 1932 for storing instructions executable by the processing component 1922, such as an application. The application stored in the memory 1932 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 1922 is configured to execute instructions to perform the above method.

[0094] The electronic device 1900 may also include a power supply component 1926 configured to perform power management of the electronic device 1900, a wired or wireless network interface 1950 configured to connect the electronic device 1900 to a network, and an input / output (I / O) interface 1958. The electronic device 1900 may operate based on an operating system stored in the memory 1932, such as a Microsoft Server operating system (Windows Server 2003). TM ), a graphical user interface operating system launched by Apple (Mac OSX TM ), a multi-user, multi-process computer operating system (Unix TM ), a free and open source Unix-like operating system (Linux TM ), an open source Unix-like operating system (FreeBSD TM ) or similar.

[0095] In an exemplary embodiment, a non-volatile computer-readable storage medium is also provided, such as a memory 1932 including computer program instructions, which can be executed by the processing component 1922 of the electronic device 1900 to perform the above method.

[0096] The present disclosure may be a system, a method and / or a computer program product. The computer program product may include a computer-readable storage medium carrying computer-readable program instructions for causing a processor to implement various aspects of the present disclosure.

[0097] Computer readable storage medium can be a tangible device that can hold and store instructions used by an instruction execution device. Computer readable storage medium can be, for example, (but not limited to) an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. More specific examples (non-exhaustive list) of computer readable storage medium include: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disk read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device, for example, a punch card or a convex structure in a groove on which instructions are stored, and any suitable combination thereof. The computer readable storage medium used here is not interpreted as a transient signal itself, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagated by a waveguide or other transmission medium (for example, a light pulse by an optical fiber cable), or an electrical signal transmitted by a wire.

[0098] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, optical fiber transmissions, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in the computer-readable storage medium in each computing / processing device.

[0099] The computer program instructions for performing the operation of the present disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages, such as Smalltalk, C++, etc., and conventional procedural programming languages, such as "C" language or similar programming languages. Computer-readable program instructions may be executed completely on a user's computer, partially on a user's computer, as an independent software package, partially on a user's computer, partially on a remote computer, or completely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., using an Internet service provider to connect via the Internet). In some embodiments, an electronic circuit, such as a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), may be customized by utilizing the state information of the computer-readable program instructions, and the electronic circuit may execute the computer-readable program instructions, thereby realizing various aspects of the present disclosure.

[0100] Various aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer-readable program instructions.

[0101] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processor of the computer or other programmable data processing device, a device that implements the functions / actions specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0102] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operating steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0103] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to multiple embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of the module, program segment or instruction includes one or more executable instructions for realizing the specified logical function. In some alternative implementations, the function marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or action, or can be implemented with a combination of special hardware and computer instructions.

[0104] The computer program product may be implemented in hardware, software or a combination thereof. In one optional embodiment, the computer program product is embodied as a computer storage medium, and in another optional embodiment, the computer program product is embodied as a software product, such as a software development kit (SDK) and the like.

[0105] The above description of various embodiments tends to emphasize the differences between the various embodiments. The same or similar aspects can be referenced to each other, and for the sake of brevity, they will not be repeated herein.

[0106] Those skilled in the art will appreciate that, in the above method of specific implementation, the order in which the steps are written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of the steps should be determined by their functions and possible internal logic.

[0107] The embodiments of the present disclosure have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The selection of terms used herein is intended to best explain the principles of the embodiments, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A register access management system based on UVM, characterized in that, include: A general management component, used to configure system parameters of the system and generate corresponding general transactions according to target operation commands on target registers, wherein the general transactions are data and information transmitted between different components of the system; A follower component, configured to obtain and transmit the general transaction; A driver component, configured to generate first driver information according to the general transaction, wherein the first driver information is used to drive a target bus to access a predefined address of the target register; A bus management component, configured to determine the target bus according to the system parameters, and to connect and drive the target bus according to the first driving information; A transaction management component, configured to determine a corresponding response result after completing access to the target register; A monitor component is used to monitor the target bus, collect the first drive information and the response result, and determine a merged result of the first drive information and the response result, wherein the merged result is used to return to the general management component for result verification.

2. The system according to claim 1, characterized in that The general management component includes: a sequence subcomponent and a conversion subcomponent; The sequence subcomponent is used to obtain the target operation command, send the target operation command to the conversion subcomponent, and control the general management component to enter a response waiting state; The conversion subcomponent is used to convert the target operation command into the general transaction and send the general transaction to the sequence subcomponent.

3. The system according to claim 2, characterized in that The follower component is used to obtain the general transaction from the sequencer component and send the general transaction to the driver component.

4. The system according to any one of claims 1 to 3, characterized in that: The driving component includes: a user input subcomponent; The user input subcomponent is used to obtain a user access command, wherein the user access command is used to access an undefined address of the target register; The driving component is used to generate second driving information according to the user access command, wherein the second driving information is used to drive the target bus to access the undefined address; The bus management component is used to connect and drive the target bus according to the second driving information.

5. The system according to any one of claims 1 to 3, characterized in that: The bus management component is used to configure the required bus interface based on the chip architecture corresponding to the target register.

6. The system according to claim 3, characterized in that The general management component also includes: a prediction subcomponent; The monitor component is used to send the merged result to the prediction subcomponent based on UVM transaction level modeling; The prediction subcomponent is used to perform result verification according to the merging result and generate response information corresponding to the current access to the target register.

7. The system according to claim 6, characterized in that The follower component is used to obtain the response information from the prediction subcomponent and send the response information to the sequence subcomponent; The sequence subcomponent is used to control the general management component to end the response waiting state according to the response information.

8. The system according to claim 6, characterized in that The drive assembly further comprises: The synchronous broadcast subcomponent is used to obtain the merged result based on the UVM transaction level modeling, and broadcast the merged result to the corresponding verification environment.

9. An electronic device, characterized in that: include: processor; a memory for storing processor-executable instructions; The processor is configured to call the instructions stored in the memory to run the system described in any one of claims 1 to 8.

10. A computer-readable storage medium having computer program instructions stored thereon, characterized in that: When the computer program instructions are executed by a processor, the system according to any one of claims 1 to 8 is executed.

Citation Information

Cited By

  • Bus data processing method and system and electronic equipment

    CN122547721A

  • Bus data processing method, system and electronic device

    CN122547721B