Multidimensional verification methods, systems, media, and terminals for simulating excitation connectivity in mixed-signal simulation

By employing a multi-dimensional verification method and utilizing verification information such as simulation logs, node mappings, and compilation information, the problem of abnormal simulation stimulus connections was resolved, ensuring effective connectivity between the simulation stimulus and the simulation IP port, and improving the accuracy and efficiency of simulation verification.

CN123070026APending Publication Date: 2026-11-10SHANGHAI QISHUAN GUANGQI INFORMATION TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611552735.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-10-09
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

In existing mixed-signal simulation technology, the simulated excitation may be connected to non-target nodes or not actually applied to the simulated IP port, resulting in inconsistencies between the simulated waveform and the actual excitation connectivity. There is a lack of effective connectivity verification mechanism, making it difficult to identify problems where the waveform has a value but is not actually connected, and the efficiency of troubleshooting is low.

Method used

By acquiring verification information generated during the mixed-signal simulation process, including simulation logs, node mapping information, compilation verification information, port mapping information, interface element information, and simulation output information, multidimensional verification is performed to determine the connectivity between the simulated stimulus and the target simulated IP.

Benefits of technology

It improves the accuracy of simulation excitation connectivity judgment, reduces the difficulty of simulation anomaly troubleshooting, and enhances the efficiency of mixed-signal simulation verification.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123070026A_ABST
    Figure CN123070026A_ABST
Patent Text Reader

Abstract

This application provides a multi-dimensional verification method, system, medium, and terminal for the connectivity of simulated excitations in mixed-signal simulation. It acquires verification information generated during the mixed-signal simulation process, including first-type and second-type verification information; performs a first verification based on the first-type verification information to determine whether the simulated netlist corresponding to the target simulated IP has been loaded and expanded by the simulator; performs a second verification based on the second-type verification information to determine whether the consistency condition is met between the excitation node corresponding to the simulated excitation and the target port node corresponding to the target simulated IP; and determines the connectivity state between the simulated excitation and the target simulated IP based on the execution results of the first and second verifications. This application can verify the connectivity state of simulated excitations from two aspects: the simulated netlist state and the correspondence between excitation nodes, solving the problem in existing mixed-signal simulations where the waveform is normal but the excitation is not actually applied to the simulated IP port, and lacking an effective connectivity verification mechanism.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of simulation verification, and in particular to a multidimensional verification method, system, medium, and terminal for simulating the connectivity of excitations in mixed-signal simulation. Background Technology

[0002] With the continuous development of integrated circuit technology, chip systems are gradually evolving towards higher integration and multi-functionality. Mixed-signal chips, which combine digital and analog circuits, are widely used in data conversion, power management, sensing interfaces, and communication control. Since mixed-signal chips contain both digital logic processing modules and analog signal processing modules, mixed-signal simulation technology is needed during chip design verification to jointly verify the digital circuits, analog circuits, and their interactions. This improves chip design reliability and reduces post-tape-out modification costs.

[0003] Currently, in chip-level mixed-signal simulation, co-simulation is typically achieved by using digital and analog simulators working together. The digital simulator (e.g., VCS) performs digital circuit simulation, while the analog simulator (e.g., XA) performs analog circuit simulation. Signal exchange between the digital and analog domains is achieved through D2A (digital-to-analog) and A2D (analog-to-digital) interfaces. For analog IP (intellectual property core, referring to reusable integrated circuit modules), its power supply, bias, and other stimuli are typically generated by voltage and current sources provided by the SPICE (analog circuit simulation language). In existing technologies, after simulation, engineers usually check the simulation waveform to determine if the stimulus was correctly injected. For example, they use waveform tools to check if the VDD node voltage reaches the expected 3.3V, or to determine if the stimulus signal meets the expected level or timing characteristics.

[0004] However, existing waveform observation-based methods have certain limitations. During mixed-signal simulations, the SPICE excitation source may actually be connected to an isolated floating node instead of the actual port of the analog IP. In this case, although the waveform shows normal excitation source voltage or current values, the analog IP port does not actually receive the excitation, rendering the simulation results invalid. For example, a 3.3V voltage source connected to a floating node will still show a normal waveform, but this voltage does not drive the AVDD port of the analog IP. Furthermore, during the mixed-signal simulation compilation process, EDA (Electronic Design Automation) tools may convert the node names in the SPICE netlist and generate a skeleton file (e.g., sklt.ntl), which records the port node information of the analog IP instance during co-simulation. When the node names in the SPICE source are inconsistent with the port node names in the skeleton file—for example, due to different case or missing hierarchical path information—although the EDA tool may allow the compilation process to pass normally due to its case-insensitive nature, the actual connection may point to the wrong node, causing the excitation to fail to apply to the analog IP. Meanwhile, when the port names of Verilog shell modules do not completely match the port names of SPICE subcircuits, EDA tools may silently map the ports to an unconnected state without generating obvious errors, resulting in incorrect signal correspondence between the digital and analog sides. Furthermore, when some ports are not recognized as valid drivers, the D2A / A2D interface may be optimized away by the optimizer, causing the analog side to be unable to obtain valid drive.

[0005] Therefore, existing mixed-signal simulation technology has the following main shortcomings: On the one hand, relying solely on simulation waveforms to determine the excitation state cannot identify hidden problems such as waveforms having values ​​but actual disconnections, easily leading to misjudgments of simulation results; on the other hand, existing technologies lack a systematic verification mechanism for the connectivity of analog excitations. When simulation anomalies occur, engineers need to repeatedly check the RTL (Register Transfer Level, a digital circuit description level), netlist, and waveform signals, making it difficult to locate the problem in a timely manner. Furthermore, existing methods struggle to effectively distinguish between different fault types, such as incomplete analog netlist expansion, incorrect node connections, abnormal port mapping, and abnormal analog-digital interface, resulting in low troubleshooting efficiency.

[0006] In summary, existing technologies still lack a technical solution to effectively determine the connectivity status of simulated excitations, improve the accuracy of connectivity judgment, reduce the difficulty of troubleshooting simulation anomalies, and enhance the verification efficiency of mixed-signal simulations, in order to address the potential issues of connection anomalies and waveform inconsistencies between simulated excitations and actual connection states during mixed-signal simulations. Summary of the Invention

[0007] In view of the shortcomings of the prior art described above, the purpose of this invention is to provide a multi-dimensional verification method, system, medium and terminal for the connectivity of simulated excitations in mixed-signal simulation, to solve the technical problem that in the existing mixed-signal simulation process, the simulated excitations may be connected to non-target nodes or not actually applied to the simulated IP ports, resulting in inconsistencies between the simulation waveform and the actual excitation connectivity state, and the lack of an effective connectivity verification mechanism.

[0008] To achieve the above and other related objectives, this application provides a method comprising: acquiring verification information generated during a mixed-signal simulation, the verification information including a first type of verification information and a second type of verification information; performing a first verification based on the first type of verification information to determine whether the simulated netlist corresponding to the target simulated IP is loaded and expanded by the simulation simulator; performing a second verification based on the second type of verification information to determine whether a consistency condition is met between the stimulus node corresponding to the simulated stimulus and the target port node corresponding to the target simulated IP; and determining the connectivity state between the simulated stimulus and the target simulated IP based on the execution results of the first verification and the second verification.

[0009] In some embodiments of the first aspect of this application, the first type of verification information includes simulation log information generated by a simulator; performing a first verification based on the first type of verification information includes: obtaining sub-circuit connectivity construction information, the number of sub-circuit definitions, and the number of sub-circuit usages corresponding to the target simulation IP in the simulation log information; determining whether the simulation netlist corresponding to the target simulation IP is loaded and expanded by the simulator based on the sub-circuit connectivity construction information, the number of sub-circuit definitions, and the number of sub-circuit usages; and determining that the first verification is passed when the simulation log information contains the sub-circuit connectivity construction information corresponding to the target simulation IP and the number of sub-circuit definitions matches the number of sub-circuit usages.

[0010] In some embodiments of the first aspect of this application, the second type of verification information includes node mapping information generated by the co-simulation compilation process; performing a second verification based on the second type of verification information includes: obtaining the target port node corresponding to the target simulated IP in the node mapping information; matching the correspondence between the simulated stimulus corresponding to the stimulus node and the target port node; determining whether the simulated stimulus corresponding to the stimulus node and the target port node meet the consistency condition based on the matching result; wherein, the consistency condition includes the node name of the simulated stimulus corresponding to the stimulus node and the target port node being consistent and the hierarchical path being consistent.

[0011] In some embodiments of the first aspect of this application, the verification information further includes compilation verification information, which is used to verify whether the mixed-signal simulation configuration is correctly identified by the compiler; the compilation verification information includes compilation logs generated by the co-simulation compiler during the compilation phase; verifying whether the mixed-signal simulation configuration is correctly identified by the compiler according to the compilation verification information includes: verifying whether the mixed-signal configuration instructions in the compilation log are correctly parsed; verifying whether there are error-level errors in the compilation log; when the mixed-signal configuration instructions are not correctly parsed, or when there are error-level errors, determining that the mixed-signal simulation configuration verification fails.

[0012] In some embodiments of the first aspect of this application, the verification information further includes port mapping information, which is used to verify whether a corresponding mapping relationship is established between digital-side module ports and analog-side sub-circuit ports; the port mapping information includes a port mapping report generated by the co-emulation compiler during the compilation phase; verifying whether a corresponding mapping relationship is established between digital-side module ports and analog-side sub-circuit ports according to the port mapping information includes: verifying whether a corresponding mapping relationship based on port name is established between digital-side module ports and analog-side sub-circuit ports in the port mapping report; verifying whether all declared ports in the port mapping report have been mapped and whether there are no unmapped port markers; when no corresponding mapping relationship is established between the digital-side module ports and the analog-side sub-circuit ports, or when there are unmapped port markers, it is determined that the mapping relationship verification has failed.

[0013] In some embodiments of the first aspect of this application, the verification information further includes interface element information, which is used to verify whether the configured D2A interface and A2D interface are identified as mixed-signal interface elements; the interface element information includes an interface element report generated by the co-simulation compiler during the compilation phase; verifying whether the configured D2A interface and A2D interface are identified as mixed-signal interface elements according to the interface element information includes: obtaining the D2A interface and A2D interface configured in the mixed-signal configuration file; obtaining the interface element in the interface element list corresponding to the interface element report; determining whether the D2A interface and A2D interface both exist in the interface element list; when the interface element list contains the interface element corresponding to the D2A interface and A2D interface, and the interface direction corresponding to the interface element is consistent with the configuration direction in the mixed-signal configuration file, the interface element verification is determined to be successful.

[0014] In some embodiments of the first aspect of this application, the verification information further includes simulation output information, which is used to verify whether the output signal of the target analog IP has undergone a valid change; the simulation output information includes simulation output log information and / or waveform information generated during the mixed-signal simulation; verifying whether the output signal of the target analog IP has undergone a valid change based on the simulation output information includes: obtaining change information of the corresponding output signal of the target analog IP from the simulation output log information and / or the waveform information; determining whether the output signal of the target analog IP has undergone a valid change based on the change information of the output signal; and determining that the simulation output verification is passed when the output signal of the target analog IP undergoes a valid change within the simulation time range.

[0015] To achieve the above and other related objectives, a second aspect of this application provides a multi-dimensional verification system for the connectivity of simulated excitations in mixed-signal simulation, comprising: an information acquisition module for acquiring verification information generated during the mixed-signal simulation process, the verification information including a first type of verification information and a second type of verification information; a first verification module for performing a first verification based on the first type of verification information to determine whether the simulated netlist corresponding to the target simulated IP is loaded and expanded by the simulator; a second verification module for performing a second verification based on the second type of verification information to determine whether the consistency condition is met between the excitation node corresponding to the simulated excitation and the target port node corresponding to the target simulated IP; and a result determination module for determining the connectivity state between the simulated excitation and the target simulated IP based on the execution results of the first verification and the second verification.

[0016] To achieve the above and other related objectives, a third aspect of this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a multidimensional verification method for simulating the connectivity of analog-digital hybrid simulation.

[0017] To achieve the above and other related objectives, a fourth aspect of the present invention provides an electronic terminal, including a memory, a processor, and a computer program stored in the memory; the processor executes the computer program to implement a multidimensional verification method for simulating the connectivity of simulated excitations in the mixed-signal simulation.

[0018] As described above, the multi-dimensional verification method, system, medium, and terminal for simulated excitation connectivity in mixed-signal simulation of this application have the following beneficial effects: This application obtains verification information generated during the mixed-signal simulation process, including a first type of verification information and a second type of verification information; performs a first verification based on the first type of verification information to determine whether the simulated netlist corresponding to the target simulated IP is loaded and expanded by the simulator; performs a second verification based on the second type of verification information to determine whether the consistency condition is met between the excitation node corresponding to the simulated excitation and the target port node corresponding to the target simulated IP; and determines the connectivity state between the simulated excitation and the target simulated IP based on the execution results of the first and second verifications. Through the above method, this application can verify the connectivity state of the simulated excitation from two aspects: the simulated netlist state and the correspondence between excitation nodes, thereby solving the technical problem in existing mixed-signal simulation processes where simulated excitations may be connected to non-target nodes or not actually applied to the simulated IP port, resulting in inconsistencies between the simulated waveform and the actual excitation connectivity state, and lacking an effective connectivity verification mechanism. Attached Figure Description

[0019] Figure 1 The diagram shows a flowchart of a multidimensional verification method for simulating excitation connectivity in a mixed-signal simulation according to an embodiment of the present invention.

[0020] Figure 2 The diagram shows a flowchart of performing a first verification based on the first type of verification information in one embodiment of the present invention.

[0021] Figure 3 This is a schematic diagram illustrating the process of performing a second verification based on the second type of verification information in one embodiment of the present invention.

[0022] Figure 4 The diagram shown is a schematic representation of a multidimensional verification system for simulating excitation connectivity in a mixed-signal simulation according to an embodiment of the present invention.

[0023] Figure 5 The diagram shown is an electronic terminal according to an embodiment of the present invention. Detailed Implementation

[0024] The following specific examples illustrate the implementation of this application. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. This application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be noted that, unless otherwise specified, the following embodiments and features in the embodiments can be combined with each other.

[0025] It should be noted that in the following description, reference is made to the accompanying drawings, which illustrate several embodiments of the present invention. It should be understood that other embodiments may also be used. In the embodiments of the present invention, the terms "first," "second," etc., are used to distinguish identical or similar items with substantially the same function and effect, without limiting their order. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or execution order, and that "first," "second," etc., are not necessarily different.

[0026] Furthermore, in the embodiments of the present invention, the words "exemplary" or "for example" indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the present invention should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0027] Furthermore, in this embodiment of the invention, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0028] The present invention provides a multi-dimensional verification method, system, medium, and terminal for simulating the connectivity of analog excitations in mixed-signal simulation. This method is applicable to integrated circuit verification scenarios involving the co-simulation of digital and analog circuits in the chip design process, including the mixed-signal simulation verification stage of data conversion chips, power management chips, sensor interface chips, communication chips, and system-on-a-chip (SoC) containing analog IP modules. This method can be applied to EDA verification processes that employ both digital and analog simulators, such as mixed-signal simulation environments built using digital simulators like VCS and Xcelium, and analog simulators like XA, CustomSim, HSPICE, and APS. It is suitable for chip design verification and simulation testing scenarios that include analog IP modules such as analog-to-digital converters. In stages of the chip design cycle, such as register transfer level (RTL) verification, gate-level netlist simulation, mixed-signal full-chip simulation, and post-simulation, this method can verify the connectivity of analog excitations based on the verification information generated during mixed-signal simulation. It can identify invalid simulation results caused by factors such as excitation sources being connected to isolated floating nodes, inconsistent node names, missing hierarchical paths, abnormal digital-analog port mapping, and abnormal mixed-signal interfaces, thereby reducing the difficulty of troubleshooting mixed-signal simulation anomalies and improving the efficiency of chip design verification.

[0029] Specifically, in the technical solution of this invention, the invention acquires verification information generated during the mixed-signal simulation process, the verification information including a first type of verification information and a second type of verification information; performs a first verification based on the first type of verification information to determine whether the simulated netlist corresponding to the target simulated IP is loaded and expanded by the simulator; performs a second verification based on the second type of verification information to determine whether the consistency condition is met between the stimulus node corresponding to the simulated stimulus and the target port node corresponding to the target simulated IP; and determines the connectivity state between the simulated stimulus and the target simulated IP based on the execution results of the first and second verifications.

[0030] The technical solutions in the embodiments of the present invention will be further described in detail below with reference to the embodiments and accompanying drawings. 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 invention.

[0031] like Figure 1 The diagram illustrates a flowchart of a multidimensional verification method for simulating excitation connectivity in mixed-signal simulation according to an embodiment of the present invention. The multidimensional verification method for simulating excitation connectivity in mixed-signal simulation in this embodiment includes the following steps:

[0032] Step S11: Obtain the verification information generated during the mixed-signal simulation process. The verification information includes a first type of verification information and a second type of verification information.

[0033] In this embodiment, the mixed-signal simulation refers to a simulation method in which digital circuit simulation and analog circuit simulation are executed collaboratively. A digital simulator (such as VCS, a digital circuit simulation tool) is used to perform digital circuit simulation, and an analog simulator (such as XA, an analog circuit simulation tool) is used to perform analog circuit simulation. The digital simulator and the analog simulator communicate via D2A (Digital to Analog) and A2D (Analog to Digital) interfaces to achieve signal interaction between the digital and analog domains. It should be noted that in chip-level mixed-signal simulation, the analog IP (Intellectual Property) refers to a reusable integrated circuit module. During mixed-signal simulation, the power supply, bias, and other stimuli of the analog IP are generated by voltage and current sources provided by the SPICE (Simulation Program with Integrated Circuit Emphasis) side and used to drive the corresponding analog IP. Therefore, verifying whether the SPICE stimulus source is actually connected to the actual port of the target analog IP is crucial to ensuring the validity of the simulation results.

[0034] In some optional implementations, the mixed-signal simulation environment includes a digital-side simulation environment, an analog-side simulation environment, a mixed-signal configuration environment, and an excitation input environment. On the digital side, a digital simulator is used to compile the entire chip's RTL (Register Transfer Level) and a test platform. The analog IP participates in co-simulation as a Verilog wrapper (a wrapper module, here referring to a shell module that only retains port definitions). On the analog side, an analog simulator is used to solve the encrypted SPICE netlist corresponding to the analog IP. The SPICE netlist contains multiple sub-circuit definitions. The mixed-signal configuration file is used to configure the D2A and A2D interfaces. The top-level SPICE file provides multiple voltage and current sources, used to provide power domain bias and input signal excitation, respectively.

[0035] In this embodiment, the verification information refers to log files, report files, and other information generated by the corresponding simulation tool during the compilation, simulation startup, and simulation execution phases of the mixed-signal simulation. To determine whether the simulated stimulus truly affects the target simulated IP, it is necessary to acquire the verification information generated during the mixed-signal simulation process and perform multi-dimensional verification based on this information. Specifically, the verification information generated during the mixed-signal simulation process includes a first type of verification information and a second type of verification information. The first type of verification information is used to perform a first verification to determine whether the simulated netlist corresponding to the target simulated IP has been loaded and expanded by the simulator; the second type of verification information is used to perform a second verification to determine whether the consistency condition is met between the stimulus node corresponding to the simulated stimulus and the target port node corresponding to the target simulated IP. In this embodiment, the first verification is used to verify whether the simulated netlist corresponding to the target simulated IP has actually entered the simulation processing flow. The second verification is used to verify whether the node corresponding to the simulated stimulus corresponds to the actual port node of the target simulated IP. By acquiring the first type of verification information and the second type of verification information, and performing the first and second verifications respectively, the connectivity status between the simulated stimulus and the target simulated IP can be determined from two aspects: the simulated netlist status and the correspondence between stimulus nodes.

[0036] In one embodiment of this application, the verification information further includes at least one of compilation verification information, port mapping information, interface element information, and simulation output information. Specifically, the compilation verification information verifies whether the mixed-signal simulation configuration is correctly recognized by the compiler; the port mapping information verifies whether a corresponding mapping relationship is established between the digital-side module ports and the analog-side sub-circuit ports; the interface element information verifies whether the configured D2A and A2D interfaces are recognized as mixed-signal interface elements; and the simulation output information verifies whether the target analog IP output signal undergoes a valid change. Each of these types of verification information corresponds to a different verification dimension, and the specific verification methods will be described in detail in subsequent related steps.

[0037] Step S12: Based on the first type of verification information, perform the first verification to determine whether the simulated netlist corresponding to the target simulated IP has been loaded and expanded by the simulation simulator.

[0038] In one embodiment of this application, the first type of verification information includes simulation log information generated by the simulator. The simulation log information is a log file automatically generated during the simulator's startup process, used to record netlist parsing, sub-circuit expansion, device and node statistics, and connectivity construction information during the simulation process. For example, in an XA simulator, the simulation log information can be xa.log; in other simulation environments, a log file containing corresponding verification information can also be used. By performing the first verification, it can be determined whether the simulation netlist corresponding to the target simulation IP has been loaded and expanded by the simulator.

[0039] In some alternative implementations, such as Figure 2 As shown, performing the first verification based on the first type of verification information includes:

[0040] Step S121: Obtain the sub-circuit connectivity construction information corresponding to the target simulation IP in the simulation log information.

[0041] In this embodiment, the simulation log information is a log file automatically generated during the startup of the simulator. It records netlist parsing, subcircuit decomposition, device and node statistics, and connectivity building information during the simulation process. The subcircuit (subckt) refers to the module definition in the SPICE netlist. The subcircuit connectivity building information refers to the log records output by the simulator when establishing the internal connections of the subcircuit, such as "Building connectivity for subckt" appearing in the xa.log file of the XA tool.<cell_name> Log messages in the format "" indicate that the simulator has performed connectivity builds for the corresponding sub-circuit.

[0042] In some optional implementations, the presence of subcircuit connectivity building information corresponding to the target simulated IP in the simulation log information determines whether the simulator has established a connection relationship for the corresponding simulated IP. For example, the simulation log information may contain entries such as "Building connectivity for subcircuit".<cell_name> "and other connectivity building information.

[0043] Step S122: Obtain the number of sub-circuit definitions and the number of sub-circuits used corresponding to the target simulation IP in the simulation log information.

[0044] In this embodiment, the number of subcircuit definitions refers to the total number of subcircuit definitions in the SPICE netlist, and the number of subcircuit uses refers to the total number of subcircuit calls by the simulator during the actual simulation. In mixed-signal simulation, if the SPICE netlist of the analog IP is correctly loaded and expanded by the simulator, the number of subcircuit definitions should match the number of subcircuit uses, and this number should be significantly greater than the case where only external voltage and current sources are included.

[0045] Step S123: Based on the sub-circuit connectivity construction information, the number of sub-circuit definitions, and the number of sub-circuit usages, determine whether the simulation netlist corresponding to the target simulation IP is loaded and expanded by the simulation simulator.

[0046] Specifically, when the simulation log information contains subcircuit connectivity building information corresponding to the target simulation IP (e.g., "Building connectivity for subcircuit"),<cell_name> If the number of sub-circuit definitions matches the number of sub-circuit used, the simulation netlist expansion status corresponding to the first verification is determined to meet the preset conditions. For example, if the simulation IP contains 342 sub-circuit definitions, the simulation log information should display "SubcktDefined / Used: 342 / 342". At this time, it is determined that the simulation netlist corresponding to the target simulation IP has been loaded and expanded by the simulation simulator, and the first verification is passed.

[0047] Conversely, if the element / node statistics in the simulation log information only include information corresponding to external voltage and current sources, but lack information on internal sub-circuits and nodes of the target simulation IP, it indicates that the simulation netlist corresponding to the target simulation IP has not been expanded. In this case, the first verification fails, indicating that the target simulation IP has not entered the expected simulation process.

[0048] Step S13: Perform a second verification based on the second type of verification information to determine whether the consistency condition is met between the incentive node corresponding to the simulated incentive and the target port node corresponding to the target simulated IP.

[0049] It should be noted that the purpose of the second verification is to confirm whether a correct one-to-one correspondence has been established between the excitation node connected to the SPICE excitation source and the target port node of the simulated IP instance. This verification step is used to eliminate the illusion of "waveform has values ​​but is not actually connected" caused by inconsistent node names (including inconsistent capitalization or missing hierarchical paths).

[0050] In one embodiment of this application, the second type of verification information includes node mapping information generated by the co-simulation compilation process. The node mapping information is used to represent the information of the port nodes corresponding to the simulated IP instances during the co-simulation process. The node mapping information is contained in the skeleton file generated by the co-simulation compiler (such as the sklt.ntl file generated by the VCS tool in the simv.daidir directory). The skeleton file is an intermediate file automatically generated by the compiler when mapping the digital-side Verilog module hierarchy to the analog-side SPICE sub-circuit ports, recording the port name and its hierarchical node path for each simulated IP instance. During the co-simulation compilation process, the EDA (Electronic Design Automation) tool may perform case conversion on the node names in the SPICE netlist (e.g., converting uppercase node names to lowercase) and generate the skeleton file. If the node names used in the SPICE stimulus source are not completely consistent with the corresponding port node names in the skeleton file, although the EDA tool may allow the compilation process to pass normally due to its case-insensitive nature, the actual connections may point to different node instances, causing the stimulus to fail to apply to the simulated IP.

[0051] In some alternative implementations, such as Figure 3 As shown, the second verification, based on the second type of verification information, includes:

[0052] Step S131: Obtain the target port node corresponding to the target simulated IP in the node mapping information.

[0053] Specifically, the port node name of the target emulated IP instance is extracted from the skeleton file. For example, the port node record information corresponding to the target emulated IP instance in the skeleton file can be found by executing the command "grep module_instance_name run / simv.daidir / sklt.ntl" in the terminal.

[0054] Step S132: Match the corresponding excitation node of the simulated excitation with the target port node.

[0055] Specifically, the names of the stimulus nodes of the simulated stimulus source in the SPICE top-level file are compared one by one with the names of the target port nodes extracted from the skeleton file.

[0056] Step S133: Determine whether the consistency condition is met between the simulated stimulus corresponding to the stimulus node and the target port node based on the matching result.

[0057] The consistency conditions include: the node names of the simulated stimulus corresponding to the stimulus node and the target port node are consistent; and the hierarchical paths of the simulated stimulus corresponding to the stimulus node and the target port node are consistent. Consistent node names mean that the stimulus node name and the target port node name are the same, including matching capitalization. Consistent hierarchical paths mean that the hierarchical path corresponding to the stimulus node and the hierarchical path corresponding to the target port node are consistent. If any stimulus node name and the corresponding target port node name are inconsistent in either node name or hierarchical path, the second verification fails, indicating that the stimulus source may be connected to an independent node outside the skeleton file and not actually connected to the target port node of the target simulated IP. For example, if the target port node recorded in the skeleton file is named "tb.module_instance_name.vdd", and the corresponding SPICE stimulus source is "VVDD tb.module_instance_name.vdd 0 DC 3.3", then the node name and hierarchical path are consistent. If the corresponding SPICE stimulus source is "VVDDtb.module_instance_name.VDD 0 DC 3.3", the node name is inconsistent due to the case difference. If the corresponding SPICE stimulus source is "VVDD vdd 0 DC 3.3", the hierarchical path is inconsistent because the corresponding hierarchical path is missing. When the node name or hierarchical path does not meet the consistency condition, the second verification fails.

[0058] In some optional implementations, when the first verification passes, it indicates that the simulated netlist corresponding to the target simulated IP has been loaded and expanded by the simulator; when the second verification passes, it indicates that the stimulus node of the simulated stimulus and the target port node of the target simulated IP meet the condition of consistent node name and hierarchical path. Optionally, if both the first and second verifications pass, it is determined that a connectivity relationship has been established between the simulated stimulus and the target simulated IP. If either the first or second verification fails, it is determined that a valid connectivity relationship has not been established between the simulated stimulus and the target simulated IP.

[0059] In some optional implementations, the first and second verifications are performed sequentially according to a predetermined order. Specifically, the first verification is performed first, followed by the second verification. If the first verification fails, it indicates that the simulated netlist corresponding to the target simulated IP has not been loaded and expanded by the simulator. In this case, the execution of the second verification is terminated, and the fault location information corresponding to the first verification is output. If the first verification passes, the second verification continues. If the second verification fails, it indicates that the consistency condition between the node corresponding to the simulated stimulus and the target port node of the target simulated IP is not met, and the fault location information corresponding to the second verification is output. Among them, the fault location information corresponding to the first verification includes information indicating that "the simulated netlist of the target simulated IP has not been expanded by the simulator"; the fault location information corresponding to the second verification includes information indicating that "the node name or hierarchical path between the stimulus node of the simulated stimulus and the target port node of the target simulated IP is inconsistent, and the simulated stimulus may be connected to an independent node outside the skeleton". Through the above verification sequence, the abnormality can be located according to different verification results, improving the efficiency of problem investigation.

[0060] In one embodiment of this application, the verification information further includes compilation verification information, which includes compilation logs generated by the co-simulation compiler during the compilation phase. The compilation logs are text log files automatically generated during the co-simulation compilation process between the digital simulator and the analog simulator, used to record configuration parsing, module mapping, and error or warning information during the compilation process. For example, in the VCS tool, the compilation log can be comp.log; in the Xcelium tool, the compilation log can be xrun.log. In some optional implementations, verifying whether the mixed-signal simulation configuration is correctly recognized by the compiler based on the compilation verification information includes: First, verifying whether the mixed-signal configuration instructions in the compilation log are correctly parsed. During mixed-signal simulation, the instructions configured in the mixed-signal configuration file need to be recognized by the co-simulation compiler to establish a co-simulation relationship between the digital and analog sides. For example, it can be determined whether the relevant configuration instructions are correctly parsed by checking whether the module mapping information corresponding to use_spice -cell appears in the compilation log. Second, verifying whether there are error-level errors in the compilation log. Optionally, it can be determined whether there are problems in the current compilation process that prevent subsequent verification from continuing by checking the error information in the compilation log. If the mixed-signal configuration instructions are not parsed correctly, or if there are error-level errors in the compilation log, the mixed-signal simulation configuration verification is considered failed. In this case, the verification process should be terminated, and the user should be prompted to check the compilation configuration. If the mixed-signal configuration instructions are parsed correctly and there are no error-level errors, the mixed-signal simulation configuration verification is considered successful. Through the above compilation verification process, it can be confirmed that the mixed-signal simulation configuration has been correctly recognized by the compiler before subsequent verification of the simulation excitation connectivity.

[0061] In one embodiment of this application, the verification information further includes port mapping information, which is used to verify whether a corresponding mapping relationship is established between digital-side module ports and analog-side sub-circuit ports. The port mapping information includes a port mapping report generated by the co-simulation compiler during the compilation phase. The port mapping report records the mapping method and mapping status between digital-side module ports and analog-side sub-circuit ports. For example, in the VCS tool environment, the port mapping report can be a port.rpt file generated in the simv.daidir directory. In some optional implementations, verifying whether a corresponding mapping relationship is established between digital-side module ports and analog-side sub-circuit ports based on the port mapping information includes: First, verifying whether a port name-based corresponding mapping relationship is established between digital-side module ports and analog-side sub-circuit ports in the port mapping report. For example, the port mapping report may display: use_spice-cell module_name port_map(*=>snps_by_name), where snps_by_name indicates mapping according to port name. Second, verifying whether all declared ports in the port mapping report have been mapped and whether there are any unmapped port markers. Optionally, the port mapping report can be checked for unmapped or not found markers to determine if all ports have been mapped. If no corresponding mapping relationship is established between digital module ports and analog sub-circuit ports, or if unmapped port markers exist, the port mapping verification fails. This failure indicates a potential port name mismatch, leading to incorrect signal connections. When a corresponding mapping relationship is established between digital module ports and analog sub-circuit ports, and all declared ports are mapped, the port mapping verification passes. This port mapping verification further confirms the interface correspondence between the digital module and the analog sub-circuit.

[0062] In one embodiment of this application, the verification information further includes interface element information, which is used to verify whether the configured D2A and A2D interfaces are identified as mixed-signal interface elements. The interface element information includes an interface element report generated by the co-simulation compiler during the compilation phase. The interface element report records information such as the port name, direction, and drive type of the interface elements identified as mixed-signal interface elements. For example, in the VCS tool environment, the interface element report can be the interface_element.rpt file generated in the simv.daidir directory. In some optional implementations, verifying whether the configured D2A and A2D interfaces are identified as mixed-signal interface elements based on the interface element information includes: first, obtaining the D2A and A2D interfaces configured in the mixed-signal configuration file; second, obtaining the interface elements in the interface element list corresponding to the interface element report; and then determining whether both the D2A and A2D interfaces exist in the interface element list. When the interface element list contains interface elements corresponding to the D2A and A2D interfaces, it is further determined whether the interface direction of the corresponding interface element is consistent with the configured direction in the mixed-signal configuration file. The interface element verification is successful when the interface element list contains corresponding interface elements for both D2A and A2D interfaces, and the interface direction of the corresponding interface element matches the configuration direction in the mixed-signal configuration file. If a configured D2A or A2D interface does not exist in the interface element list, it means that the interface has not been recognized as a mixed-signal interface element. For example, if a D2A interface is configured in the mixed-signal configuration file, but the corresponding element does not exist in the interface element report, it may be due to reasons such as a mismatch between the port name and the SPICE netlist, the port path pointing to an internal connection instead of a module port, or the D2A / A2D interface being optimized away by the optimizer.

[0063] In one embodiment of this application, the verification information further includes simulation output information, which is used to verify whether the output signal of the target analog IP has undergone a valid change. The simulation output information includes simulation output log information and / or waveform information generated during the mixed-signal simulation. The simulation output log information is a text log file generated during the operation of the digital simulator, used to record signal value changes and time information during the simulation. For example, in the VCS tool, the simulation output log can be sim.log. The waveform information can be in formats such as FSDB (FastSignal Database) or VCD (Value Change Dump). In some optional embodiments, verifying whether the output signal of the target analog IP has undergone a valid change based on the simulation output information includes: first, obtaining the change information of the corresponding output signal of the target analog IP from the simulation output log information and / or the waveform information. Specifically, the state of the output signal of the target analog IP (such as the EOC conversion end signal of an ADC) at each simulation time point can be extracted from the simulation output log, or the waveform changes of the output signal can be viewed using a waveform tool. Secondly, based on the output signal change information, determine whether the target simulation IP output signal has undergone a valid change. Specifically, verify whether the target simulation IP output signal has a valid flip or a non-zero change within the simulation time range. For example, in a 10-bit SAR ADC hybrid simulation embodiment, the ADC output signal, such as the change of EOC (End Of Conversion), can be checked. The simulation output log can be checked using the following method: `grep -i "eoc\|b\[" run / sim.log | tail -20`. When the target simulation IP output signal undergoes a valid change within the simulation time range (e.g., a signal flip occurs, and it does not always remain in the initial default state, such as all 0s or all Xs), the simulation output verification is considered successful. If the target simulation IP output signal remains unchanged, it indicates that the target simulation IP may not have been solved effectively, which may involve problems such as the simulation netlist not being expanded, the simulation stimulus not being connected, or the interface not being established.

[0064] In some optional implementations, the above verification process can be automated using a verification script. Specifically, the verification script acquires verification information generated during the mixed-signal simulation. This verification information may include compilation logs, simulation logs, node mapping information, port mapping reports, interface element reports, and simulation output information. Subsequently, according to preset verification rules, the verification script automatically performs a first verification, a second verification, and verifications based on at least one of the following: compilation verification information, port mapping information, interface element information, and simulation output information. During execution, the verification script can read the corresponding log files and report files and automatically perform information comparisons based on preset criteria. For example: checking for error-level errors in the compilation log; checking for sub-circuit expansion information in the simulation log; checking for node mapping relationships; checking for port mapping status; checking for interface element lists; and checking for output signal changes. After completing the above verifications, the corresponding verification results are output. The automated script can read specific information from each log file and report file by executing Linux text search commands (such as the grep command) or more complex text parsing programs (such as Python scripts) in the terminal, automatically compare it with preset criteria, and generate a verification report. The verification report can include the pass / fail status of each verification dimension, the reason for failure, and fault location information. Automating the process via scripts reduces the need for manual review of log and report files, thus increasing the automation level of the verification process.

[0065] In some optional implementations, the timing of the first and second verifications can be adjusted according to the mixed-signal simulation process. Optionally, the first and second verifications can be performed before the mixed-signal simulation. Specifically, after the mixed-signal simulation compilation and related information generation are completed, the first and second types of verification information are obtained, and the first and second verifications are performed. For example, simulation log information is used to perform the first verification; node mapping information is used to perform the second verification. By performing verification before the simulation officially runs, problems such as incomplete simulation netlist expansion or abnormal excitation node correspondence can be identified in advance. Optionally, the first and second verifications can also be performed uniformly based on the verification information after the mixed-signal simulation is completed. Specifically, after the simulation runs, the verification information generated during the mixed-signal simulation is obtained, and the corresponding verifications are performed uniformly. By adjusting the timing of verification execution, a suitable verification method can be selected according to different simulation scenarios.

[0066] Compared with the prior art, the present invention has at least the following beneficial effects:

[0067] First, cross-validation is performed using a first verification and a second verification. The first verification confirms whether the simulated netlist corresponding to the target simulated IP has been loaded and expanded by the simulator. The second verification confirms whether the consistency conditions are met between the excitation nodes corresponding to the simulated excitations and the target port nodes corresponding to the target simulated IP. The connectivity status between the simulated excitations and the target simulated IP is determined from both the simulated netlist status and the excitation node correspondence. Therefore, even if the simulation waveform shows that the excitation source voltage or current value is normal, it can still identify cases where the simulated excitations are not actually connected, avoiding misjudgments of simulation results due to isolated nodes, inconsistent node names, or missing hierarchical paths.

[0068] Second, by performing verifications across multiple dimensions according to a pre-defined process, and locating the abnormal steps based on the failed verification dimensions, the efficiency of problem localization can be improved. Specifically, if the first verification fails, it can be determined that the simulated netlist expansion state is abnormal; if the second verification fails, it can be determined that there is an abnormal correspondence between the excitation node and the target port node; if the compilation verification fails, it can be determined that the mixed-signal simulation configuration identification is abnormal; if the port mapping verification fails, it can be determined that there is a mapping abnormality between the digital side module port and the analog side sub-circuit port; if the interface element verification fails, it can be determined that the D2A / A2D interface identification is abnormal; and if the simulation output verification fails, it can be determined that the target analog IP output signal has not produced a valid change.

[0069] Third, this invention does not rely on specific EDA tools. The information sources used for each verification dimension include compilation logs, simulation logs, skeleton files, port mapping reports, interface element reports, and simulation output logs or waveform files. As long as the corresponding verification information can be provided, the invention can be used for implementation. Therefore, it is applicable to different mixed-signal simulation environments.

[0070] Fourth, each verification dimension can be executed automatically through verification scripts. By reading the corresponding log files and report files and judging the verification results according to preset verification rules, the manual operation of checking logs and waveforms one by one can be reduced, thereby improving the automation level of the verification process.

[0071] Fifth, the present invention can adjust the timing of verification execution according to the specific simulation process. Some verification dimensions can be completed before the simulation is executed, thereby enabling the early detection of connectivity problems such as unexpanded simulation netlists and abnormal node correspondences, avoiding manual investigation after the simulation results are abnormal, and improving the efficiency of mixed numerical simulation verification.

[0072] To better understand the implementation scheme of the multidimensional verification method for simulating excitation connectivity in mixed-signal simulation, the following is a detailed explanation with reference to specific embodiments:

[0073] Specific Implementation Example 1: Connectivity Verification of a 10-bit SAR ADC (Successive Approximation Register Analog-to-Digital Converter) Hybrid Simulation

[0074] In this embodiment, the digital side uses a digital simulator (VCS) to compile the entire chip's RTL and a test platform. The ADC participates in co-simulation as a Verilog shell wrapper. This Verilog shell wrapper only retains the port definitions corresponding to the analog IP, used to establish the module interface for the analog IP in the digital simulation environment. On the analog side, an analog simulator (XA) solves the encrypted SPICE netlist corresponding to the ADC. The SPICE netlist contains multiple sub-circuit definitions used to describe the internal analog circuit structure of the ADC. Regarding interface configuration, the mixed-signal configuration file contains multiple D2A and A2D instructions to establish the signal interaction interface between the digital and analog domains. For excitation input, the top-level SPICE file provides multiple voltage and current sources, used to provide power domain bias and input signal excitation, respectively. In the above simulation environment, to verify whether the analog excitation is truly injected into the ADC's corresponding analog IP ports, the following verification process is executed sequentially.

[0075] (a) Compilation configuration verification

[0076] First, the compilation logs generated during the co-simulation compilation process between the digital and analog sides are checked. These compilation logs are text log files automatically generated by the co-simulation compiler during the compilation phase, used to record configuration parsing, module mapping, and error or warning information during the compilation process. For example, in the VCS tool environment, the compilation log can be `comp.log`; in the Xcelium tool environment, the compilation log can be `xrun.log`. In this embodiment, the mixed-signal configuration instructions are verified by checking the `comp.log` file. For example, the following commands can be executed: `grep -i "error"run / comp.log | head -20` and `grep -i "use_spice" run / comp.log`. Through the above checks: if there are no error-level errors in the compilation logs, and the mapping information corresponding to the `use_spice -cell` module name can be found, then the compilation configuration verification is considered successful. If error-level errors exist during the compilation process, the subsequent verification process is terminated, and the current mixed-signal simulation configuration verification is determined to have failed.

[0077] (ii) Verification by simulated netlist expansion

[0078] After completing the compilation and configuration verification, the simulation log generated by the simulator is checked. The simulation log is a log file automatically generated during the simulator's startup phase, used to record netlist parsing, sub-circuit unpacking, device and node statistics, and connectivity building information. For example, in the XA tool, the simulation log can be xa.log; in the CustomSim tool, it can be cs.log; and in the HSPICE tool, it can be a .lis file. In this embodiment, by checking the xa.log file, it is determined whether the SPICE netlist of the analog IP corresponding to the ADC has been truly unpacked by the simulator. For example, the following commands can be executed: `grep -i "building connectivity" run / xa.log` and `grep -i "subcktdefined" run / xa.log`. If the log shows: "Building connectivity for subckt module name" and "Subckt Defined / Used: total number of modules / total number of modules", it indicates that the sub-circuit of the analog IP corresponding to the ADC has been unpacked and connectivity building information has been formed. For example, when the ADC simulation IP contains 342 sub-circuit definitions, the simulation log may display: Subckt Defined / Used: 342 / 342. In this case, the first verification is confirmed to have passed. Conversely, if the element statistics in xa.log only contain a small amount of external stimulus information such as voltage and current sources, and do not reflect the corresponding sub-circuit and node information of the ADC's internal simulation circuit, it indicates that the ADC's corresponding simulation netlist has not been expanded. In this case, the simulation stimulus may only be connected to isolated nodes, and the first verification will fail.

[0079] (III) Node Consistency Verification

[0080] After the simulated netlist expansion verification passes, node consistency verification is further performed. In this embodiment, the skeleton file automatically generated by the co-simulation compiler during the compilation phase is read first. The skeleton file records the port node definitions of the simulated IP instance in the co-simulation hierarchy and is an intermediate file generated during the mapping process between the digital-side Verilog module hierarchy and the analog-side SPICE sub-circuit ports. For example, in the VCS+XA co-simulation environment, the skeleton file can be: simv.daidir / sklt.ntl. This file records the port names corresponding to the simulated IP instances and the hierarchical node paths. In this embodiment, the target port node corresponding to the ADC simulated IP instance is obtained by reading the sklt.ntl file. For example, the simulated IP port node information can be obtained by executing: grep "module instance name" run / simv.daidir / sklt.ntl. Subsequently, the excitation nodes corresponding to the simulated excitation sources in the top-level SPICE file are matched with the target port nodes recorded in the skeleton file. For example, if the target port node in the skeleton file is tb.module_instance_name.vdd, and the SPICE stimulus source is VVDDtb.module_instance_name.vdd 0 DC 3.3, then the node names and hierarchical paths are consistent, and the node consistency verification passes. If the SPICE stimulus source is VVDD tb.module_instance_name.VDD 0 DC 3.3, due to the case difference in node names, although the EDA tool may allow the compilation process to pass due to its case-insensitive nature, it may actually point to different node instances, and the node consistency verification fails. If the SPICE stimulus source is VVDD vdd 0 DC 3.3, due to the lack of a hierarchical path corresponding to the simulated IP instance, the stimulus may connect to an independent node outside the skeleton, and the node consistency verification fails.

[0081] (iv) Port mapping verification

[0082] In this embodiment, port mapping information can be further used to verify the correspondence between digital-side module ports and analog-side sub-circuit ports. The port mapping report is a report file automatically generated by the co-simulation compiler when processing the `use_spice` instruction, used to record the mapping method and mapping status between module ports. For example, in the VCS tool environment, the port mapping report can be: `simv.daidir / port.rpt`. By reading the `port.rpt` file, it is verified whether a correct mapping relationship has been established between the digital-side shell module ports and the analog-side SPICE sub-circuit ports. For example: `cat run / simv.daidir / port.rpt`. If the port mapping report displays: `use_spice -cell module_name port_map(*=>snps_by_name)`, it indicates that the ports are mapped by name. If all declared ports exist in the mapping list and there are no `unmapped` or `not found` markers, the port mapping verification is successful. If `*=>snps_positional` appears, or there are unmapped ports, it indicates that the port names or port correspondences may be abnormal and require further investigation.

[0083] (v) Interface element verification

[0084] In this embodiment, interface element information can be further used to verify whether the configured D2A and A2D interfaces are correctly identified as mixed-signal interface elements. The interface element information includes an interface element report generated by the co-simulation compiler during the compilation phase. This report records information such as the port name, interface direction, and driver type of the interface identified as a mixed-signal interface. For example, in the VCS tool environment, the interface element report could be: simv.daidir / interface_element.rpt. In this embodiment, the D2A and A2D interfaces configured in the mixed-signal configuration file are first obtained. The D2A interface is used to convert digital signals to analog signals, and the A2D interface is used to convert analog signals to digital signals. Then, the interface element list corresponding to the interface element report is read, and it is determined whether both the D2A and A2D interfaces exist in the interface element list. For example, you can execute: cat run / simv.daidir / interface_element.rpt. If all D2A and A2D interfaces configured in the mixed-signal configuration file exist in the interface element list, then further determine whether the direction of the corresponding interface element is consistent with the configuration direction in the mixed-signal configuration file. When the corresponding D2A and A2D interfaces exist in the interface element list and the interface direction is consistent with the configuration direction, it is determined that the interface element verification is successful. If a configured D2A or A2D interface does not appear in the interface element list, it means that the interface has not been recognized as a valid mixed-signal interface element. For example, if the configuration file is configured as: d2a port=clk, but there is no corresponding interface element in the interface element report, the interface may not be established due to the following reasons: (1) the port name does not match the SPICE netlist; (2) the port path points to the internal connection instead of the module port; (3) the D2A / A2D interface is optimized away by the optimizer. At this time, it is determined that the interface element verification is unsuccessful.

[0085] (vi) Verification of the validity of simulation output

[0086] In this embodiment, simulation output information can be further used to verify whether the output signal of the target analog IP has undergone a valid change. The simulation output information includes simulation output log information and / or waveform information generated during the mixed-signal simulation. The simulation output log information is a text log file automatically generated during the operation of the digital simulator, used to record signal value changes and corresponding time information during the simulation. For example, in the VCS tool, the simulation output log can be sim.log. The waveform information can be stored in formats such as FSDB (Fast Signal Database) or VCD (Value Change Dump). In this embodiment, by reading the simulation output log information or waveform information, the change information of the corresponding output signal of the target analog IP is obtained, and the validity of the target analog IP output signal is determined based on the output signal change information. For example, for an ADC (Analog-to-Digital Converter) analog IP, the change of its conversion end signal EOC (EndOf Conversion) can be detected. In this embodiment, the command `grep -i "eoc\|b\[" run / sim.log | tail -20` can be executed to check the target output signal change information in the simulation output log. When the target simulated IP output signal undergoes a valid change within the simulation time range, the simulation output verification is considered successful. If the target simulated IP output signal remains unchanged, for example, always 0 or always X, it indicates that the simulated IP may not have been truly solved, and there may be problems such as the simulated netlist not being expanded, stimuli not being injected, or interfaces not being connected.

[0087] All six dimensions have been verified, indicating that the simulated stimulus has been truly injected into the ADC port.

[0088] In some optional implementations, multiple verification dimensions can be executed in a preset order. For example: (1) First dimension: compilation log verification; (2) Second dimension: simulated netlist expansion verification; (3) Third dimension: node consistency verification; (4) Fourth dimension: port mapping verification; (5) Fifth dimension: interface element verification; (6) Sixth dimension: simulation output validity verification. When a certain verification dimension fails, the abnormality can be located based on the corresponding verification result. For example: when compilation verification fails, it indicates that there may be a mixed signal configuration problem; when simulated netlist expansion verification fails, it indicates that the simulated IP netlist has not been expanded and the simulated stimulus may be connected to an isolated node; when node consistency verification fails, it indicates that the simulated stimulus node does not match the target simulated IP port node; when port mapping verification fails, it indicates that there may be a mapping abnormality between the digital side module port and the simulated side sub-circuit port; when interface element verification fails, it indicates that the D2A / A2D interface may not be correctly identified or established. Through the above multi-dimensional verification process, misjudgment caused by judging the state of simulated stimulus based on only a single simulation waveform can be avoided.

[0089] In some optional implementations, the timing of the verification process can be adjusted according to the specific simulation flow. Some verification dimensions can be completed before the formal execution of the mixed-signal simulation. For example, the information used for compilation verification, simulated netlist expansion verification, node consistency verification, port mapping verification, and interface element verification can be obtained after compilation, and the corresponding verifications can be performed. For simulation output validity verification, which relies on output logs or waveform information generated during simulation execution, it can be performed after the simulation is completed. Optionally, all verification information can be obtained at once after the simulation is completed, and multiple verification dimensions can be executed uniformly.

[0090] In some optional implementations, the information source for each verification dimension is not limited to a fixed file name generated by a specific tool. Any file or report that can provide the corresponding verification information can be used to implement the above verification method. For example, the compilation log is not limited to comp.log generated by the VCS tool, but can also be xrun.log generated by the Xcelium tool; the simulation log is not limited to xa.log generated by the XA tool, but can also be cs.log generated by the CustomSim tool or a .lis file generated by the HSPICE tool. The method of this application does not depend on a specific simulation tool, but realizes the verification of the simulated excitation connectivity state based on the verification information generated during the mixed-signal simulation process.

[0091] In some alternative implementations, the number of verification dimensions can be adjusted according to the specific mixed-signal simulation scenario. For example, in complex simulation scenarios, new verification dimensions can be added, such as power supply current and power consumption verification; in simple simulation scenarios, some verification dimensions can be reduced, such as skipping interface element verification. By adjusting the verification dimensions, the connectivity verification requirements in different types of mixed-signal simulation scenarios can be adapted.

[0092] like Figure 4 The diagram illustrates the structure of a multidimensional verification system 400 for simulating excitation connectivity in a mixed-signal simulation according to an embodiment of the present invention. The multidimensional verification system 400 for simulating excitation connectivity in a mixed-signal simulation in this embodiment includes: an information acquisition module 401, a first verification module 402, a second verification module 403, and a result determination module 404.

[0093] The information acquisition module 401 is used to acquire the verification information generated during the mixed-signal simulation process. The verification information includes a first type of verification information and a second type of verification information.

[0094] The first verification module 402 is used to perform a first verification based on the first type of verification information to determine whether the simulated netlist corresponding to the target simulated IP has been loaded and expanded by the simulation simulator.

[0095] The second verification module 403 is used to perform a second verification based on the second type of verification information to determine whether the consistency condition is met between the incentive node corresponding to the simulated incentive and the target port node corresponding to the target simulated IP.

[0096] The result determination module 404 is used to determine the connectivity status between the simulated stimulus and the target simulated IP based on the execution results of the first verification and the second verification.

[0097] It should be noted that the implementation principle and process of the multidimensional verification system for simulating excitation connectivity in mixed-signal simulation provided in this embodiment of the invention are similar to the multidimensional verification method for simulating excitation connectivity in mixed-signal simulation described above, and will not be repeated here. The specific process of each module performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0098] It should also be understood that the module division in the embodiments of the present invention is illustrative and only represents one logical functional division; in actual implementation, there may be other division methods. Furthermore, the functional modules in the various embodiments of the present invention can be integrated into a single processor, exist as separate physical entities, or two or more modules can be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0099] like Figure 5 The diagram shown is a schematic of an electronic terminal provided in an embodiment of this application. The electronic terminal includes at least one processor 501, a memory 502, at least one network interface 503, and a user interface 505. The various components in the device are coupled together via a bus system 504. It is understood that the bus system 504 is used to implement communication between these components. In addition to a data bus, the bus system 504 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 5 The general will label all buses as bus systems.

[0100] The user interface 505 may include a monitor, keyboard, mouse, trackball, clicker, button, touchpad, or touch screen.

[0101] It is understood that memory 502 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM) or programmable read-only memory (PROM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM) and synchronous static random access memory (SSRAM). The memories described in the embodiments of this invention are intended to include, but are not limited to, these and any other suitable categories of memory.

[0102] In this embodiment of the invention, the memory 502 is used to store various types of data to support the operation of the electronic terminal 500. Examples of this data include: any executable program for operation on the electronic terminal 500, such as the operating system 5021 and application programs 5022; the operating system 5021 contains various system programs, such as the framework layer, core library layer, driver layer, etc., for implementing various basic services and handling hardware-based tasks. The application program 5022 may contain various applications, such as a media player, browser, etc., for implementing various application services. The methods provided in this embodiment of the invention can be included in the application program 5022.

[0103] The methods disclosed in the above embodiments of the present invention can be applied to processor 501, or implemented by processor 501. Processor 501 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in processor 501 or by instructions in the form of software. The processor 501 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Processor 501 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. General-purpose processor 501 may be a microprocessor or any conventional processor, etc. The steps of the accessory optimization method provided in the embodiments of the present invention can be directly reflected as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, which is located in a memory. The processor reads the information in the memory and combines it with its hardware to complete the steps of the aforementioned method.

[0104] In an exemplary embodiment, the electronic terminal 500 may be used to execute the aforementioned method by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), or complex programmable logic devices (CPLDs).

[0105] According to the method provided in the embodiments of the present invention, the present invention also provides a computer program product, the computer program product comprising: computer program code, which, when the computer program code is run on a computer, causes the computer to execute a multidimensional verification method for simulating excitation connectivity in mixed-signal simulation of any of the embodiments shown.

[0106] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute a multidimensional verification method for simulating excitation connectivity in mixed-signal simulation of any of the embodiments shown.

[0107] As used in this specification, the terms "component," "module," "system," etc., are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process and / or an execution thread, and components may be located on a single computer and / or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable media on which various data structures are stored. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).

[0108] Those skilled in the art will recognize that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0109] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0110] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0111] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0112] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0113] In the above embodiments, the functions of each functional unit can be implemented entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. A computer program product includes one or more computer instructions (programs). When the computer program instructions (programs) are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. Computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs, DVDs), or semiconductor media (e.g., solid-state disks, SSDs, etc.).

[0114] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0115] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0116] In summary, the multi-dimensional verification method, system, medium, and terminal for simulated excitation connectivity in mixed-signal simulation provided by this invention acquires verification information generated during the mixed-signal simulation process, including a first type of verification information and a second type of verification information. Based on the first type of verification information, a first verification is performed to determine whether the simulated netlist corresponding to the target simulated IP is loaded and expanded by the simulator. Based on the second type of verification information, a second verification is performed to determine whether the consistency condition is met between the excitation node corresponding to the simulated excitation and the target port node corresponding to the target simulated IP. Based on the execution results of the first and second verifications, the connectivity state between the simulated excitation and the target simulated IP is determined. Through this method, this application can verify the connectivity state of the simulated excitation from two aspects: the simulated netlist state and the correspondence between excitation nodes. This solves the technical problem in existing mixed-signal simulation processes where simulated excitations may be connected to non-target nodes or not actually applied to the simulated IP port, leading to inconsistencies between the simulated waveform and the actual excitation connectivity state, and the lack of an effective connectivity verification mechanism.

[0117] Therefore, this application effectively overcomes the various shortcomings of the prior art and has high industrial application value.

[0118] The above embodiments are merely illustrative of the principles and effects of this application and are not intended to limit this application. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of this application. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in this application should still be covered by the claims of this application.

Claims

1. A multidimensional verification method for simulating excitation connectivity in mixed-signal simulation, characterized in that, include: Acquire verification information generated during the mixed-signal simulation process, the verification information including a first type of verification information and a second type of verification information; Based on the first type of verification information, perform the first verification to determine whether the simulated netlist corresponding to the target simulated IP has been loaded and expanded by the simulation simulator. Based on the second type of verification information, perform a second verification to determine whether the consistency condition is met between the incentive node corresponding to the simulated incentive and the target port node corresponding to the target simulated IP. Based on the execution results of the first verification and the second verification, the connectivity status between the simulated stimulus and the target simulated IP is determined.

2. The multidimensional verification method for simulated excitation connectivity in mixed-signal simulation according to claim 1, characterized in that, The first type of verification information includes simulation log information generated by the simulator; performing the first verification based on the first type of verification information includes: Obtain the sub-circuit connectivity construction information, the number of sub-circuit definitions, and the number of sub-circuit usages corresponding to the target simulation IP from the simulation log information; Based on the sub-circuit connectivity construction information, the number of sub-circuit definitions, and the number of sub-circuit usages, determine whether the simulation netlist corresponding to the target simulation IP is loaded and expanded by the simulation simulator. When the simulation log information contains sub-circuit connectivity construction information corresponding to the target simulation IP, and the number of sub-circuit definitions matches the number of sub-circuits used, the first verification is determined to be successful.

3. The multidimensional verification method for simulated excitation connectivity in mixed-signal simulation according to claim 1 or 2, characterized in that, The second type of verification information includes node mapping information generated by the co-simulation compilation process; Based on the second type of verification information, performing the second verification includes: Obtain the target port node corresponding to the target simulated IP in the node mapping information; Match the simulated stimulus nodes with the target port nodes to establish a correspondence. Based on the matching results, determine whether the consistency condition is met between the simulated stimulus corresponding to the stimulus node and the target port node. The consistency conditions include that the node names of the simulated stimulus corresponding to the stimulus node and the target port node are consistent, as well as that the hierarchical paths are consistent.

4. The multidimensional verification method for simulated excitation connectivity in mixed-signal simulation according to claim 1, characterized in that, The verification information also includes compilation verification information, which is used to verify whether the mixed-signal simulation configuration is correctly recognized by the compiler; the compilation verification information includes compilation logs generated by the co-simulation compiler during the compilation phase. Verifying whether the mixed-signal simulation configuration is correctly recognized by the compiler based on the compilation verification information includes: Verify that the mixed-signal configuration instructions in the compilation log are correctly parsed; Verify that there are error-level errors in the compilation log; If the mixed-signal configuration instruction is not parsed correctly, or if an error-level error exists, the verification of the mixed-signal simulation configuration is determined to have failed.

5. The multidimensional verification method for simulated excitation connectivity in mixed-signal simulation according to claim 1, characterized in that, The verification information also includes port mapping information, which is used to verify whether a corresponding mapping relationship is established between digital-side module ports and analog-side sub-circuit ports; the port mapping information includes a port mapping report generated by the co-simulation compiler during the compilation phase. Verifying whether a corresponding mapping relationship is established between the digital-side module port and the analog-side sub-circuit port based on the port mapping information includes: Verify whether a port name-based mapping relationship is established between the digital-side module ports and the analog-side sub-circuit ports in the port mapping report; Verify that all declared ports in the port mapping report have been mapped and that there are no unmapped ports marked. When no corresponding mapping relationship is established between the digital side module port and the analog side sub-circuit port, or when there is an unmapped port marker, it is determined that the mapping relationship verification has failed.

6. The multidimensional verification method for simulated excitation connectivity in mixed-signal simulation according to claim 1, characterized in that, The verification information also includes interface element information, which is used to verify whether the configured D2A interface and A2D interface are identified as mixed-signal interface elements; the interface element information includes the interface element report generated by the co-simulation compiler during the compilation phase; Verifying whether the configured D2A and A2D interfaces are identified as mixed-signal interface elements based on the interface element information includes: Obtain the D2A and A2D interfaces configured in the mixed-signal configuration file; Retrieve the interface element from the corresponding interface element list of the interface element report; Determine whether both the D2A interface and the A2D interface exist in the interface element list; When the interface element list contains interface elements corresponding to the D2A interface and the A2D interface, and the interface direction corresponding to the interface element is consistent with the configuration direction in the mixed signal configuration file, the interface element verification is determined to be successful.

7. The multidimensional verification method for simulated excitation connectivity in mixed-signal simulation according to claim 1, characterized in that, The verification information also includes simulation output information, which is used to verify whether the target analog IP output signal has undergone a valid change; the simulation output information includes simulation output log information and / or waveform information generated during the mixed-signal simulation process. Verifying whether the target analog IP output signal has undergone a valid change based on the simulation output information includes: Obtain the change information of the output signal corresponding to the target simulated IP from the simulation output log information and / or the waveform information; Determine whether the target analog IP output signal has undergone a valid change based on the change information of the output signal; When the target simulated IP output signal undergoes a valid change within the simulation time range, the simulation output verification is deemed successful.

8. A multidimensional verification system for simulating excitation connectivity in mixed-signal simulation, characterized in that, include: The information acquisition module is used to acquire the verification information generated during the mixed-signal simulation process, the verification information including a first type of verification information and a second type of verification information. The first verification module is used to perform a first verification based on the first type of verification information to determine whether the simulated netlist corresponding to the target simulated IP has been loaded and expanded by the simulation simulator. The second verification module is used to perform a second verification based on the second type of verification information to determine whether the consistency condition is met between the incentive node corresponding to the simulated incentive and the target port node corresponding to the target simulated IP. The result determination module is used to determine the connectivity status between the simulated stimulus and the target simulated IP based on the execution results of the first verification and the second verification.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the multidimensional verification method for simulating excitation connectivity in mixed-signal simulation as described in any one of claims 1 to 7.

10. An electronic terminal, comprising a memory, a processor, and a computer program stored in the memory, characterized in that, The processor executes the computer program to implement the multidimensional verification method for simulating excitation connectivity in mixed-signal simulation as described in any one of claims 1 to 7.