SMPU module verification system and method based on UVM verification platform
Through the SMPU module verification system based on the UVM verification platform, the problems of too late verification intervention and low efficiency in traditional verification technology are solved, and efficient module-level verification is achieved, ensuring the completeness and efficiency of the SMPU module.
Patent Information
- Application Number
- CN202411043063.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-31
- Publication Date
- 2024-11-22
AI Technical Summary
Traditional SMPU module verification technology is carried out on the entire chip. The verification intervention is too late and it is difficult to traverse all accesses, especially illegal and erroneous access, resulting in incomplete verification and low efficiency, low simulation efficiency and poor reusability, increasing workload and simulation time.
The SMPU module verification system based on the UVM verification platform is adopted, including the SMPU module to be verified, register model, reference model, scoreboard component, input agent and output monitor of AHB and AXI buses. Through module-level simulation, it simulates a multi-core environment. The verification of SMPU modules is achieved and the disadvantages of traditional verification technology is overcome.
It greatly improves the verification efficiency of SMPU modules, and early intervention verification, improves the completeness and reusability of verification, reduces simulation time and workload, and ensures the behavior of all cores and the traversal of storage space.
Smart Images

Figure CN119004565A_ABST
Abstract
Description
Technical Field
[0001] The invention belongs to the technical field of chip verification, and relates to an SMPU module verification system and method based on a UVM verification platform. Background Art
[0002] With the continuous development of electronic information technology, the demand for chips is increasing. The constantly upgraded electronic information functions often require multiple cores in a chip to improve processing power and efficiency. The information security requirements brought by multiple cores have also become a major focus of multi-core processor design. SMPU (system-memory-protection-unint, system storage space protection unit) is mainly implemented in multi-core systems to set permissions for each bus to access storage space to ensure the information security of each storage space. For example, administrator cores and user cores can be set in multiple cores, allowing the set administrator core to access all storage spaces, and allowing the set user core to access only part of the storage space. This setting of core permissions requires SMPU to implement. At present, the traditional verification technology for SMPU is to perform system verification on the entire chip, and to implement SMPU verification by configuring different processors and sending different access requests.
[0003] However, this verification method directly on the system intervenes in the verification stage too late. Verification can only be intervened after the whole chip is integrated, which increases the risk of project delivery; it is difficult to traverse all accesses, especially some illegal accesses and erroneous accesses, so it is difficult to ensure the completeness of verification; the reusability is poor. After changing a project and increasing or decreasing the number of cores, the use case and configuration process must be re-adapted; the simulation efficiency is low. Whether the expected result of each stimulus issued is intercepted needs to be calculated separately in the use case, and the expected result cannot be automatically generated; at the same time, after carrying the whole chip and all cores, the addition of some irrelevant modules slows down the simulation and debugging, which increases the workload of the verification personnel and the simulation time. Therefore, the traditional verification technology still has the technical problem of low verification efficiency. Summary of the invention
[0004] In view of the problems existing in the above-mentioned traditional methods, the present invention proposes an SMPU module verification system based on a UVM verification platform and an SMPU module verification method based on the UVM verification platform, which can greatly improve the verification efficiency of the SMPU module.
[0005] In order to achieve the above objectives, the embodiments of the present invention adopt the following technical solutions:
[0006] On the one hand, a SMPU module verification system based on a UVM verification platform is provided, comprising an SMPU module to be verified and a register model, a reference model, a scoreboard component, n groups of input agents of AHB buses, m groups of input agents of AXI buses, n groups of output monitors of AHB buses, and m groups of output monitors of AXI buses, wherein n and m are configurable parameters not less than 1;
[0007] The SMPU module is respectively connected to n groups of input agents of the AHB bus and m groups of input agents of the AXI bus. The n groups of input agents of the AHB bus are used to send data packets conforming to the AHB bus to the corresponding driver through a sequence, and the m groups of input agents of the AXI bus are used to send data packets conforming to the AXI bus to the corresponding driver through a sequence. The data packets include the read / write information, mid information, prot information and the address of the accessed storage space required by the AHB bus and the AXI bus. The corresponding driver is used to issue the behavior drive SMPU module conforming to the AXI bus and the AHB bus according to the received data packets.
[0008] The register model is used to read and write the registers of the SMPU module through the APB bus to complete the configuration of the SMPU module;
[0009] The reference model is used to obtain the configuration of the registers of the SMPU module. When the environment of the SMPU module verification system initiates AXI bus and AHB bus access, it receives the same data packet as that received by the SMPU module and calculates whether interception is required. When the result is that interception occurs, the access information of the current bus access is sent to the scoreboard component as the expected result.
[0010] The output monitor of n groups of AHB buses is used to monitor the situation that n groups of AHB buses are intercepted by the SMPU module and send the access information of the current bus access as the actual result to the scoreboard component when interception occurs. The output monitor of m groups of AXI buses is used to monitor the situation that m groups of AXI buses are intercepted by the SMPU module and send the access information of the current bus access as the actual result to the scoreboard component when interception occurs.
[0011] The scoreboard component is used to compare the expected results with the actual results, and output the comparison result information when the comparison is inconsistent; the comparison result information is used to indicate the verification result of the SMPU module.
[0012] On the other hand, a SMPU module verification method based on a UVM verification platform is also provided, which is applied to the above-mentioned SMPU module verification system based on the UVM verification platform. The SMPU module verification method based on the UVM verification platform includes the steps of:
[0013] Randomly configure the register model, send the random configuration information to the reference model and write the register of the SMPU module through the APB bus;
[0014] Randomly generate stimulus information that conforms to the AHB bus and the AXI bus through sequences corresponding to n groups of AHB bus input agents and m groups of AXI bus input agents, send the stimulus information to the reference model and drive the SMPU module;
[0015] The reference model sends the access information of the bus access each time an interception occurs to the scoreboard component as the expected result;
[0016] The output monitor of n groups of AHB buses monitors the situation that n groups of AHB buses are intercepted by the SMPU module and sends the access information of the current bus access as the actual result to the scoreboard component when the interception occurs;
[0017] The output monitor of the m groups of AXI buses is used to monitor the situation that the m groups of AXI buses are intercepted by the SMPU module and send the access information of the current bus access as the actual result to the scoreboard component when interception occurs;
[0018] The scoreboard component compares the expected result with the actual result, and outputs the comparison result information when the comparison is inconsistent; the comparison result information is used to indicate the verification result of the SMPU module.
[0019] One of the above technical solutions has the following advantages and beneficial effects:
[0020] The SMPU module verification system and method based on the UVM verification platform are designed to meet the verification requirements of the SMPU module, and the verification system is composed of the SMPU module to be verified and the register model, reference model, scoreboard component, n groups of AHB bus input agents, m groups of AXI bus input agents, n groups of AHB bus output monitors and m groups of AXI bus output monitors. The verification of the SMPU module is completed by simulating multi-core at the module level, and the disadvantages of the SMPU module intervention node too late, poor completeness, poor reusability and low efficiency in the traditional verification technology are overcome, thereby achieving the effect of greatly improving the verification efficiency of the SMPU module. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the conventional technology, the drawings required for use in the embodiments or the conventional technology descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0022] Figure 1 A schematic diagram of the platform architecture of an SMPU module verification system based on a UVM verification platform in one embodiment;
[0023] Figure 2 A schematic diagram of a verification process of an SMPU module verification system based on a UVM verification platform in one embodiment;
[0024] Figure 3 The figure is a flow chart of a SMPU module verification method based on a UVM verification platform in one embodiment. DETAILED DESCRIPTION
[0025] In order to make the purpose, technical scheme and advantages of the present invention clearer, the present invention is further described in detail below in conjunction with the accompanying drawings and Examples. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those generally understood by those skilled in the art of the present invention. The terms used in the specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention.
[0026] It should be noted that the reference to "embodiment" in this article means that the specific features, structures or characteristics described in conjunction with the embodiment may be included in at least one embodiment of the present invention. The presentation of this phrase at various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It will be appreciated by those skilled in the art that the embodiments described herein may be combined with other embodiments. The term "and / or" used in the specification of the present invention and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes these combinations.
[0027] The following will describe the implementation of the present invention in detail with reference to the accompanying drawings in the embodiment diagram of the present invention.
[0028] First, it should be briefly explained that one aspect of the key feature of the UVM verification methodology is reusable components and standardized hierarchical structure, the structure of its UVM workbench includes three parts from top to bottom, such as top-level (simulation) file testbench, interface layer interface and part to be tested DUT, wherein, interface is used to connect top-level file and DUT, and DUT can be various products that need test verification, such as SMPU module for example in the present invention.
[0029] In one embodiment, Figure 1As shown, a SMPU module verification system based on a UVM verification platform is provided, including an SMPU module to be verified and a register model, a reference model, a scoreboard component, n groups of input agents of AHB buses, m groups of input agents of AXI buses, n groups of output monitors of AHB buses, and m groups of output monitors of AXI buses created based on a test case base class of the UVM verification platform; n and m are both configurable parameters not less than 1. The SMPU module is connected to n groups of input agents of AHB buses and m groups of input agents of AXI buses respectively, and the n groups of input agents of AHB buses are used to send data packets conforming to the AHB bus to corresponding drivers through sequences. The m groups of input agents of AXI buses are used to send data packets conforming to the AXI bus to corresponding drivers through sequences; the data packets include read / write information, mid information, prot information required by the AHB bus and the AXI bus, and the address of the accessed storage space. The corresponding driver is used to drive the SMPU module with behaviors conforming to the AXI bus and the AHB bus according to the received data packets. The register model is used to read and write registers of the SMPU module through the APB bus to complete the configuration of the SMPU module.
[0030] The reference model is used to obtain the configuration of the registers of the SMPU module. When the environment of the SMPU module verification system initiates AXI bus and AHB bus access, it receives the same data packet as that received by the SMPU module and calculates whether interception is required. When the result is that interception occurs, the access information of the current bus access is sent to the scoreboard component as the expected result. The output monitor of n groups of AHB buses is used to monitor the situation where n groups of AHB buses are intercepted by the SMPU module and send the access information of the current bus access as the actual result to the scoreboard component when interception occurs. The output monitor of m groups of AXI buses is used to monitor the situation where m groups of AXI buses are intercepted by the SMPU module and send the access information of the current bus access as the actual result to the scoreboard component when interception occurs. The scoreboard component is used to compare the expected result with the actual result, and output the comparison result information when the comparison is inconsistent; the comparison result information is used to indicate the verification result of the SMPU module.
[0031] It can be understood that the platform architecture of the verification system can be as follows Figure 1 As shown in the figure, the verification object of this platform architecture is the SMPU module, and there is no need to integrate the entire chip as the design under test.
[0032] The bus interfaces connected to the SMPU module are mostly AHB (Advanced High_performance Bus) interfaces and AXI (Advanced eXtensible Interface) interfaces. The SMPU module, as a design to be tested, can be connected to n groups of AHB bus input agents and m groups of AXI bus input agents, respectively. n and m are configurable parameters. The input agents of the AHB bus and AXI bus can send data packets that conform to the AHB bus and AXI bus to the corresponding driver through the corresponding sequence (sequence, which is a database object used to generate unique integers). The data packet may include the read / write information required by the AHB bus and AXI bus, mid (indicating which core it comes from), prot (access type, privilege / user, instruction / data, etc.) information, and the address of the accessed storage space. The driver of the AHB bus and AXI bus can issue behaviors that conform to the AXI bus and AHB bus protocols to drive the SMPU module based on the received data packets. The data packets here can simulate randomly different mids to simulate all cores; randomly simulate all access rights and behaviors, including valid and invalid accesses; randomly simulate all valid addresses to simulate access to different storage spaces.
[0033] The register model (which can be recorded as Reg_model) is implemented to read and write the registers of the SMPU module through buses such as APB (Advanced Peripheral Bus) to complete the configuration of the SMPU module. In the UVM verification methodology, the register model is a mechanism for simulating and managing hardware registers. It provides an abstract way to access and operate registers, thereby simplifying the verification work at the register level. In this embodiment, it is designed as a configuration executor of the SMPU module, which is used to read and write the registers of the SMPU module through the APB bus.
[0034] The reference model (which can be denoted as Rm) can obtain the configuration of the registers. Then, whenever the environment of the SMPU module verification system initiates access to the AXI bus and AHB bus, the reference model can receive the same data packet as the DUT (i.e., the SMPU module), and calculate the data packet to determine whether it needs to be intercepted. When interception occurs, the access information is sent as the expected result to the scoreboard component (which can be denoted as Scb). In the UVM verification methodology, the reference model is an idealized or high-level model used to verify the behavior of the SMPU module. The main purpose of the reference model is to provide a known correct output to be compared with the actual output of the SMPU module, thereby verifying whether the function of the SMPU module is correct. The reference model can obtain the register configuration of the SMPU module through direct access, mirroring mechanism, configuration callback, or file input, so that the reference model can accurately obtain and use the register configuration of the SMPU module to ensure the comprehensiveness and accuracy of the verification.
[0035] Among them, when the driver driver in the input agent of AHB bus and AXI bus initiates AXI bus and AHB bus access (SMPU module receives access) in the environment of SMPU module verification system built based on UVM verification platform, the quantity and content initiated can be controlled by test case. The data packet sent to the driver driver can also be sent to the reference model in the environment of SMPU module verification system, so the reference model can obtain the same data information as the AHB bus or AXI bus driven to DUT at this time.
[0036] Implement output monitors for n groups of AHB buses and m groups of AXI buses, monitor the situation where the corresponding buses are intercepted by the SMPU module, and when interception occurs, send the access information as the actual result to the scoreboard component.
[0037] The scoreboard component receives the expected results from the reference model and the actual results from the monitor for real-time comparison. When the actual results are inconsistent with the expected results, the comparison result information is output for automatic checking. The comparison result information can clearly display the detailed error information of the SMPU module under each bus access storage space, thereby guiding the user to perform corresponding troubleshooting.
[0038] The test case base class (base_testcase) can realize the random configuration constraints of the registers of the SMPU module, the random constraints of the data packets of the AHB bus and AXI bus, including the random number of data packets and the mid, address, port and other information in the data packet content. At the same time, the test case base class can derive test cases with different constraints to achieve flexible control of data packets.
[0039] The above-mentioned SMPU module verification system based on the UVM verification platform can be involved in verification after the SMPU module is developed through module-level simulation, and the verification can be added earlier. The interface parameterization of the AHB bus and the AXI bus effectively solves the demand impact caused by increasing or reducing the number of cores at any time, and improves the reusability of the verification system. The access data packets of the AHB bus and the AXI bus do not need to be configured and issued by the core on the system, but can be directly generated by the driver based on the effective protocol. Therefore, all addresses including read / write, user / privilege, instruction / data and valid range of all cores can be traversed, ensuring that all behaviors and all storage spaces of the SMPU module can be traversed, greatly improving the completeness of the verification system. The environment of the verification system only integrates the SMPU module-level design to be tested, and can automatically generate expected results through the reference model to realize automatic comparison on the scoreboard component, so the workload and simulation time of the verification personnel can be greatly reduced, thereby greatly improving the verification efficiency.
[0040] In one embodiment, the register model is a random register model.
[0041] like Figure 2 Shown is the execution process of an instance of the SMPU module verification system based on the UVM verification platform. The user can input a random register configuration to the register model, send the register configuration to the reference model and write it to the SMPU module through the APB bus at the same time. The design to be tested, then randomly generate the excitation information that meets the AHB bus and the AXI bus by configuring the sequence, the system sends these excitation information to the reference model and drives the SMPU module based on the corresponding protocol (i.e., AHB bus and AXI bus) by driving. Then the reference model calculates each data packet to obtain whether the bus access needs to be intercepted, and when the result is interception, the access information of the bus access is sent to the scoreboard component as the expected result. Correspondingly, the output monitors of n groups of AHB buses and m groups of AXI buses collect the interception results of the SMPU module, and when interception occurs, the access information of the bus access is sent to the scoreboard component as the actual result. The scoreboard component compares the expected result with the actual result and outputs the comparison result.
[0042] Finally, the verification system will determine whether all stimuli have been sent. If so, the simulation verification of the SMPU module is completed. Otherwise, it will continue to send stimulus information and perform subsequent verification processes until the verification is completed.
[0043] It can be understood that the random register model can enable each operation of the verification system to implement different permission configurations for the SMPU module, thereby further improving the completeness of the verification.
[0044] The above-mentioned verification system can be built using the existing SystemVerilog language in this field and follow the UVM verification methodology. It can be configured and obtained by using the components in the UVM verification platform according to the verification interaction functions required to be provided respectively. For example, the verification sequence library is a library for storing and managing verification sequences (sequences). In the UVM verification methodology, verification sequences are objects used to generate test scenarios and interactions, and they describe the sequence of events that occur in the test, such as input, output and timing relationships. The verification sequence library provides a structured way to organize and call these verification sequences. When the verification sequence library is used to manage the verification sequence, it provides a central location for users to register, store and retrieve customized verification sequences. Users can register their verification sequences in the verification sequence library so that these sequences can be accessed and executed in the test, and such registration is usually completed in the initialization phase of the test environment. Once the verification sequence is registered, other components (such as tests, other verification sequences, etc.) can call these sequences through the verification sequence library, so that the test scenario can create complex test cases by organically combining different sequences. The verification sequence library can support hierarchical structures, allowing users to organize and manage multiple related verification sequences. The verification sequence library also supports dynamic configuration, allowing users to dynamically select and randomly configure verification sequences as needed during runtime. Therefore, when performing verification tests, users can use the verification sequence library to randomly configure verification sequences according to the verification needs of the SMPU module, thereby supporting more complete verification tests.
[0045] Each module in the SMPU module verification system based on the UVM verification platform can be implemented in whole or in part by software, hardware and a combination thereof. Each of the above modules can be embedded in or independent of a device with data processing functions in the form of hardware, or can be stored in the memory of the aforementioned device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules. The aforementioned device can be, but is not limited to, various types of verification computer devices already available in the art.
[0046] In one embodiment, Figure 3 As shown, a SMPU module verification method based on a UVM verification platform is provided, which may include the following processing steps S10 to S20:
[0047] S10, applied to the above-mentioned SMPU module verification system based on the UVM verification platform, the SMPU module verification method based on the UVM verification platform comprises the steps of:
[0048] S12, randomly configure the register model, send the randomly configured information to the reference model and write the register of the SMPU module through the APB bus;
[0049] S14, randomly generating stimulus information that conforms to the AHB bus and the AXI bus through sequences corresponding to n groups of AHB bus input agents and m groups of AXI bus input agents, sending the stimulus information to the reference model and driving the SMPU module;
[0050] S16, the reference model sends the access information of the bus access each time the interception occurs to the scoreboard component as the expected result;
[0051] S17, the output monitor of n groups of AHB buses monitors the situation that n groups of AHB buses are intercepted by the SMPU module and sends the access information of the current bus access as the actual result to the scoreboard component when interception occurs;
[0052] S18, the output monitor of the m groups of AXI buses is used to monitor the situation where the m groups of AXI buses are intercepted by the SMPU module and send the access information of the current bus access as the actual result to the scoreboard component when interception occurs;
[0053] S20, the scoreboard component compares the expected result and the actual result, and outputs comparison result information when the comparison is inconsistent; the comparison result information is used to indicate the verification result of the SMPU module.
[0054] The above-mentioned SMPU module verification method based on the UVM verification platform can be used for verification after the SMPU module is developed through module-level simulation, and the verification can be added earlier. The interface parameterization of the AHB bus and the AXI bus effectively solves the demand impact caused by increasing or reducing the number of cores at any time, and improves the reusability of the verification system. The access data packets of the AHB bus and the AXI bus do not need to be configured and issued by the core on the system, but can be directly generated by the driver based on the effective protocol. Therefore, all addresses including read / write, user / privilege, instruction / data and valid range of all cores can be traversed, ensuring that all behaviors and all storage spaces of the SMPU module can be traversed, greatly improving the completeness of the verification system. The environment of the verification system only integrates the SMPU module-level design to be tested, and can automatically generate expected results through the reference model to realize automatic comparison on the scoreboard component, so the workload and simulation time of the verification personnel can be greatly reduced, thereby greatly improving the verification efficiency.
[0055] In one embodiment, after the above step S20, the above SMPU module verification method based on the UVM verification platform may further include the following steps:
[0056] When it is determined that all stimulus information has been sent, the simulation verification of the SMPU module is ended.
[0057] This ensures that the entire verification process ends and exits accurately and timely, avoiding excessive computing resource usage.
[0058] In one embodiment, after the above step S20, the above SMPU module verification method based on the UVM verification platform may further include the following steps:
[0059] When it is determined that all the incentive information has not been sent, return to step S14.
[0060] This ensures that the entire verification process traverses all verifications under all stimuli, avoiding premature or erroneous exit of the verification process of the SMPU module, thereby improving the reliability of the verification results.
[0061] It can be understood that for the specific limitations of the SMPU module verification method based on the UVM verification platform, reference can be made to the corresponding limitations of the SMPU module verification system based on the UVM verification platform above, which will not be repeated here.
[0062] It should be understood that although Figure 3 The steps in the method are shown in sequence as indicated by the arrows, but the steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of the steps, and the steps can be executed in other orders. Figure 3 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequentially, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.
[0063] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided by the present invention can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus dynamic random access memory (RambusDRAM, referred to as RDRAM) and interface dynamic random access memory (DRDRAM).
[0064] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0065] The above embodiments only express several implementation methods of the present invention, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of protection of the invention. It should be pointed out that, for those of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present invention, which all belong to the scope of protection of the present invention. Therefore, the scope of protection of the present invention shall be subject to the attached claims.
Claims
1. A SMPU module verification system based on UVM verification platform, characterized in that: It includes the SMPU module to be verified and the register model, reference model, scoreboard component, n groups of AHB bus input agents, m groups of AXI bus input agents, n groups of AHB bus output monitors and m groups of AXI bus output monitors created based on the test case base class of the UVM verification platform; n and m are both configurable parameters not less than 1; The SMPU module is respectively connected to n groups of input agents of the AHB bus and m groups of input agents of the AXI bus, wherein the n groups of input agents of the AHB bus are used to send data packets conforming to the AHB bus to the corresponding driver through a sequence, and the m groups of input agents of the AXI bus are used to send data packets conforming to the AXI bus to the corresponding driver through a sequence; the data packets include the read / write information, mid information, prot information and the address of the accessed storage space required by the AHB bus and the AXI bus, and the corresponding driver is used to drive the SMPU module by issuing behaviors conforming to the AXI bus and the AHB bus according to the received data packets; The register model is used to read and write the registers of the SMPU module through the APB bus to complete the configuration of the SMPU module; The reference model is used to obtain the configuration of the register of the SMPU module, and when the environment of the SMPU module verification system initiates AXI bus and AHB bus access, receive the same data packet as received by the SMPU module and calculate whether interception is required, and when the result is that interception occurs, send the access information of the current bus access as the expected result to the scoreboard component; The output monitors of n groups of AHB buses are used to monitor the situation that n groups of AHB buses are intercepted by the SMPU module and send the access information of the secondary bus access as the actual result to the scoreboard component when interception occurs; the output monitors of m groups of AXI buses are used to monitor the situation that m groups of AXI buses are intercepted by the SMPU module and send the access information of the secondary bus access as the actual result to the scoreboard component when interception occurs; The scoreboard component is used to compare the expected result and the actual result, and output comparison result information when the comparison is inconsistent; the comparison result information is used to indicate the verification result of the SMPU module.
2. The SMPU module verification system based on UVM verification platform according to claim 1, characterized in that, The register model is a random register model.
3. A SMPU module verification method based on UVM verification platform, characterized in that, Applied to the SMPU module verification system based on the UVM verification platform according to claim 1 or 2, the SMPU module verification method based on the UVM verification platform comprises the steps of: Randomly configure the register model, send the randomly configured information to the reference model and write the register of the SMPU module through the APB bus; Randomly generate stimulus information that conforms to the AHB bus and the AXI bus through sequences corresponding to n groups of AHB bus input agents and m groups of AXI bus input agents, send the stimulus information to the reference model and drive the SMPU module; The reference model sends the access information of the secondary bus access as the expected result to the scoreboard component each time an interception occurs; The output monitor of n groups of AHB buses monitors the situation that n groups of AHB buses are intercepted by the SMPU module and sends the access information of the current bus access as the actual result to the scoreboard component when interception occurs; The output monitor of the m groups of AXI buses is used to monitor the situation that the m groups of AXI buses are intercepted by the SMPU module and send the access information of the current bus access as the actual result to the scoreboard component when interception occurs; The scoreboard component compares the expected result and the actual result, and outputs comparison result information when the comparison is inconsistent; the comparison result information is used to indicate the verification result of the SMPU module.
4. The SMPU module verification method based on UVM verification platform according to claim 3, characterized in that, Also includes the steps: When it is determined that all the stimulus information has been sent, the simulation verification of the SMPU module is terminated.
5. according to the SMPU module verification method based on UVM verification platform described in claim 3 or 4, it is characterized in that, Also includes the steps: When it is determined that all stimulus information has not been sent, the sequence corresponding to the input agents of n groups of AHB buses and the input agents of m groups of AXI buses is returned, stimulus information that conforms to the AHB bus and the AXI bus is randomly generated, and the stimulus information is sent to the reference model and drives the SMPU module.
Citation Information
Cited By
UVM verification platform reference model hardware architecture supporting multistage dynamic configuration
CN120723635A
