Random excitation generation method and device for chip verification, equipment and medium

By obtaining the scheduler and routing destination in chip verification, random excitation generation is realized, which solves the readability and scalability problems of complex random excitation verification in the prior art, and improves the evaluation and management efficiency of verification quality.

CN119088521APending Publication Date: 2024-12-06HYGON INFORMATION TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411196872.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-29
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

The existing complex random incentive verification methods lack clear guidance on verification schemes, the code structure is scattered, the readability is poor, and the review is difficult to quantify and evaluate the verification quality, and lack reusability, scalability and portability.

Method used

By obtaining the interface of the object module to be tested, the scheduler is obtained, configured to support multiple protocols, obtain multiple routing destinations, and trigger the scheduler thread to send data packets to multiple routing destinations, realizing random incentive generation, using parent class The inheritance relationship of the subclass is sent packets, and the coverage monitoring component is integrated to evaluate functional coverage.

Benefits of technology

It realizes complex random incentive verification for any interface and any combination scenario, has good reusability and scalability, simplifies the construction of complex incentives, and improves the evaluation and management efficiency of verification quality.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119088521A_ABST
    Figure CN119088521A_ABST
Patent Text Reader

Abstract

The invention provides a random excitation generation method and device for chip verification, electronic equipment and a medium. The method comprises the following steps: acquiring a to-be-tested object module; a scheduler is obtained based on the interface used for the to-be-tested object module, and the scheduler is configured to support protocols corresponding to the interface; obtaining a plurality of routing destinations based on the to-be-tested object module; obtaining a thread corresponding to the scheduler based on the scheduler and the plurality of routing destinations; and triggering a thread of the scheduler, and sending data packets to a plurality of routing destinations of the to-be-tested object module so as to obtain the random excitation reaching the to-be-tested object module. Complex excitation is generated based on scheduling packet sending, and a complex random excitation verification scene of any interface and any combination scene can be realized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present disclosure relate to a method, device, electronic device, and medium for generating random stimuli for chip verification. Background Art

[0002] As semiconductor processes and application computing power requirements continue to increase, the scale and complexity of chip design continue to increase. Verification work needs to match the design. As a result, the scale of the verification environment is also increasing day by day, and the required verification scenarios are becoming more and more complex.

[0003] For the common chip design specifications such as complex system-on-chip (SoC), the chip peripheral interface usually includes PCIe (Peripheral Component Interconnect express, which is a high-speed serial computer expansion bus standard), DDR (Double Data Rate) and other general high-speed interfaces. Each manufacturer also usually has different cross-core circuit groups (DIE) and cross-Socket interconnection solutions. In integrated circuits, DIE is a chip particle on which a specific functional circuit is manufactured. For Socket, it means that on a server, a motherboard can have multiple Sockets, that is, the physical slots of the processor. In addition, some auxiliary Slow IO interfaces (such as I2C, GPIO, etc.) are also involved. Slow IO interfaces refer to low-speed input and output interfaces.

[0004] There are usually multiple complex bus protocols inside the chip. Each interface / protocol contains multiple types of data packets, and different data packets can be routed to different destinations based on addresses or IDs (Identity documents, a specific identifier used for routing tags).

[0005] When multiple interfaces are working at the same time, various types of data packets are intertwined in the chip's internal bus. In such a complex scenario, the chip must not only meet the correctness of data interaction, but also meet bandwidth requirements, and avoid deadlock. This requires that the stimulus generation of the verification environment must be complex and random, so as to simulate a close-to-real application scenario. Summary of the invention

[0006] At least one embodiment of the present disclosure provides a method for generating random stimuli for chip verification, comprising: obtaining a module of an object under test; obtaining a scheduler based on an interface for the module of the object under test, wherein the scheduler is configured to respectively support protocols corresponding to the interface; obtaining multiple routing destinations based on the module of the object under test; obtaining a thread corresponding to the scheduler based on the scheduler and the multiple routing destinations; triggering the thread of the scheduler to send data packets to the multiple routing destinations of the module of the object under test, so as to obtain random stimuli that reach the module of the object under test.

[0007] For example, in a random stimulus generation provided by at least one embodiment of the present disclosure, a scheduler is obtained based on an interface for the module of the object to be tested, including: in response to the number of interfaces for the module of the object to be tested being N interfaces, N schedulers are obtained, wherein the N schedulers correspond one-to-one to the N interfaces, and each of the N interfaces corresponds to a protocol, and N is an integer greater than or equal to 1.

[0008] For example, in a random stimulus generation provided by at least one embodiment of the present disclosure, the multiple threads corresponding to each of the schedulers correspond one-to-one to the multiple routing destinations.

[0009] For example, in a random stimulus generation provided by at least one embodiment of the present disclosure, the thread of the scheduler is triggered to send data packets to multiple routing destinations of the module under test, including: obtaining a stimulus-driven adapter component of the scheduler, wherein the stimulus-driven adapter component corresponds one-to-one to the scheduler; based on the stimulus-driven adapter component, sending the data packet generated by the thread corresponding to the scheduler through the interface to the corresponding routing destination of the module under test.

[0010] For example, in a random stimulus generation provided by at least one embodiment of the present disclosure, before sending the data packet generated by the thread corresponding to the scheduler to the corresponding routing destination of the object module under test through the interface, the method also includes: randomly generating a data packet through thread control and thread constraints and based on the routing destination; storing the randomly generated data packet in a random data entry queue for use after the thread of the scheduler is triggered to send it to the object module under test.

[0011] For example, in a random stimulus generation provided by at least one embodiment of the present disclosure, the thread of the scheduler is triggered to send a data packet to the routing destination of the module of the object under test, including: in response to the N schedulers being one scheduler, the multiple threads corresponding to the schedulers are triggered in parallel to send data packets to the multiple routing destinations of the module of the object under test; in response to the N schedulers being multiple schedulers, the multiple schedulers are triggered in parallel to send data packets to the multiple routing destinations of the module of the object under test.

[0012] For example, in a random stimulus generation provided by at least one embodiment of the present disclosure, a scheduler is obtained based on an interface for the module of the object to be tested, including: defining a first parent class for stimulus drive adaptation, wherein the first parent class is configured to implement a unified packet sending task, and the unified packet sending task is configured to call a corresponding packet sending task according to the type of data packet; defining a second parent class, wherein the second parent class is an interface control parent class; based on the first parent class, one or more first subclasses inherited from the first parent class are implemented, wherein the one or more first subclasses correspond one-to-one to the interface and each of the first subclasses corresponds to each of the stimulus drive adaptation components; based on the second parent class, one or more second subclasses inherited from the second parent class are implemented, wherein the one or more second subclasses correspond one-to-one to the interface.

[0013] For example, in a random stimulus generation provided by at least one embodiment of the present disclosure, based on the stimulus-driven adaptation component, the data packet generated by the thread corresponding to the scheduler is sent to the corresponding routing destination of the object module under test through the interface, including: based on the first parent class, the second parent class, the first subclass and the second subclass, the data packet is called and sent to the object module under test by pointing to the subclass object through the parent class pointer.

[0014] For example, in a random stimulus generation provided by at least one embodiment of the present disclosure, the scheduler also includes a coverage monitoring component, and the method also includes: in response to triggering the thread of the scheduler, the stimulus driving adaptation component sends a data packet of the thread corresponding to the scheduler to the coverage monitoring component of the scheduler to collect functional coverage.

[0015] At least one embodiment of the present disclosure provides a random stimulus generation device for chip verification, comprising: an object under test module, including multiple routing destinations; a scheduler, configured to be created based on an interface for the object under test module, wherein the scheduler respectively supports protocols corresponding to the interface, the scheduler is provided with a thread determined based on the multiple routing destinations, and the scheduler is configured to: in response to triggering the thread, send a data packet to the multiple routing destinations of the object under test module to obtain random stimulus reaching the object under test module.

[0016] For example, in a random stimulus generation device provided in at least one embodiment of the present disclosure, there are N schedulers, and the N schedulers correspond one-to-one to N interfaces used for the module of the object to be tested, each of the N interfaces corresponds to a protocol, and N is an integer greater than or equal to 1.

[0017] For example, in a random stimulus generation device provided by at least one embodiment of the present disclosure, the multiple threads corresponding to each of the schedulers correspond one-to-one to the multiple routing destinations.

[0018] For example, in a random stimulus generation device provided by at least one embodiment of the present disclosure, the scheduler includes a one-to-one stimulus drive adaptation component, and the stimulus drive adaptation component is configured to send the data packet generated by the thread corresponding to the scheduler to the corresponding routing destination of the object module under test through the interface.

[0019] For example, in a random stimulus generation device provided by at least one embodiment of the present disclosure, the N schedulers are one scheduler, and the scheduler is configured to be triggered in parallel between corresponding multiple threads to send data packets to multiple routing destinations of the module under test; or, the N schedulers are multiple schedulers, and the multiple schedulers are configured to be triggered in parallel to send data packets to multiple routing destinations of the module under test.

[0020] For example, in a random incentive generation device provided by at least one embodiment of the present disclosure, the N schedulers include: a first parent class for incentive-driven adaptation, wherein the first parent class is configured to implement a unified packet issuance task, and the unified packet issuance task is configured to call a corresponding packet issuance task according to the type of data packet; a second parent class, wherein the second parent class is an interface control parent class; one or more first subclasses inherited from the first parent class, wherein the one or more first subclasses correspond one-to-one to the interface and each of the first subclasses corresponds to each of the incentive-driven adaptation components; one or more second subclasses inherited from the second parent class, wherein the one or more second subclasses correspond one-to-one to the interface.

[0021] For example, in a random stimulus generation device provided by at least one embodiment of the present disclosure, the scheduler also includes a coverage monitoring component, and the coverage monitoring component is configured to obtain the data packet of the thread corresponding to the scheduler sent by the stimulus-driven adaptation component to collect functional coverage.

[0022] For example, in a random stimulus generation device provided by at least one embodiment of the present disclosure, the scheduler further includes a thread monitoring component, and the thread monitoring component is configured to monitor the execution of the thread and the state of the thread.

[0023] At least one embodiment of the present disclosure provides an electronic device, including: a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the random excitation generation method as described in any one of the above items is implemented.

[0024] At least one embodiment of the present disclosure provides a computer-readable storage medium, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, the random excitation generation method as described in any of the above examples is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0026] Figure 1 A schematic diagram of a random stimulus generation device for chip verification provided in some embodiments of the present disclosure;

[0027] Figure 2 A schematic diagram of a random stimulus generation device for chip verification provided in some other embodiments of the present disclosure;

[0028] Figure 3-Figure 4 A schematic diagram of multi-interface complex stimulus generation and related scheduling provided for some embodiments of the present disclosure;

[0029] Figure 5A-Figure 5B They are Figure 4 A partial schematic diagram of a specific example of .

[0030] Figure 6 A flowchart of a random stimulus generation method for chip verification provided in some embodiments of the present disclosure;

[0031] Figure 7 for Figure 6A flowchart of an execution process of step S2 in FIG.

[0032] Figure 8 A schematic diagram of the structure of an electronic device provided for some embodiments of the present disclosure. DETAILED DESCRIPTION

[0033] The following will be combined with the drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

[0034] Unless otherwise defined, all terms (including technical and scientific terms) used in the embodiments of the present disclosure have the same meanings as commonly understood by those of ordinary skill in the art to which the present disclosure belongs. It should also be understood that terms such as those defined in common dictionaries should be interpreted as having meanings consistent with their meanings in the context of the relevant technology, and should not be interpreted in an idealized or extremely formal sense, unless the embodiments of the present disclosure explicitly define such meanings.

[0035] The words "first", "second" and similar words used in the embodiments of the present disclosure do not indicate any order, quantity or importance, but are only used to distinguish different components. Words such as "one", "an" or "the" and similar words do not indicate a quantity limitation, but indicate the existence of at least one. Similarly, words such as "include" or "comprise" and similar words mean that the elements or objects appearing before the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. Words such as "connect" or "connected" and similar words are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. Flowcharts are used in the embodiments of the present disclosure to illustrate the steps of the method according to the embodiments of the present disclosure. It should be understood that the previous or subsequent steps are not necessarily carried out in order. On the contrary, various steps can be processed in reverse order or simultaneously. At the same time, other operations can also be added to these processes, or one or more steps can be removed from these processes.

[0036] At present, adopting verification methodology is one of the trends of chip verification, and universal verification methodology (UniversalVerificationMethodology, referred to as UVM) is a typical representative thereof. UVM is a universal verification methodology based on SystemVerilog class, and utilizes its reusable components to build a functional verification environment with standardized hierarchy and interface, i.e. UVM verification environment. The UVM verification environment stipulates the basic class (i.e. reusable component) in UVM, for example, sequence editor (Sequencer, also can be called sequencer), monitor (Monitor), exciter (Driver, also can be called driver) etc. and communication interface and function coverage component etc.

[0037] In some current mainstream UVM verification platforms, sequences are used to generate transaction packets in the UVM verification platform and pass them to the exciter in a certain order through a sequencer; for another example, the exciter is used to convert the excitation transaction packet into an interface signal and output it to the design under test (DUT, also known as the object under test) in the UVM verification platform. For example, the monitor may include an initiator monitor (Master Monitor) and a responder monitor (Slave Monitor). The verifier can expand the class he needs on the basis of the basic class, and then connect the communication interfaces of each class with the communication statements of the UVM standard. For example, one or more agents (Agent) plus a scoreboard constitute a simulation environment (ENV, also known as a verification environment), such as a simulation environment is a hierarchical component, which combines interrelated verification components together and encapsulates all verification components for DUT. The test case is the top-level component in the UVM test platform, which is responsible for executing the test and associating the sequence to the sequencer.

[0038] At present, the verification of complex random stimulus scenarios is the focus and difficulty of the verification of complex IP (intellectual property) modules, subsystems, and SoCs (systems on a chip). The verification of traditional complex stimuli lacks clear verification scheme guidance, and the code structure is scattered, the readability is poor, and the review is difficult, which makes it difficult to quantify the verification quality. In addition, traditional complex stimulus verification is often only applied to one project, lacking reusability, scalability, and portability.

[0039] The inventors of the present disclosure have discovered that, under the framework of UVM, there are generally two existing complex random stimulus generation methods: one is to implement tasks (tasks, which are tasks implemented based on SystemVerilog language) for sending different types of stimuli in UVM use cases, and to call related stimulus tasks according to different scenarios in the main_phase of the use case (one of the phases that UVM consumes simulation time, implemented based on tasks); the other is a sequence scheduling implementation based on UVM, in which the sending of different types of stimuli is implemented in respective sequence modules, and then the corresponding sequences are called in the virtual sequencer according to the application scenarios.

[0040] The inventors of the present disclosure have found that both of the above two methods have certain defects. For example, the first method is simple to implement, but lacks reusability, is not convenient for random control, and is difficult to expand to cover sufficiently complex scenes. The second method is slightly more complicated and has certain reusability, but is not scalable enough, lacks versatility, and is difficult to intuitively grasp the incentive coverage results at a higher level.

[0041] In this regard, at least one embodiment of the present disclosure provides a method for generating random stimuli for chip verification, including: obtaining a module of the object under test; obtaining a scheduler based on an interface for the module of the object under test, wherein the scheduler is configured to respectively support protocols corresponding to the interface; obtaining multiple routing destinations based on the module of the object under test; obtaining a thread corresponding to the scheduler based on the scheduler and the multiple routing destinations; triggering the thread of the scheduler to send data packets to the multiple routing destinations of the module of the object under test, so as to obtain random stimuli that reach the module of the object under test.

[0042] The random stimulus generation method in the embodiment of the present disclosure generates complex incentives based on scheduling and packet sending, and can realize complex random incentive verification scenarios of any interface and any combination of scenarios, and has good reusability and scalability.

[0043] At least one embodiment of the present disclosure further provides a random excitation generation device corresponding to the above-mentioned random excitation generation method.

[0044] It should be noted that in the embodiments of the present disclosure, the focus is on explaining the random stimulus generation and scheduling of chip verification. The relevant content of components such as stimulators, monitors, scoreboards, etc. in the general verification methodology of chip verification is not the focus of the description of the embodiments of the present disclosure. It can refer to the relevant existing technology. For the clarity and conciseness of the description in this article, it will not be repeated here.

[0045] The embodiments and examples of the present disclosure are described in detail below with reference to the accompanying drawings.

[0046] Figure 1A schematic diagram of a random stimulus generation device for chip verification provided in some embodiments of the present disclosure.

[0047] For example, Figure 1 As shown, the random stimulus generation device provided by at least one embodiment of the present disclosure includes a DUT module 100 (ie, a design under test, Design Under Test, DUT) and a scheduler 200.

[0048] For example, DUT 100 is a testability design, which can also be called an object to be tested module, which can be an object that a verification engineer is mainly responsible for verifying. For example, if a cache needs to be verified, DUT 100 includes the verified cache. For example, DUT 100 is implemented by corresponding design codes. Of course, this is only exemplary and is not a limitation of the embodiments of the present disclosure. It can be any circuit module or system depending on the chip verification requirements, and it will not be exhaustively listed or repeated here.

[0049] The object under test module 100 of the embodiment of the present disclosure includes multiple routing destinations (Target) 110. For example, Figure 1 In the example, the multiple routing destinations 110 of the object module 100 are respectively recorded as Target0, Target 1, Target 2 to Target n, that is, the multiple routing destinations 110 included in the object module 100 are recorded as n+1 routing destinations 110, where n is an integer greater than 0.

[0050] For example, the scheduler 200 of the embodiment of the present disclosure is configured to be created based on the interface (Port) for the object module 100 to be tested, the scheduler 200 supports the protocols corresponding to the interface respectively, and the scheduler 200 is provided with a thread (Thread) determined based on multiple routing destinations 110. The scheduler 200 is configured to: in response to the triggering thread, send a data packet (Item) to multiple routing destinations 110 of the object module 100 to obtain a random stimulus reaching the object module 100 to be tested. In the embodiment of the present disclosure, Port can be understood as a data sending and / or receiving port of a specific protocol, each data packet can be called an Item, the packet sending component corresponding to the Port can be called a Driver adapter (see below), and the routing destination Target refers to the destination of the Item after routing.

[0051] For example, in some embodiments of the present disclosure, there are N schedulers 200, and the N schedulers 200 correspond one-to-one to N interfaces for the module under test, each of the N interfaces corresponds to a protocol, and N is an integer greater than or equal to 1.

[0052] It should be noted that the protocol in the embodiment of the present disclosure may be a bidirectional protocol (for example, see Figure 1 The bidirectional arrows shown are for exemplary purposes only), or may be a unidirectional protocol, which may be determined based on actual conditions, and the present disclosure does not limit or elaborate on this.

[0053] In some examples, for a bidirectional protocol, the object module 100 under test can also read and write data to the scheduler 200. Of course, this is merely exemplary and is not a limitation of the embodiments of the present disclosure.

[0054] In some examples, the multiple threads corresponding to each scheduler 200 correspond one-to-one to the multiple routing destinations 110 of the object module 100. Figure 1 As shown, the multiple threads corresponding to the scheduler 200 are thread 0, thread 1, and thread n, which are consistent with the number of multiple routing destinations 110 of the object module 100 under test. For example, in the embodiments of the present disclosure, each scheduler 200 supports a protocol and the data packets generated inside the scheduler 200 are sent through the same interface, and in some embodiments of the present disclosure, according to the different routing destinations 110 of the data packets (such as Figure 1 n+1 routing destinations shown) are subdivided into different threads (such as Figure 1 n+1 threads shown).

[0055] In the embodiments of the present disclosure, each thread can individually and randomly constrain a certain number and type of data packets to be sent, thereby constructing a random incentive for the corresponding scenario.

[0056] In some examples of the present disclosure, for threads at the application software level, it is usually based on the business type (for example, a thread can also have multiple data routing destinations). Different business types focus on different scenarios and use different data types, which are not listed here in detail.

[0057] In some examples, the scheduler 200 includes a one-to-one stimulus driver adapter component (Driver adapter) 210, and the stimulus driver adapter component 210 is configured to send a data packet generated by a thread corresponding to the scheduler 200 to a corresponding routing destination 110 of the object module 100 through an interface.

[0058] In some examples, the N schedulers 200 in the random stimulus generation device may be one scheduler 200 (ie, N=1), such as Figure 1 As shown, the scheduler 200 is configured to trigger multiple threads corresponding to it in parallel to send data packets to multiple routing destinations 110 of the object module 100. For example, Figure 1In the example, the parallel triggering of multiple threads corresponding to the scheduler 200 includes: the n+1 threads corresponding to the scheduler 200 can be triggered at the same time, so that the data packets corresponding to these threads are sent to the object under test module 100 at the same time to generate random excitation. For example, in some embodiments of the present disclosure, when multiple threads simultaneously seize the excitation drive adaptation component 210, polling scheduling, weight scheduling or random selection of a thread can be flexibly selected.

[0059] In some embodiments of the present disclosure, each thread can be individually and randomly constrained to send a certain number and type of data packets, and the threads can be triggered in parallel, thereby achieving a random incentive mixing scenario with the same source but different destinations.

[0060] Figure 2 A schematic diagram of a random stimulus generation device for chip verification provided in some other embodiments of the present disclosure.

[0061] In some examples, the N schedulers 200 in the chip verification apparatus may also be multiple schedulers (ie, N is greater than 1) 200. For example, Figure 2 As shown, the test object module 100 has multiple interfaces (such as Figure 2 ), thus, in the verification environment, each interface corresponds to a scheduler 200, so that Figure 2 The plurality of schedulers 200 in the example is n+1 schedulers 200 .

[0062] In some embodiments of the present disclosure, multiple schedulers 200 are configured to be triggered in parallel to send data packets to multiple routing destinations 110 of the object module 100. Figure 2 In the example, the parallel triggering of multiple schedulers 200 means that the sum of all threads corresponding to the multiple schedulers 200 can be triggered at the same time (such as there is no dependency between the threads), so that the data packets corresponding to these threads are sent to the object module 100 to generate random excitation at the same time. The parallel triggering of multiple schedulers 200 in the above embodiment of the present disclosure can be understood as including both the parallel triggering between the schedulers 200 and the parallel triggering between the threads within each scheduler 200.

[0063] In some embodiments of the present disclosure, when there are multiple ports in the module to be tested, the parallel triggering of multiple corresponding schedulers can be used to achieve a multi-port random excitation mixing scenario, thereby realizing verification of complex random excitation scenarios for the current intellectual property (IP) module, chip internal subsystem (Subsystem) and system on chip (SoC).

[0064] For example, Figure 2 As shown, the multiple schedulers 200 are Scheduler 0, Scheduler 1, Scheduler 2, and Scheduler n, respectively; the multiple excitation drive adapter components 210 are Driver adapter 0, Driver adapter 1, Driver adapter 2, and Driver adapter n, respectively; the multiple ports are port 0, port 1, port 2, and port n, respectively; thus, Driver adapter 0 sends the data packet generated by the thread corresponding to scheduler Scheduler 0 to a corresponding routing destination 110 in the object module 100 through the interface port 0; Driver adapter 1 sends the data packet generated by the thread corresponding to scheduler Scheduler 1 to a corresponding routing destination 110 in the object module 100 through the interface port 1; similarly, until Driver adapter n sends the data packet generated by the thread corresponding to scheduler Scheduler n to a corresponding routing destination 110 in the object module 100 through the interface port n. In addition, in some embodiments of the present disclosure, the destination to which the data packet is routed depends on the corresponding relationship between the address allocation and access configuration between the scheduler and the module of the object under test, which may be determined according to the specific situation and will not be elaborated here.

[0065] The embodiments of the present disclosure take the source and routing destination of the data flow as the entry point, and gradually construct complex incentive scenarios from points (such as single thread packet sending) to lines (such as single interface random packet sending) and then to surfaces (such as random packet sending of multiple interface combinations). It can realize complex random incentive verification scenarios of any interface and any combination of scenarios.

[0066] In some examples, the scheduler 200 further includes a coverage monitoring component (Coverage Monitor) 220, which is configured to obtain data packets of threads corresponding to the scheduler sent by the stimulus-driven adapter component 210 to collect functional coverage. Therefore, the embodiments of the present disclosure send data packets generated by different threads to the DUT through an interface through the stimulus-driven adapter component 210 according to certain scheduling rules, and at the same time, a data packet can also be sent to the coverage monitoring component 220 for collecting functional coverage.

[0067] Under the framework of the embodiments of the present disclosure, the source and destination of complex random excitations can be easily obtained at a specific place inside the scheduler, which facilitates the collection of functional coverage and allows the review of verification quality.

[0068] In some examples, the scheduler 200 further includes a thread monitoring component (Thread Monitor) 230 , which is configured to monitor the execution of threads and the status of threads.

[0069] In some examples, before sending the data packet generated by the thread corresponding to the scheduler 200 to the corresponding routing destination 110 of the object module 100 through the interface, the embodiments of the present disclosure also randomly generate data packets through thread control and thread constraints and based on the routing destination; and store the randomly generated data packets in a random data entry queue for use after the thread of the scheduler 200 is triggered to send to the object module 100.

[0070] For example, within a thread, the embodiment of the present disclosure can also generate a certain number of data packets (Items) and store them in a random data item queue (Random ItemQueue) through thread control, thread constraints, and random constraints of the routing destination 110, and then send the Items out by calling the stimulus drive adaptation component 210. In the embodiment of the present disclosure, Item can be understood as a random data packet item, such as a data packet Item having at least data content and access address information. A string of Items placed in a queue forms a random sequence, for example Figure 1 The string of Item 0, Item 1 to Item n in thread 0 can form a random sequence. In the embodiments of the present disclosure, the Random Item Queue is used as a basic sequence for calling and can be used by various protocols, as shown below. For example, in some embodiments of the present disclosure, the Random Item Queue can be generated after the thread is triggered, and generally there may be no other strict restrictions. It can be determined according to the actual situation, and no restrictions or details are given here. In one example, on the basis of a prescribed number, it may be the case that a new data packet is randomly generated after the incentive drive adapter component 210 sends the previous data packet, and then continues to be handed over to the incentive drive adapter component 210. Of course, this is merely exemplary and is not a limitation of the embodiments of the present disclosure.

[0071] The embodiment of the present disclosure abstracts the minimum unit for generating complex incentives into the concept of threads based on routing destinations, and can perform constraint control on each thread individually, so as to facilitate the construction of rich random scenarios. Compared with traditional methods, the implementation method of complex incentives in the embodiment of the present disclosure greatly reduces the number of constructions such as redundant sequences, and can focus on top-level configuration to quickly construct random incentives for corresponding scenarios.

[0072] Figure 3-Figure 4 A schematic diagram of multi-interface complex stimulus generation and related scheduling provided for some embodiments of the present disclosure. Figure 5A-Figure 5B They are Figure 4 A partial schematic diagram of a specific example of .

[0073] For example, Figure 3 As shown, in some embodiments of the present disclosure, the N schedulers 200 further include a first parent class 201, a second parent class 202, and one or more first subclasses 203 (eg, Figure 3 The two first subclasses shown correspond to the first subclass examples of the two interface protocols) and one or more second subclasses 204 (eg, Figure 3 The two second subclasses shown correspond to the second subclass examples of two interface protocols). The first parent class 201 is used to stimulate the base class of the driver adapter, that is, the first parent class 201 is a base class (base_driver_adapter) for defining a Driver adapter. The second parent class 202 is the interface control parent class (port_cfg_base). The embodiments of the present disclosure can define functions in the parent class, thereby defining a general task (such as a unified package sending task).

[0074] In some examples, the one or more first subclasses 203 correspond to the interface one-to-one and each first subclass 203 corresponds to each excitation drive adapter component 210, that is, one-to-one correspondence with the interface protocol. The one or more second subclasses 204 correspond to the interface one-to-one, that is, one-to-one correspondence with the interface protocol.

[0075] For example, for Figure 2 In the example, port 0, port 1, port 2, and port n are provided, and the plurality of first subclasses 203 in the embodiment of the present disclosure are n+1 first subclasses 203 corresponding to each other, and the second subclasses 204 are n+1 second subclasses corresponding to each other. Of course, this is merely exemplary and is not intended to limit the embodiments of the present disclosure.

[0076] For example, Figure 3 and Figure 4As shown, the first parent class 201 is configured to implement a unified packet sending task (task send-item) 207, and the unified packet sending task is configured to call a corresponding packet sending task for the type (Type) of the data packet (Item). For example, the unified packet sending task may be a packet sending task for various types of data packets such as input / output (IO), memory (Memory, abbreviated as MEM), message (Message, abbreviated as MSG), configuration (Configuration, abbreviated as CFG), atomic operation (ATOMIC), message interrupt (MessageInterrupt, abbreviated as MSI), etc. These classes can be understood as basic classes, which support the types required by various interface protocols of the target. For example, the Item type of the Random Item Queue in the thread can be at least one of IO, MEM, MSG, CFG, and ATOMIC, which corresponds to the type of the data packet of the unified packet sending task, and is used to implement the packet sending task (refer to Figure 5B Of course, this is only exemplary and not limiting of the present disclosure.

[0077] For example, Figure 5A and Figure 5B As shown, the first parent class 201 has a virtual task list (virtual tasklist), and each first subclass 203 has an override task list (override task list). There is a matching relationship between the virtual task list and the override task list. For example, the task type of the virtual task list covers the task type of each override task list. For example, the specific implementation of the virtual task list virtual task list and the override task list override task list can be referred to Figure 5B For example, the send_io_item, send_mem_item and other tasks in the figure.

[0078] In some embodiments of the present disclosure, inheritance is a basic mechanism of object-oriented programming, which allows the creation of a new class (which may be called a subclass) to inherit properties and behaviors from an existing class (which may be called a parent class or base class), that is, the subclass can inherit the properties and behaviors of the parent class, and can also add its own unique properties and methods. For example, the way in which the parent class pointer points to the subclass object in the embodiments of the present disclosure can be understood as: the pointer of the parent type points to the instance of its subclass, and the member function in the subclass can be called through the parent class pointer, and the parent class can be extended to multiple types of subclasses, which can improve the reusability and extensibility of the code.

[0079] In some embodiments of the present disclosure, based on the first parent class 201, the second parent class 202, the first subclass 203 and the second subclass 204, the data packet is called and sent to the object under test module 100 by pointing the parent class pointer to the subclass object. In the embodiments of the present disclosure, each subclass does not change the function name of its corresponding parent class relative to the corresponding parent class, that is, the task type is not changed. For the subclass inherited from the corresponding parent class, after the inheritance, the subclass can overwrite the task of sending the data packet for the corresponding driver adapter (that is, implement the corresponding content under the corresponding function name, such as the specific content of how to send a certain type of data packet under a specific protocol), that is, the parent class used for general definition is not used for how to specifically implement the task of sending the packet. In this way, the embodiment of the present disclosure implements calling and sending the data packet by pointing the parent class pointer to the subclass object to complete the task of sending the packet. In this way, on the one hand, it is convenient for top-level management, and the driver adapter is uniformly defined as a parent class type variable, and queues, associative arrays, etc. can be used; on the other hand, it is convenient to formulate a unified random strategy for sending packets, which does not depend on the specific protocol. For example, the first subclass of AXI-driver-adapter below can be used to implement how to send MEM packets under the AXI protocol and the first subclass of PCIe-driver-adapter can be used to implement how to send MEM packets under the PCIe protocol. Of course, this is only exemplary.

[0080] In some embodiments of the present disclosure, the first parent class 201 defines a task type, such as send mem item or sendio item, etc.; the first subclass 203 does not change the task type relative to the first parent class 201 (e.g., for the task of send mem item of the first parent class 201, the first subclass 203 also corresponds to the task of send mem item).

[0081] In some examples, when using the driver adapter to send packets, the packet sending task is called once each time a data packet is obtained from the thread, and the embodiments of the present disclosure only need to call the corresponding task according to the type of the data packet. For example, when the Item is a MEM type data packet, the task of send mem item is called, wherein the virtual task list in the first parent class 201 has the virtual task of send mem item, and the overwrite task list in the first subclass 203 has the overwrite task of send mem item.

[0082] For example, in Figure 3 and Figure 4In the example, since the first parent class is a defined universal base class, the dotted line connection between the packet sending task box 206 and the first parent class 201 is represented, and the packet sending task box 206 and the first subclass 203 are connected. That is, the call of the packet sending task is apparently pointed by a dotted line, but the actual call is pointed by a corresponding solid line, thereby realizing the call of the data packet.

[0083] The embodiment of the present disclosure, based on a certain random data entry queue, transmits data packets by pointing to subclass objects through parent class pointers to achieve the generation of random excitations. For example, for a MEM type data packet to be sent to the corresponding interface, it is randomized under the type constraint (i.e., randomized at the level of each specific protocol interface) and then sent.

[0084] The embodiments of the present disclosure implement complex stimulus generation and scheduling of multiple interfaces by defining a parent class and calling each subclass, which is convenient for management, easy to expand and deploy any protocol type, and has flexible reusability and portability.

[0085] All components in the device of the embodiment of the present disclosure can be abstracted into a general component, and in the application, they can be expanded on the basis of the general component according to different protocols. For example, in most scenarios, it is only necessary to inherit and rewrite the incentive drive adaptation component, and then set corresponding constraint rules for different interfaces, which has good reusability and scalability.

[0086] For example, Figure 3 Examples may include examples of driver adapters for two interface protocols, PCIe and AXI (Advanced extensible Interface, a bus protocol). For example, the first parent class for the driver adapter may be recorded as base_driver_adapter, and the interface control parent class (i.e., the second parent class) may be recorded as port_cfg_base. This is merely exemplary, so that those skilled in the art can understand the technical solutions of the embodiments of the present disclosure, and is not intended to limit the embodiments of the present disclosure.

[0087] For example, Figure 4 , Figure 5A and Figure 5B As shown, the embodiments of the present disclosure illustrate the configuration and scheduling of the Driver adapter for the two interface protocols of PCIe and AXI as follows:

[0088] (1) First, define the first parent class base_driver_adapter of the Driver adapter, declare the sending tasks of all types of data packets (Item) internally without specific implementation, and implement a unified packet sending task (tasksend-item), in which the corresponding packet sending task is called according to the type of data packet, and set an instance of the second parent class port_cfg_base at the same time, such as Figure 5A and Figure 5B shown.

[0089] (2) Implement the first subclass for PCIe and AXI interface protocols respectively (i.e. Figure 3 The two first subclasses 203 shown are respectively denoted as PCIe-driver-adapter and AXI-driver-adapter, which can be referred to Figure 5A ), the two first subclasses 203, PCIe-driver-adapter and AXI-driver-adapter, are inherited from the first parent class base_driver_adapter, and then the corresponding sequence generators (such as Figure 5A The set sequencer (pcie) and setsequencer (axi)) shown in the figure are used to randomly generate the Random Item Queue mentioned above) to implement the packet sending task, and then according to the characteristics of the protocol, only the packet sending task of the data packet type supported by the protocol needs to be implemented.

[0090] (3) Based on the second parent class port_cfg_base, the second subclasses corresponding to the PCIe and AXI interface protocols are extended respectively (i.e. Figure 3 The two second subclasses 204 shown are respectively denoted as PCIe_port_cfg and AXI_port_cfg, which can be referred to Figure 5A ), all routing destinations corresponding to the interface and the address mapping range corresponding to each routing destination are configured internally. For example, in the embodiment of the present disclosure, access to all routing destinations can be achieved through the correspondence between the segments of the address in the configuration table. In addition, the embodiment of the present disclosure can also be extended to add some configuration information specific to the interface (which can be personalized configuration supporting the interface work, such as speed, which is not limited or elaborated here).

[0091] (4) After completing the above operations, use the type conversion function in SystemVerilog (such as the $cast function, such as Figure 5A-Figure 5BThe $cast to pcie type, $cast to axi type) shown in the figure converts the two first subclasses, PCIe-driver-adapter and AXI-driver-adapter, into the base_driver_adapter parent class type, and then assigns them to the driver-adapter in the scheduler corresponding to the PCIe interface and the AXI interface respectively. In this way, the driver-adapter calls the packet sending task once each time it obtains a data packet from the thread. In this way, the extension of the general driver-adapter to the specific protocol driver-adapter is realized, and the sending of the general data packet type is converted into the sending of the data packet type under the specific protocol.

[0092] (5) Implement the coverage monitoring components corresponding to the PCIe and AXI interface protocol items respectively (such as Figure 3 The coverage monitoring components 220a and 220b shown in the figure) send data packets to the corresponding coverage monitoring components (for example, PCIe-driver-adapter corresponds to coverage monitoring component 220a, and AXI-driver-adapter corresponds to coverage monitoring component 220b) at the same time when PCIe-driver-adapter or AXI-driver-adapter calls the packet sending task, thereby completing the collection of functional coverage.

[0093] The PCIe-driver-adapter and AXI-driver-adapter implemented based on some embodiments of the present disclosure can be directly reused from subsystem verification to SoC verification and other projects when the VIP (Verfication IP, code confirmation and verification technology) of PCIe or AXI remains unchanged. For example, if the VIP is changed, only the corresponding driver_adapter data packet sending task needs to be overwritten; when reused in other projects, the random constraint strategy needs to be adjusted accordingly according to the needs.

[0094] The embodiments of the present disclosure utilize the concept of SystemVerilog object-oriented programming to provide a method for controlling the generation of complex stimuli. This method can be abstracted into a general framework. In addition to realizing the specific functions of complex random packet sending, it is also reusable and scalable. All complex scenarios can be easily handled based on the embodiments of the present disclosure.

[0095] It should be noted that in the embodiments of the present disclosure, the random excitation generation device may include more or fewer modules, and the connection relationship between the modules is not limited and can be determined according to actual needs. The specific configuration of each module is not limited.

[0096] Each module in the above embodiment can be configured as software, hardware, firmware or any combination of the above items to perform specific functions. For example, these modules can correspond to a dedicated integrated circuit, can also correspond to pure software code, and can also correspond to a module combining software and hardware.

[0097] It should be noted that although the random excitation generation device is divided into modules for respectively performing corresponding processing when describing it above, it is clear to those skilled in the art that the processing performed by each module can also be performed without any specific module division in the random excitation generation device or without clear demarcation between the modules.

[0098] At least one embodiment of the present disclosure further provides a random excitation generation method for chip verification, which can be implemented based on the random excitation generation device described in any of the above embodiments. The specific implementation and technical effects of the random excitation generation method based on the random excitation generation device can also refer to the random excitation generation device provided in the above embodiments of the present disclosure.

[0099] Figure 6 A flowchart of a random stimulus generation method for chip verification provided in some embodiments of the present disclosure. A detailed description of an example of a random stimulus generation method in an embodiment of the present disclosure is provided below.

[0100] For example, Figure 6 As shown, the random stimulus generation method for chip verification provided by at least one embodiment of the present disclosure includes steps S1 to S5.

[0101] Step S1, obtaining a module of an object to be tested.

[0102] For example, DUT is a testable design, which can also be called an object under test module, and it can be the object that a verification engineer is mainly responsible for verifying.

[0103] Step S2: acquiring a scheduler based on the interface for the module of the object to be tested, wherein the scheduler is configured to support protocols corresponding to the interfaces respectively.

[0104] For example, the scheduler is configured to be created based on an interface for the module of the object under test, and the scheduler supports protocols corresponding to the interface respectively.

[0105] Step S3: Acquire multiple routing destinations based on the module of the object to be tested.

[0106] For example, the object module 100 includes a plurality of routing destinations, where the routing destination refers to the destination where the data packet (Item) is routed.

[0107] Step S4: Based on the scheduler and multiple routing destinations, obtain the thread corresponding to the scheduler.

[0108] For example, some embodiments of the present disclosure subdivide different threads according to different routing destinations of data packets.

[0109] Step S5: trigger the thread of the scheduler to send data packets to multiple routing destinations of the module under test to obtain random stimuli that arrive at the module under test.

[0110] The random stimulus generation method of the embodiment of the present disclosure generates complex incentives based on scheduling packets, and can realize complex random incentive verification scenarios of any interface and any combination of scenarios.

[0111] For example, in step S2, a scheduler is obtained based on the interface used for the object module to be tested, including the following process or steps: in response to the number of interfaces used for the object module to be tested being N interfaces, N schedulers are obtained, wherein the N schedulers correspond one-to-one to the N interfaces, and each of the N interfaces corresponds to a protocol, and N is an integer greater than or equal to 1.

[0112] In some examples, the multiple threads corresponding to each scheduler correspond one-to-one to the multiple routing destinations.

[0113] For example, the above-mentioned step S5 may include the following processes or steps: obtaining the stimulus-driven adaptation component of the scheduler, wherein the stimulus-driven adaptation component corresponds one-to-one to the scheduler; and based on the stimulus-driven adaptation component, sending the data packet generated by the thread corresponding to the scheduler through the interface to the corresponding routing destination of the object module under test.

[0114] In some examples, before sending the data packet generated by the thread corresponding to the scheduler to the corresponding routing destination of the module under test through the interface, the random stimulus generation method of the embodiment of the present disclosure also includes the following processes or steps: randomly generating a data packet through thread control and thread constraints and based on the routing destination; and storing the randomly generated data packet in a random data entry queue for use after the thread of the scheduler is triggered to send it to the module under test.

[0115] The random stimulus generation method of the embodiment of the present disclosure abstracts the minimum unit of complex stimulus generation into the concept of threads based on routing destinations, and can perform constraint control on each thread individually, so as to facilitate the construction of rich random scenarios. Compared with traditional methods, the complex stimulus implementation method of the embodiment of the present disclosure greatly reduces the number of constructions such as redundant sequences, and can focus on the top-level configuration to quickly construct random incentives for corresponding scenarios.

[0116] In some examples, in step S5, triggering the thread of the scheduler to send a data packet to the routing destination of the module under test may include the following processes or steps: in response to N schedulers being one scheduler, multiple threads corresponding to the schedulers are triggered in parallel to send data packets to multiple routing destinations of the module under test; and in response to N schedulers being multiple schedulers, multiple schedulers are triggered in parallel to send data packets to multiple routing destinations of the module under test.

[0117] The embodiment of the present disclosure randomly combines complex random stimulus generation from point (single thread packet) to line (single interface random packet) and then to surface (multiple interface combination random packet) step by step. The top-level structure is clear, which is convenient for setting random verification schemes, and the code has highly visual management. In addition, based on the embodiment of the present disclosure, it is convenient to expand any protocol type, easy to deploy, and has flexible reusability and portability, and can be widely used in various IP, subsystem and SoC verification.

[0118] Figure 7 for Figure 6 A flowchart of an execution process of step S2 in FIG. Figure 7 As shown, an example of step S2 includes at least steps S21 to S24.

[0119] Step S21, defining a first parent class for incentive-driven adaptation, wherein the first parent class is configured to implement a unified packet sending task, and the unified packet sending task is configured to call a corresponding packet sending task according to the type of the data packet.

[0120] Step S22: define a second parent class, wherein the second parent class is an interface control parent class.

[0121] Step S23: Implement one or more first subclasses inherited from the first parent class based on the first parent class, wherein the one or more first subclasses correspond to the interface one-to-one and each first subclass corresponds to each excitation drive adapter component.

[0122] Step S24: Implement one or more second subclasses inherited from the second parent class based on the second parent class, wherein the one or more second subclasses correspond to the interface one-to-one.

[0123] In some examples, the above-mentioned incentive-driven adaptation component sends the data packet generated by the thread corresponding to the scheduler to the corresponding routing destination of the object module under test through the interface, which can include the following processes or steps: based on the first parent class, the second parent class, the first subclass and the second subclass, the data packet is called and sent to the object module under test by pointing to the subclass object through the parent class pointer.

[0124] The embodiments of the present disclosure can abstract the complex stimulus random generation method into a general framework, which is not limited to a specific protocol. Under this framework, random stimulus generation of any protocol can be expanded and realized, and has flexible reusability and portability.

[0125] Figure 8 A schematic diagram of the structure of an electronic device provided in at least one embodiment of the present disclosure.

[0126] For example, Figure 8 As shown, the electronic device 300 provided by at least one embodiment of the present disclosure includes a processor 310 and a memory 320, wherein the memory 320 stores a computer program, and when the computer program is executed by the processor 310, the random excitation generation method of at least some embodiments of the present disclosure is implemented.

[0127] The electronic devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as laptop computers, tablet computers, etc. and fixed terminals such as desktop computers, etc. Figure 8 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0128] For example, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. When the computer program is executed by a processor, the random excitation generation method of the embodiment of the present disclosure is executed.

[0129] It should be noted that the computer-readable medium disclosed above may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, 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), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In an embodiment of the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, device or device. In an embodiment of the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0130] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0131] It should be noted that, in the embodiment of the present disclosure, the specific functions and technical effects of the electronic device 300 can refer to the above description of the random excitation generation method, which will not be repeated here.

[0132] There are a few points to note:

[0133] (1) The drawings of the embodiments of the present disclosure only relate to the structures involved in the embodiments of the present disclosure, and other structures may refer to the general design.

[0134] (2) In the absence of conflict, the embodiments of the present disclosure and the features therein may be combined with each other to obtain new embodiments.

[0135] The above are only specific implementations of the present disclosure, but the protection scope of the present disclosure is not limited thereto, and the protection scope of the present disclosure shall be based on the protection scope of the claims.

Claims

1. A random stimulus generation method for chip verification, comprising: Get the module of the object to be tested; Acquiring a scheduler based on an interface for the module of the object under test, wherein the scheduler is configured to support protocols corresponding to the interfaces respectively; Acquire multiple routing destinations based on the object module to be tested; Based on the scheduler and the multiple routing destinations, obtaining a thread corresponding to the scheduler; The thread of the scheduler is triggered to send data packets to multiple routing destinations of the module under test to obtain random stimuli that arrive at the module under test.

2. The random excitation generation method according to claim 1, wherein: Acquiring a scheduler based on an interface for the module of the object to be tested, comprising: In response to the number of interfaces for the object module to be tested being N, N schedulers are obtained, wherein the N schedulers correspond one-to-one to the N interfaces, and each of the N interfaces corresponds to a protocol, and N is an integer greater than or equal to 1.

3. The random excitation generation method according to claim 1, wherein: The multiple threads corresponding to each of the schedulers correspond one-to-one to the multiple routing destinations.

4. The random stimulus generation method according to claim 1, wherein: Triggering the thread of the scheduler to send data packets to multiple routing destinations of the module under test, including: Acquire an excitation drive adapter component of the scheduler, wherein the excitation drive adapter component corresponds to the scheduler one by one; Based on the stimulus-driven adaptation component, the data packet generated by the thread corresponding to the scheduler is sent to the corresponding routing destination of the object module under test through the interface.

5. The random excitation generation method according to claim 4, wherein: Before sending the data packet generated by the thread corresponding to the scheduler to the corresponding routing destination of the object module under test through the interface, the method further includes: Randomly generate data packets through thread control and thread constraint and based on the routing destination; The randomly generated data packets are stored in a random data entry queue for use after the thread of the scheduler is triggered to send to the module of the object to be tested.

6. The random excitation generation method according to claim 2, wherein: Triggering the thread of the scheduler to send a data packet to the routing destination of the module under test, including: In response to the N schedulers being one scheduler, multiple threads corresponding to the schedulers are triggered in parallel to send data packets to multiple routing destinations of the module under test; In response to the N schedulers being a plurality of schedulers, the plurality of schedulers are triggered in parallel to send data packets to a plurality of routing destinations of the module under test.

7. The random excitation generation method according to claim 4, wherein: Acquiring a scheduler based on an interface for the module of the object to be tested, comprising: Define a first parent class for incentive-driven adaptation, wherein the first parent class is configured to implement a unified packet sending task, and the unified packet sending task is configured to call a corresponding packet sending task according to the type of the data packet; Define a second parent class, wherein the second parent class is an interface control parent class; Implementing one or more first subclasses inherited from the first parent class based on the first parent class, wherein the one or more first subclasses correspond to the interfaces one-to-one and each of the first subclasses corresponds to each of the excitation drive adapter components; One or more second subclasses inherited from the second parent class are implemented based on the second parent class, wherein the one or more second subclasses correspond to the interface one by one.

8. The random excitation generation method according to claim 7, wherein: Based on the stimulus-driven adapter component, sending the data packet generated by the thread corresponding to the scheduler to the corresponding routing destination of the object under test module through the interface includes: Based on the first parent class, the second parent class, the first subclass and the second subclass, the data packet is called and sent to the object under test module by pointing the parent class pointer to the subclass object.

9. The random excitation generation method according to claim 4, wherein: The scheduler further includes a coverage monitoring component, and the method further includes: In response to triggering the thread of the scheduler, the stimulus-driven adaptation component sends a data packet of the thread corresponding to the scheduler to the coverage monitoring component of the scheduler to collect functional coverage.

10. A random stimulus generation device for chip verification, comprising: The object under test module includes multiple routing destinations; A scheduler is configured to be created based on an interface for the module of the object under test, wherein the scheduler supports protocols corresponding to the interface respectively, and the scheduler is provided with threads determined based on multiple routing destinations, The scheduler is configured to, in response to triggering the thread, send data packets to multiple routing destinations of the module under test to obtain random stimuli that arrive at the module under test.

11. The random excitation generating device according to claim 10, wherein: There are N schedulers, and the N schedulers correspond one-to-one to the N interfaces used for the module of the object to be tested, each of the N interfaces corresponds to a protocol, and N is an integer greater than or equal to 1.

12. The random excitation generating device according to claim 10, wherein: The multiple threads corresponding to each of the schedulers correspond one-to-one to the multiple routing destinations.

13. The random excitation generating device according to claim 11, wherein: The scheduler includes a one-to-one stimulus drive adapter component, and the stimulus drive adapter component is configured to send the data packet generated by the thread corresponding to the scheduler to the corresponding routing destination of the object module under test through the interface.

14. The random excitation generating device according to claim 11, wherein: The N schedulers are one scheduler, and the scheduler is configured to trigger the corresponding multiple threads in parallel to send data packets to multiple routing destinations of the module under test; or, The N schedulers are a plurality of schedulers, and the plurality of schedulers are configured to be triggered in parallel to send data packets to a plurality of routing destinations of the module under test.

15. The random excitation generating device according to claim 13, wherein: The N schedulers include: A first parent class for stimulating drive adaptation, wherein the first parent class is configured to implement a unified packet sending task, and the unified packet sending task is configured to call a corresponding packet sending task according to the type of the data packet; A second parent class, wherein the second parent class is an interface control parent class; One or more first subclasses inherited from the first parent class, wherein the one or more first subclasses correspond to the interfaces one-to-one and each of the first subclasses corresponds to each of the excitation drive adapter components; One or more second subclasses inherited from the second parent class, wherein the one or more second subclasses correspond to the interface one-to-one.

16. The random excitation generating device according to claim 13, wherein: The scheduler further includes a coverage monitoring component, and the coverage monitoring component is configured to obtain a data packet of a thread corresponding to the scheduler sent by the stimulus-driven adaptation component to collect functional coverage.

17. The random excitation generating device according to claim 13, wherein: The scheduler further includes a thread monitoring component configured to monitor the execution of threads and the status of threads.

18. An electronic device, comprising: processor and memory, Wherein, a computer program is stored in the memory, and when the computer program is executed by the processor, the random excitation generation method according to any one of claims 1 to 9 is implemented.

19. A computer-readable storage medium, wherein: The storage medium stores a computer program, and when the computer program is executed by a processor, the random excitation generation method according to any one of claims 1 to 9 is implemented.