Master-slave UVM verification system, method and device
Through the master-slave UVM verification system, the upstream and downstream modules and register configurations of the vector computing unit are simulated, and packet transmission is realized that more in line with the master-slave protocol is solved, and the existing UVM verification system structure does not conform to the vector computing unit logic is improved. The system is reusable and convenient for maintenance.
Patent Information
- Application Number
- CN202410620341.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-05-20
- Publication Date
- 2024-12-06
AI Technical Summary
The existing UVM verification system structure does not conform to the master-slave protocol logic of the vector computing unit, resulting in unclear logical relationships between signals and difficult to maintain, and the logic of the verification system is messy and poorly readable, and it is difficult to mislocate and modify.
The master-slave UVM verification system is adopted, and the upstream module of the vector computing unit is simulated by the main agent component to write and read data, and the downstream module of the proxy component to receive and send data. The register configuration agent component uses the APB bus protocol to configure the register to realize The excitation infusion of the packet transmission protocol enhances the logical standardization of the system.
The verification system is logically more in line with the vector computing unit transmission protocol, which improves the system's reusability and the convenience of error positioning and modification, and reduces the difficulty of replacing the verification system builder.
Smart Images

Figure CN119089834A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of functional verification, and in particular relates to a master-slave UVM verification system, method and equipment. Background Art
[0002] With the vigorous development of the chip industry, in order to meet the development of intelligence in today's society, various semiconductor companies have designed many IP cores of AI chips with complex functions. These AI chip cores often have many functions, and most of them are based on fixed master-slave protocol signal associations in terms of interfaces, rather than simple single signal input and output.
[0003] In terms of verification, verification methodology has flourished. In the field of verification, a complete verification process from chip specification analysis, verification point decomposition to platform construction has been proposed to ensure the correctness of the verified chip function. However, in many verification methodologies, including the mainstream UVM verification methodology, the structural template of the verification system uses two modules, output_agent (output encapsulation) and input_agent (input encapsulation), to build the verification system. Input_agent is only responsible for the input signal part of the platform input to the vector computing unit (module to be tested), and output_agent is only responsible for the output signal part of the platform output to the vector computing unit (module to be tested). This means that there is only a monitor that receives the signal of the vector computing unit in the output_agent, and there is no sound driver (driver) and sequencer (sequence arbitrator) like in the input_agent. Although such a verification system structure can complete basic verification work, it does not conform to the logic of the master-slave protocol of the vector computing unit, weakens the logical relationship between signals, and makes the platform difficult to maintain.
[0004] Moreover, all outputs of the existing verification system structure are written in input_agent (input encapsulation), which is logically messy and has poor readability, making it difficult to locate errors when the verification system needs to be modified, and when the verification system builder is replaced midway, it brings great difficulties to the successor.
[0005] Therefore, there is an urgent need for a verification system that can logically better fit the vector computing unit transmission protocol and the interaction environment of upstream and downstream modules. Summary of the invention
[0006] The present invention aims to provide a master-slave UVM verification system, method and device, which are more logically consistent with the verification system of the interactive environment of the vector computing unit transmission protocol and the upstream and downstream modules, have high reusability and are convenient for error location and modification.
[0007] Specifically, on the one hand, the present invention provides a master-slave UVM verification system, which serves as a master-slave machine of a vector computing unit, realizes the functions of sending a data packet to the vector computing unit, receiving a data packet of the vector computing unit, and configuring a register, and completes the data packet stimulus injection according to the data packet transmission protocol of the vector computing unit through the verification IP interface between the vector computing unit; the master-slave UVM verification system includes a master agent component, a slave agent component, and a register configuration agent component;
[0008] The main agent component simulates the process of the upstream module of the vector computing unit writing data to the vector computing unit, and performs the input of the fusion data of the read input and the input of the read input response data;
[0009] The slave proxy component simulates a downstream module of the vector computing unit, receives characteristic data of a write output mode of the vector computing unit, sends a write output response to the vector computing unit, and receives a read request from the vector computing unit;
[0010] The register configuration agent component simulates register configuration and adopts APB bus protocol to configure the registers of the vector computing unit.
[0011] Further, the master agent component, the slave agent component and the register configuration agent component each contain three sub-components: a sequence arbitrator, a driver and a monitor;
[0012] The sequence arbiter receives the data packet stimulus for verification generated by the sequence generator, and transmits it to the driver of the corresponding master agent component, slave agent component or register configuration agent component after arbitration;
[0013] The driver inputs the data packet stimulus arbitrated by the sequence arbiter into the vector computing unit through an interface interacting with the vector computing unit according to the vector computing unit transmission protocol requirements;
[0014] The monitor monitors the input and output of data signals between the corresponding master agent component, slave agent component or register configuration agent component and the vector computing unit, and simultaneously transmits the relevant data signals input to the vector computing unit to the reference model, and transmits the relevant data signals output from the vector computing unit to the scoreboard.
[0015] Further, after the register configuration agent component completes the configuration of the register data, the master agent component and the slave agent component run in parallel.
[0016] Furthermore, the data packet transmission protocol includes three types of data packet transmission protocols: read input, write input, and write output; the verification IP interface controls the input and output of the vector calculation unit; the output of the verification IP interface adopts the write output data packet transmission protocol, and the input of the verification IP interface includes write input and read input, which are used to input image feature values and fusion data respectively; write input is the image feature data of the upstream module written into the vector calculation unit.
[0017] Furthermore, the writing input is that the main agent component writes the image feature data into the vector calculation unit, and the process includes:
[0018] The main agent component transmits three types of data packet stimuli, namely, a channel request for writing input data, channel data, and a channel data address, to an interface interacting with the vector computing unit according to a data packet transmission protocol;
[0019] Receives the channel response of the write input data returned by the vector computing unit.
[0020] Further, the write output is that the slave proxy component, as a downstream module of the vector calculation unit, receives the image feature data written by the vector calculation unit and sends the response data of the write output to the vector calculation unit, and the process includes:
[0021] After receiving the channel request for writing output data sent by the vector calculation unit and the number of image feature data corresponding to the channel request, the proxy component sends a channel response with the same number of data to the vector calculation unit.
[0022] Furthermore, the read input is to input the fused data into the vector computing unit, which is completed by the combination of the master agent component and the slave agent component, and the process includes:
[0023] After receiving the read input request sent by the vector calculation unit, the slave agent component injects the response signal data into the vector calculation unit; the master agent component injects the channel address and channel data of the read input data into the vector calculation unit.
[0024] On the other hand, the present invention also provides a master-slave UVM verification method, which is implemented by the above-mentioned master-slave UVM verification system, including:
[0025] Re-instantiate each agent component and its driver, monitor and sequence arbiter, connect the components, and configure the register model;
[0026] Execute various time-consuming phases, then start the sequence generator to generate data packet excitations and send them to the master agent component and the slave agent component; the master-slave agent component transmits these data packet excitations to the vector calculation unit according to the relevant interface protocol to complete the injection of data excitations; the same data packet excitations as those injected into the vector calculation unit are transmitted to the reference model for the same data calculation, and then output to the scoreboard, and compared with the data output by the vector calculation unit in the scoreboard to determine whether the vector calculation unit is working correctly;
[0027] End the simulation run and output the log.
[0028] In yet another aspect, the present invention further provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program implements the steps of the above method when executed by a processor.
[0029] In yet another aspect, the present invention further provides a computer program product, comprising a computer program, wherein the computer program implements the steps of the above method when executed by a processor.
[0030] The beneficial effects of the master-slave UVM verification system, method and device of the present invention are as follows:
[0031] The master-slave UVM verification system, method and device of the present invention, the verification system no longer divides the agent components (agent) by input / output, but divides the agent components by master / slave. The upstream module of the vector computing unit is simulated by the master agent component (master_agent) to interact with the vector computing unit, including output request (req), data (data), address (hdr), and input response (resp); the downstream module of the vector computing unit is simulated by the slave agent component (slave_agent) to interact with the vector computing unit, including input request (req), data (data), address (hdr), and output response (resp), so that the verification system is more logically consistent with the vector computing unit transmission protocol and the interactive environment of the upstream and downstream modules.
[0032] The master-slave UVM verification system, method and equipment of the present invention can enhance the logical normalization of the UVM verification system. For all IPs on a soc, there are modules with the same data packet structure and transmission protocol specification, and the master-slave UVM verification system of the present invention has higher reusability. For example, in the existing UVM verification system, IP basically must interact with other IPs for data, and there is data interaction, that is, there is a master-slave relationship of data transmission and reception. If you want to change the IP of verification, you need to modify the verification system structure. And if the master-slave UVM verification system of the present invention wants to change the IP of verification, it is only necessary to change the data packet structure sent by the UVM verification system and the interactive logical relationship in the master-agent component and the slave-agent component, without the need to modify the verification system structure, to achieve reusability.
[0033] The master-slave UVM verification system, method and device of the present invention are more logically in line with the specification design of the vector computing unit. Starting from the transmission protocol design idea of the vector computing unit specification, on the premise of understanding the vector computing unit specification, the master-slave UVM verification system is designed according to the transmission protocol of transmission and reception. When a successor modifies the platform, according to the master-slave relationship of the platform, errors in compilation or receiving and sending logic can be found and modified in the master agent component for input errors, and output errors can be modified in the slave agent component. BRIEF DESCRIPTION OF THE DRAWINGS
[0034] Figure 1 Schematic diagram of a system according to an embodiment of the present invention.
[0035] Figure 2 It is a schematic diagram of an IP interface according to an embodiment of the present invention.
[0036] Figure 3 yes Figure 2 Write output timing diagram in the external interface.
[0037] Figure 4 yes Figure 2 Write input timing diagram in the external interface.
[0038] Figure 5 yes Figure 2 Read input timing diagram of the external interface in .
[0039] Figure 6 It is a schematic diagram of the verification process of an embodiment of the present invention. DETAILED DESCRIPTION
[0040] The present invention is further described in detail below in conjunction with embodiments and with reference to the accompanying drawings.
[0041] One embodiment of the present invention is a master-slave UVM verification system, which is a verification system architecture developed based on verifying a vector computing unit (i.e., DUT) hardware accelerator. Figure 1 shown.
[0042] The vector calculation unit is a verified object in the master-slave UVM verification system of the present invention, and its functions can be analyzed from two aspects: interface function and data processing function.
[0043] The verification IP interface of DUT in the master-slave UVM verification system of the present invention controls the input and output of DUT. The interface types are as follows: Figure 2 shown.
[0044] Verify that the IP interface output uses the write output protocol, such as Figure 3 As shown. There are two types of output modes, namely broadcast output and non-broadcast output. The broadcast output mode uses a computing unit or storage unit of a lower layer in the on-chip network as the output object, such as output to a routing node; the output destination register is configured as the output layer number. Among them, the layer number, number of computing units, and number of storage units of the output layer are different, the register content configured by the vector computing unit is different, and the number of response data returned by the lower layer to the vector computing unit is also different. The non-broadcast output mode is an output mode that outputs to a single downstream module (such as a computing unit and a storage unit); the output destination register is configured as the output unit module, that is, the ID number of the downstream module.
[0045] Verifying IP interface input functions is closely related to data processing functions, including write input (such as Figure 4 as shown) and read input (as Figure 5 As shown in the figure, they are used to input image feature values and fusion data respectively.
[0046] The data processing of the vector calculation unit mainly includes four data processing operations: fusion, activation, pooling, and filling of feature maps, and each of them can be controlled whether to be enabled, but they are strictly executed in order. Among them, the activation operation includes the Clamp_ReLU activation method and the Leaky_ReLU activation function method. Pooling processing includes three pooling methods, namely maximum pooling, minimum pooling, and mean pooling. The side length of the pooled sliding window is configured to be greater than the step length to prevent data omission, and the step length and side length of the sliding window are within 5. The step length refers to the number of skipped data, and the side length of the sliding window refers to the side length of the matrix formed by the sliding window.
[0047] The master-slave UVM verification system of the present invention is applicable to the above-mentioned vector computing unit, and different forms of incentives are sent by the three agent components of the master agent component (master_agent), the slave agent component (slave_agent) and the register configuration agent component (apb_agent), satisfying the injection incentive requirements and completing the verification. Specifically, the master-slave UVM verification system of the present invention acts as the host (upstream module) and the slave (downstream module) of the vector computing unit, realizing the functions of sending data packets to the vector computing unit, receiving data packets of the vector computing unit and configuring registers, and completing the injection of data packets incentives according to the data packet transmission protocol of the vector computing unit through the verification IP interface between the vector computing unit. Wherein the data packet transmission protocol includes three types of data packet transmission protocols of read input, write input and write output, and the incentive injection work of the three types of data packet transmission protocols is completed by designing the master and slave agent components according to the three types of data packet transmission protocols.
[0048] like Figure 1 As shown, the UVM verification system structure of the present invention is designed according to the needs of the vector computing unit, wherein the top layer is the system environment (environment), comprising three agent components (agent) for simulating the interface protocol: a register configuration agent component (apb_agent), a master agent component (Master_agent) and a slave agent component (Slave_agent).
[0049] The three agent components used to simulate the interface protocol, the master agent component (Master_agent), the slave agent component (Slave_agent) and the register configuration agent component (apb_agent), have different functions. The master agent component simulates the process of the upstream module of the vector computing unit writing data to the vector computing unit, and injects the fusion data of the read input and the read input response data. The slave agent component simulates the downstream module of the vector computing unit, receives the characteristic data of the write output mode of the vector computing unit, sends the write output response to the vector computing unit, and receives the read request of the vector computing unit. The register configuration agent component simulates the register configuration and uses the APB (Advanced PeripheralBus) bus protocol to configure the register of the vector computing unit.
[0050] Each agent component contains three subcomponents: driver, monitor, and sequencer. The sequencer generates data packet stimulus for the test case to be verified. The data packet queue of the test case is arbitrated by the sequencer and passed to the driver of the corresponding master agent component, slave agent component or register configuration agent component. The driver transmits the data packet stimulus arbitrated by the sequencer according to the DUT interface transmission protocol requirements (such as Figures 3 to 5 The timing shown in FIG. 1 is a timing sequence of a vector computing unit (shown in FIG. 1 ) and a vector computing unit (shown in FIG. 1 ). The timing sequence of the vector computing unit (shown in FIG. 1 ) is a timing sequence of a vector computing unit (shown in FIG. 1 ) and a timing sequence of ...
[0051] The main function of the master agent component (Master_agent) is to serve as the upstream module of the vector computing unit, send the image feature data of the write input mode, and receive the corresponding response returned by the vector computing unit. That is, the master agent component (Master_agent) simulates the process of the upstream module of the vector computing unit to write data to the vector computing unit, and is responsible for the input of the fusion data of the read input and the input of the read input response data. The master agent component (Master_agent) includes three sub-components: the master driver (master_driver), the master monitor (master_monitor), and the master sequence arbitrator (master_sequencer).
[0052] The timing of the write input process is as follows Figure 4 As shown. Writing input is the main agent component (upstream module) writing image feature data into the vector calculation unit. The ready signal in the data transmission process defaults to 1. Figure 4 The timing diagram omits the ready signal. Each interface channel transmits data independently of each other. The write input process includes:
[0053] The main agent component transmits three types of data packet stimuli, namely, the channel request for writing input data (channel_in_req, where in indicates that the data packet enters the DUT), channel data (channel_in_data), and channel data address (channel_in_data_hdr), to the interface that interacts with the vector computing unit according to the data packet transmission protocol. After the upstream module issues a write data request (i.e., the write input channel request channel_in_req), the data channel follows and issues the same number of image feature data as the request. The upstream module waits for and receives the channel response (channel_out_resp) of the write input data returned by the vector computing unit, completing a write input operation.
[0054] Specifically, the main driver inputs the data packet excitation in the main sequence arbitrator into the DUT according to the protocol requirements of the data packet write input, and the three types of data packet excitations of the channel request (channel_in_req), channel data (channel_in_data), and channel data address (channel_in_data_hdr) of the write input are passed to the interface (interface) interacting with the DUT. The main monitor (master_monitor) monitors the input and output signals of the write input process between the UVM verification system and the DUT, and transmits the relevant signals (channel request, channel data, channel data address) to the reference model (reference mode) outside the proxy component. The main sequence arbitrator (master_sequencer) passes the write input related data packet excitation generated by the main sequence generator (master_sequence) to the main driver (master_driver), which plays the role of arbitration.
[0055] After the register configuration agent component (apb_agent) completes the configuration of the register data, the master agent component (Master_agent) and the slave agent component (Slave_agent) run in parallel.
[0056] The instantiation of the driver and sequencer in the agent component generally depends on the requirements. If there are request and response signals in the transmission protocol of the DUT's external interface, all of them need to be instantiated; if only the one-way acceptance of the verification system is required, the driver and sequencer do not need to be instantiated. The general UVM verification system usually distinguishes between input and output agent components (agent), and the agent component input to the UVM verification system only instantiates the monitor (monitor).
[0057] In this embodiment, the master agent component (Master_agent) meets the conditions of both outputting stimuli and receiving data, so the master driver (master_driver) and the master sequence arbiter (master_sequencer) of the master agent component (Master_agent) are instantiated as needed.
[0058] In this embodiment, the main function of the slave agent component (Slave_agent) is to serve as a downstream module of the DUT, receive image feature data in the write output mode, and send corresponding response data to the vector calculation unit.
[0059] The slave agent component contains three subcomponents: slave driver (slave_driver), slave monitor (slave_monitor), and slave sequence arbitrator (slave_sequencer). The slave agent component meets the conditions of both outputting stimulus and receiving data, so the slave driver (slave_driver) and slave sequence arbitrator (slave_sequencer) of the slave agent component should be instantiated as needed.
[0060] The timing of the write output process is as follows Figure 3 As shown in the figure. After the DUT completes data inference, the output is to output the image feature data to the next module. The slave proxy component, as the downstream module of the vector calculation unit, receives the image feature data written by the vector calculation unit and sends the response data of the write output to the vector calculation unit. The write output process includes:
[0061] After receiving the channel request (channel_out_req, where out indicates that the data packet is output by the DUT) for writing output data sent by the vector computing unit from the proxy component (downstream module) and the image feature data with the corresponding number of inferences completed as the channel request, the same number of channel responses are sent to the vector computing unit.
[0062] Specifically, the slave driver (slave_driver) inputs the data packet stimulus from the slave sequence arbitrator (slave_sequencer) into the DUT according to the protocol requirements of the data packet write input, mainly the channel response (channel_in_resp, where in means that the data packet enters the DUT) data packet stimulus, and passes it to the interface (interface) that interacts with the DUT. After the slave monitor (slave_monitor) monitors the three types of data packet stimulus received for write output, namely, the channel request (channel_out_req), channel data (channel_out_data), and channel data address (channel_out_data_hdr), the data packet stimulus is transmitted to the scoreboard (checker / scoreboard) outside the slave agent component for data comparison. The role of the slave sequence arbitrator (slave_sequencer) is to pass the relevant data packet stimulus (i.e., channel data and channel address data packet stimulus) generated by the sequence generator (slave_sequence) to the slave driver (slave_driver) to play the role of arbitration.
[0063] The working mode of read input is used for inputting fused data into the vector computing unit, and the vector computing unit at the downstream sends a read request to the UVM verification system at the upstream, and the UVM verification system receives the read request and responds to the response of the same number of the vector computing unit. After the response is sent, the UVM verification system gives the data of the same number of the request. In the master-slave verification system of the present invention, the read input process is completed by the combination of the master agent component master_agent and the slave agent component slave_agent, which is specifically:
[0064] The channel request (channel_out_req, where out means that the data packet is sent from DUT) of the read input protocol is sent by DUT, and then the UVM verification system gives DUT the channel response signal (channel_in_resp, where in means that the data packet enters DUT) of the read input, and the UVM verification system pours the channel address (channel_in_data_hdr) and channel data (channel_in_data) of the read input into DUT to complete the read input work. Therefore, the channel response signal (channel_in_resp) data packet stimulus of the read input is poured into DUT by the slave agent component, and the channel data and channel address data packet stimulus is poured into DUT by the master agent component.
[0065] The timing of the read input working process is as follows Figure 5 As shown, the process includes:
[0066] After receiving the read input request sent by the vector calculation unit, the slave agent component injects the response signal data into the vector calculation unit; the master agent component injects the channel address and channel data of the read input data into the vector calculation unit.
[0067] The steps for building the master-slave authentication system of the present invention are as follows:
[0068] 1. Build an IP interface for interconnection between the UVM verification system and the DUT being verified, and establish a modport interface in the IP interface to control the interface direction.
[0069] The IP interface should include all external interfaces of the vector computing unit to be verified, which is used for interconnection between the master-slave UVM verification system and the vector computing unit, that is, the IP interface verified by the master-slave UVM verification system of the present invention, through which three transmission protocols of write input, write output and read input are realized. The interface types are as follows: Figure 2 As shown. The amount of data transmitted between the upstream and downstream modules through the peer-to-peer (P2P) interface. Taking the input data request signal req as an example, when the maximum number of unprocessed reqs received by the DUT is 5, p2p_out_req_valid pulls up 5 clocks, and the downstream module also feeds back a high level of five clocks to p2p_in_req_ready, so that in_req can input a maximum of 5 data at a time, as shown in Figure 3 to Figure 5 shown.
[0070] 2. Create a data packet according to the verified data format of the vector computing unit, and create a sequence generator (sequence) component and a virtual sequence generator (virtual_sequence) component to generate data packet excitation.
[0071] The sequence generator of the master-slave verification system of the present invention includes three components: a master sequence generator (master_sequence), a slave sequence generator (slave_sequence), and an apb sequence generator (apb_sequence). The master sequence generator generates data packet stimuli for write input, as well as data packet stimuli for DUT data input and response input during read input. The slave sequence generator generates data packet stimuli for write output and receives request data packet stimuli for read input; the apb sequence generator generates configuration APB bus data; finally, the three data packets generated by the master sequence generator, the slave sequence generator, and the apb sequence generator are called after arbitration by the virtual sequence arbitrator in the corresponding proxy component.
[0072] The creation process of the sequence generator component is:
[0073] 2-1) Create a new class that inherits from uvm_sequence.
[0074] 2-2) Implement the body() method, which describes the transaction generation logic, including the constraints between the data packet fields (the constraints vary depending on the DUT protocol being verified). Some initialization operations can be performed in the pre_body() method.
[0075] 3. Create corresponding base class components of sequencer component and virtual_sequencer component for arbitration of data packets.
[0076] The process of establishing a sequencer is as follows:
[0077] 3-1) Create a new class that inherits from uvm_sequencer.
[0078] 3-2) Implement the constructor and pass parameters as needed. Implement transaction generation and distribution logic in the get_next_item() method; start the execution of a transaction in the start_item() method.
[0079] 4. Create a base class for the driver component for data driving.
[0080] According to the master-slave structure, the master driver (master_driver) and the slave driver (slave_driver) are established. The master driver (master_driver) is mainly responsible for simulating the timing logic in the write input process, and is responsible for the input of DUT data and response in the read input process. The slave driver (slave_driver) is mainly responsible for simulating the timing logic in the write output process, and is responsible for the input of DUT requests in the read input.
[0081] 5. Establish the monitor base class to transfer interface information.
[0082] According to the master-slave structure, a master monitor (master_monitor) is established, which is mainly responsible for the response timing logic during the process of receiving write input. A slave monitor (slave_monitor) is established, which is mainly responsible for the timing logic during the process of receiving write output.
[0083] 6. Create the master agent component (master_agent) and the slave agent component (slave_agent), and instantiate their internal components, including the driver, monitor, and sequencer.
[0084] 7. Establish an agent component related to register configuration, namely, a register configuration agent component (apb_agent). Usually, the APB bus protocol is used to configure and build apb_agent.
[0085] 8. Establish register model, checker, reference model, and coverage model components to complete the construction of the verification system.
[0086] like Figure 6 As shown, the master-slave UVM verification system operation process of the present invention is as follows:
[0087] Verify that the system starts up and uses the build phase to re-instantiate each agent component and its driver, monitor, and sequence arbitrator (such as Figure 1 As shown in Figure 1, connect the components in the connect phase and configure the register model. After completing the preliminary preparations, start the simulation.
[0088] During the simulation, various time-consuming phases (including run_phase and its 12 parallel phases, such as main_phase) are mainly executed. Then the sequence generator is started to generate data packet stimuli and sent to various agent components (master agent component master_agent, slave agent component slave_agent). The master-slave agent components transmit these data packet stimuli to the DUT according to the relevant interface protocols (i.e. write input, write output, read input) to complete the injection of data packet stimuli. The same data packet stimuli injected into the DUT are passed to the reference model (reference mode) for the same data calculation, output to the scoreboard, and compared with the data output by the vector calculation unit in the scoreboard to determine whether the DUT is working correctly.
[0089] Finally, the simulation ends, that is, the run phase and its parallel phases end, and the log is printed for log output.
[0090] The master-slave UVM verification system, method and device of the present invention, the verification system no longer divides the agent components (agent) by input / output, but divides the agent components by master / slave. The upstream module of the DUT is simulated by the master agent component (master_agent) to interact with the DUT, including output request (req), data (data), address (hdr), and input response (resp); the downstream module of the DUT is simulated by the slave agent component (slave_agent) to interact with the DUT, including input request (req), data (data), address (hdr), and output response (resp), so that the verification system is more logically consistent with the DUT transmission protocol and the interactive environment of the upstream and downstream modules.
[0091] The master-slave UVM verification system, method and equipment of the present invention can enhance the normalization of the verification system in logic. For all IPs on a soc, there are modules with the same data packet structure and transmission protocol specification, and the master-slave UVM verification system of the present invention is more reusable. For example, in the existing verification system, IP basically must interact with other IPs for data, and there is data interaction, i.e., there is a master-slave relationship of data transmission and reception. If the verification system wants to change the IP of verification, it only needs to change the data packet structure sent by the verification system and the interactive logical relationship in the master-agent component and the slave-agent component, without the need to modify the verification system structure, to achieve reusability.
[0092] The master-slave UVM verification system, method and device of the present invention are more in line with the specification design of DUT in logic. Starting from the transmission protocol design idea on the DUT specification and on the premise of understanding the DUT specification, the master-slave UVM verification system is designed according to the transmission protocol of transmission and reception. When a successor modifies the platform, according to the master-slave relationship of the platform, errors in compilation or receiving and sending logic can be found and modified in the master agent component for input errors, and output errors can be modified in the slave agent component.
[0093] In some embodiments, certain aspects of the above-mentioned techniques may be implemented by one or more processors of a processing system executing software. The software includes one or more executable instruction sets stored or otherwise tangibly implemented on a non-transitory computer-readable storage medium. The software may include instructions and certain data that manipulate one or more processors to perform one or more aspects of the above-mentioned techniques when executed by one or more processors. Non-transitory computer-readable storage media may include, for example, magnetic or optical disk storage devices, solid-state storage devices such as flash memory, cache, random access memory (RAM), or other non-volatile memory devices. The executable instructions stored on the non-transitory computer-readable storage medium may be source code, assembly language code, object code, or other instruction formats interpreted or otherwise executed by one or more processors.
[0094] Computer-readable storage media may include any storage medium or combination of storage media that can be accessed by a computer system during use to provide instructions and / or data to the computer system. Such storage media may include, but are not limited to, optical media (e.g., compact disks (CDs), digital versatile disks (DVDs), Blu-ray disks), magnetic media (e.g., floppy disks, tapes, or magnetic hard drives), volatile memory (e.g., random access memory (RAM) or cache), non-volatile memory (e.g., read-only memory (ROM) or flash memory), or micro-electromechanical system (MEMS)-based storage media. Computer-readable storage media may be embedded in a computing system (e.g., system RAM or ROM), fixedly attached to a computing system (e.g., a magnetic hard drive), removably attached to a computing system (e.g., an optical disk or a universal serial bus (USB)-based flash memory), or coupled to a computer system via a wired or wireless network (e.g., network accessible storage (NAS)).
[0095] Although the present invention has been disclosed as above with preferred embodiments, the embodiments are not intended to limit the present invention. Any equivalent changes or modifications made without departing from the spirit and scope of the present invention also belong to the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the content defined by the claims of this application.
Claims
1. A master-slave UVM verification system, It is characterized in that As the master-slave machine of the vector computing unit, it realizes the functions of sending data packets to the vector computing unit, receiving data packets of the vector computing unit and configuring registers, and completes the data packet stimulus injection according to the data packet transmission protocol of the vector computing unit through the verification IP interface between the vector computing unit; the master-slave UVM verification system includes a master agent component, a slave agent component and a register configuration agent component; The main agent component simulates the process of the upstream module of the vector computing unit writing data to the vector computing unit, and performs the input of the fusion data of the read input and the input of the read input response data; The slave proxy component simulates a downstream module of the vector computing unit, receives characteristic data of a write output mode of the vector computing unit, sends a write output response to the vector computing unit, and receives a read request from the vector computing unit; The register configuration agent component simulates register configuration and adopts APB bus protocol to configure the registers of the vector computing unit.
2. The master-slave UVM verification system according to claim 1, It is characterized in that The master agent component, the slave agent component and the register configuration agent component each contain three sub-components: a sequence arbitrator, a driver and a monitor; The sequence arbiter receives the data packet stimulus for verification generated by the sequence generator, and transmits it to the driver of the corresponding master agent component, slave agent component or register configuration agent component after arbitration; The driver inputs the data packet stimulus arbitrated by the sequence arbiter into the vector computing unit through an interface interacting with the vector computing unit according to the vector computing unit transmission protocol requirements; The monitor monitors the input and output of data signals between the corresponding master agent component, slave agent component or register configuration agent component and the vector computing unit, and simultaneously transmits the relevant data signals input to the vector computing unit to the reference model, and transmits the relevant data signals output from the vector computing unit to the scoreboard.
3. The master-slave UVM verification system according to claim 1, It is characterized in that After the register configuration agent component completes the configuration of the register data, the master agent component and the slave agent component run in parallel.
4. The master-slave UVM verification system according to claim 2, It is characterized in that The data packet transmission protocol includes three types of data packet transmission protocols: read input, write input, and write output; the verification IP interface controls the input and output of the vector calculation unit; the output of the verification IP interface adopts the write output data packet transmission protocol, and the input of the verification IP interface includes write input and read input, which are used to input image feature values and fusion data respectively; Write input is the image feature data of the upstream module written into the vector calculation unit.
5. The master-slave UVM verification system according to claim 1, It is characterized in that The writing input is that the main agent component writes the image feature data into the vector calculation unit, and the process includes: The main agent component transmits three types of data packet stimuli, namely, a channel request for writing input data, channel data, and a channel data address, to an interface interacting with the vector computing unit according to a data packet transmission protocol; Receives the channel response of the write input data returned by the vector computing unit.
6. The master-slave UVM verification system according to claim 1, It is characterized in that The write output is that the slave proxy component, as a downstream module of the vector calculation unit, receives the image feature data written by the vector calculation unit and sends the response data of the write output to the vector calculation unit. The process includes: After receiving the channel request for writing output data sent by the vector calculation unit and the number of image feature data corresponding to the channel request, the proxy component sends a channel response with the same number of data to the vector calculation unit.
7. The master-slave UVM verification system according to claim 1, It is characterized in that The read input is to input the fused data into the vector computing unit, which is completed by the combination of the master agent component and the slave agent component. The process includes: After receiving the read input request sent by the vector calculation unit, the slave agent component injects the response signal data into the vector calculation unit; the master agent component injects the channel address and channel data of the read input data into the vector calculation unit.
8. A master-slave UVM verification method, It is characterized in that The method is implemented by the master-slave UVM verification system according to any one of claims 1 to 7, comprising: Re-instantiate each agent component and its driver, monitor and sequence arbiter, connect the components, and configure the register model; Execute various time-consuming phases, then start the sequence generator to generate data packet excitations and send them to the master agent component and the slave agent component; the master-slave agent component transmits these data packet excitations to the vector calculation unit according to the relevant interface protocol to complete the injection of data excitations; the same data packet excitations as those injected into the vector calculation unit are transmitted to the reference model for the same data calculation, and then output to the scoreboard, and compared with the data output by the vector calculation unit in the scoreboard to determine whether the vector calculation unit is working correctly; End the simulation run and output the log.
9. A computer-readable storage medium having a computer program stored thereon, It is characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.
10. A computer program product, It is characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.
Citation Information
Cited By
Equipment communication verification method and device, equipment, storage medium and program product
CN120144520A
Device communication verification method, apparatus, device, storage medium and program product
CN120144520B
