Security design method of chip, electronic equipment and storage medium
By performing error simulation and iterative modification of circuit design codes in the chip design stage, the problem of low chip safety verification efficiency in the existing technology is solved, and fast and efficient safety testing and design optimization are achieved.
Patent Information
- Application Number
- CN202411002280.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-24
- Publication Date
- 2024-11-12
AI Technical Summary
The existing chip security verification method is based on ready-made chip testing completed, resulting in long test time and low efficiency, and the design needs to be adjusted repeatedly to meet predetermined indicators.
By obtaining the circuit design code, analyzing and generating the circuit netlist, determining the register list, extracting the error injection point, performing error simulation, judging diagnostic coverage, and iterating the circuit design code until it meets the functional safety design conditions.
It improves chip testing efficiency, ensures the safety of the chip and meets functional safety design conditions.
Smart Images

Figure CN118940687A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of chip design, and in particular to a chip security design method, electronic device and storage medium. Background Art
[0002] A chip, also known as an integrated circuit (IC), is an electronic device that integrates multiple electronic components (such as transistors, resistors, capacitors, etc.) on a tiny piece of semiconductor material (usually a silicon wafer). The design and manufacture of chips represent the core of modern electronic technology. Chips usually play a vital role in electronic devices. For example, the main control chip of a laser radar is the core component of the laser radar and is responsible for the information collection, processing and transmission of the laser radar.
[0003] At present, chip safety verification usually tests the implementation of safety mechanisms through fault injection and evaluates the diagnostic coverage of chip safety mechanisms, so as to determine whether the chip meets the functional safety level assessment and generate a chip functional safety assessment report.
[0004] In the process of implementing this application, the inventors found that there are at least the following problems in the prior art: the existing safety verification method is to test ready-made chips after production, and to generate a chip functional safety assessment report by judging whether the ready-made chips meet the predetermined indicators. However, this method requires adjusting the chip design and performing repeated tests after the test results do not meet the predetermined indicators, resulting in long testing time and low testing efficiency. Summary of the invention
[0005] The embodiments of the present application provide a chip security design method, an electronic device, and a storage medium, which can improve the chip testing efficiency and ensure the chip security.
[0006] The embodiments of the present application provide the following technical solutions:
[0007] In a first aspect, an embodiment of the present application provides a chip security design method, the chip includes multiple modules, and the method includes:
[0008] Obtaining a first circuit design code, and parsing the first circuit design code to generate a circuit netlist;
[0009] According to the circuit netlist, determine the register list;
[0010] Extract the error injection points of each module according to the register list to generate an error injection point list;
[0011] According to the list of error injection points, the chip is error simulated to determine the chip's diagnostic coverage;
[0012] If the diagnostic coverage of the chip does not meet the functional safety design conditions, the first circuit design code is modified to obtain the second circuit design code, and the error simulation is repeated until the diagnostic coverage of the chip meets the functional safety design conditions.
[0013] In some embodiments,
[0014] According to the register list, extract the error injection points of each module to generate an error injection point list, including:
[0015] Extract all error injection points of each module in the register list;
[0016] Alternatively, a plurality of error injection points of each module in the register list are extracted according to a preset extraction ratio.
[0017] In some embodiments,
[0018] According to the register list, extract the error injection points of each module to generate an error injection point list, including:
[0019] Get the security level of each module;
[0020] According to the security level of each module, determine the extraction ratio of each module, wherein each security level corresponds to an extraction ratio;
[0021] According to the extraction ratio of each module, a number of error injection points of each module in the register list are extracted to generate an error injection point list.
[0022] In some embodiments,
[0023] Determine the diagnostic coverage of the chip, including:
[0024] Determine the diagnostic coverage of each module of the chip;
[0025] According to the diagnostic coverage of each module, the diagnostic coverage of the chip is calculated.
[0026] In some embodiments,
[0027] Determine the diagnostic coverage of each module of the chip, including:
[0028] In the circuit function simulation environment, error behavior is injected into the error injection point of each module to determine the error detection status of each error injection point in each module;
[0029] Based on the error detection of each error injection point, the diagnostic coverage of each module is determined.
[0030] In some embodiments,
[0031] Perform error behavior injection on the error injection point of each module to determine the error detection status of each error injection point in each module, including:
[0032] Get the signal corresponding to the error flag bit of each error injection point;
[0033] According to the signal corresponding to the error flag bit corresponding to each error injection point, the error detection status of each error injection point is determined.
[0034] In some embodiments,
[0035] According to the signal corresponding to the error flag bit corresponding to each error injection point, the error detection condition of each error injection point is determined, including:
[0036] If the signal corresponding to the error flag bit is a valid signal, then the error detection condition of the error injection point is determined to be detected;
[0037] If the signal corresponding to the error flag bit is an invalid signal, it is determined that the error detection status of the error injection point is not detected.
[0038] In some embodiments, the method further comprises:
[0039] Determine the error type corresponding to each error injection point;
[0040] According to the error type corresponding to each error injection point, the error behavior of each error injection point is simulated;
[0041] Determine the error detection of each fault injection point in each module, including:
[0042] Determine the error detection status corresponding to the error type of each error injection point according to the signal corresponding to the error flag bit corresponding to each error injection point;
[0043] The error type corresponding to each error injection point includes a fixed error and / or a transient error.
[0044] In some embodiments, modifying the first circuit design code to obtain the second circuit design code specifically includes:
[0045] Obtaining a test mode of the chip, wherein the test mode of the chip includes a first test mode, a second test mode, or a third test mode;
[0046] If the test mode of the chip is the first test mode, modifying the first circuit design code to add a running program for testing to generate a second circuit design code;
[0047] If the test mode of the chip is the second test mode, modifying the first circuit design code to add stimulus data for testing to generate a second circuit design code;
[0048] If the test mode of the chip is the third test mode, the first circuit design code is modified to increase the inspection data used for the test and / or the number of test stimuli is increased to generate the second circuit design code.
[0049] In some embodiments,
[0050] The diagnostic coverage of the chip includes fixed failure coverage and transient failure coverage, and the functional safety design conditions include the first coverage threshold and the second coverage threshold;
[0051] The method also includes:
[0052] Determine whether the chip's diagnostic coverage meets the functional safety design requirements, including:
[0053] Determine whether the fixed failure coverage of the chip is greater than or equal to a first coverage threshold, and whether the transient failure coverage is greater than or equal to a second coverage threshold;
[0054] If the fixed failure coverage of the chip is greater than or equal to the first coverage threshold, and the transient failure coverage is greater than or equal to the second coverage threshold, it is determined that the diagnostic coverage of the chip meets the functional safety design conditions;
[0055] If the fixed failure coverage of the chip is less than the first coverage threshold, or the transient failure coverage is less than the second coverage threshold, it is determined that the diagnostic coverage of the chip does not meet the functional safety design conditions.
[0056] In a second aspect, an embodiment of the present application provides an electronic device, including:
[0057] A processor and a memory, the processor is used to execute the executable program code in the memory, and when the executable program code is executed, the processor executes the instructions of the chip security design method as described in the first aspect.
[0058] In a third aspect, an embodiment of the present application provides a non-volatile computer-readable storage medium, which stores a computer program. When the computer program is executed, the chip security design method of the first aspect is implemented.
[0059] The beneficial effect of the embodiments of the present application is: different from the prior art, the embodiments of the present application provide a chip security design method, the chip includes multiple modules, and the chip security design method includes: obtaining a first circuit design code, and parsing the first circuit design code to generate a circuit netlist; according to the circuit netlist, determining a register list; according to the register list, extracting the error injection points of each module to generate an error injection point list; according to the error injection point list, performing error simulation on the chip to determine the diagnostic coverage of the chip; if the diagnostic coverage of the chip does not meet the functional safety design conditions, modifying the first circuit design code to obtain a second circuit design code, and repeating the error simulation until the diagnostic coverage of the chip meets the functional safety design conditions.
[0060] Error simulation is used to determine whether the chip's diagnostic coverage meets the functional safety design conditions. If not, the circuit design code is iteratively modified until the chip's diagnostic coverage meets the functional safety design conditions. This application can improve the chip's testing efficiency and ensure the chip's safety. BRIEF DESCRIPTION OF THE DRAWINGS
[0061] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.
[0062] Figure 1 is a schematic diagram of an application environment provided by an embodiment of the present application;
[0063] Figure 2 It is a flowchart of a chip security design method provided in an embodiment of the present application;
[0064] Figure 3 yes Figure 2 A detailed flow chart of step S203 in FIG.
[0065] Figure 4 yes Figure 2 A detailed flow chart of step S204 in FIG.
[0066] Figure 5 yes Figure 4 A detailed flow chart of step S241 in FIG.
[0067] Figure 6 yes Figure 5 A detailed flow chart of step S2411 in FIG.
[0068] Figure 7 yes Figure 2 A detailed flow chart of step S205 in FIG.
[0069] Figure 8 yes Figure 2 A detailed flowchart of step S206 in FIG.
[0070] Fig. 9 This is a schematic diagram of the overall process of a chip security design method provided by an embodiment of the present application;
[0071] Fig.10 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application.
[0072] Description of Figure Numbers:
[0073]
[0074] DETAILED DESCRIPTION
[0075] In order to make the purpose, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application.
[0076] It should be noted that, if there is no conflict, the various features in the embodiments of the present application can be combined with each other, all within the scope of protection of the present application. In addition, although the functional module division is performed in the device schematic diagram and the logical order is shown in the flow chart, in some cases, the steps shown or described can be performed in a sequence different from the module division in the device or the flow chart. Furthermore, the words "first", "second", "third", etc. used in this application do not limit the data and execution order, but only distinguish the same items or similar items with basically the same functions and effects.
[0077] The technical solution of this application is described in detail below with reference to the accompanying drawings:
[0078] See also Figure 1 , Figure 1 It is a schematic diagram of an application environment provided by an embodiment of the present application.
[0079] like Figure 1As shown, the application environment 100 includes: architecture design tool 101, RTL code 102, logic synthesis tool 103, circuit netlist 104, physical implementation tool 105 and layout 106. The architecture design tool 101, logic synthesis tool 103 and physical implementation tool 105 can be different EDA software, or they can be units or modules in the same EDA software for performing different functions.
[0080] Specifically, the architecture design tool 101 is used to receive chip design requirements associated with chip design, for example: module information determined based on the design requirements, the module information including at least one of the module's function, number, area, location, hierarchical relationship between modules, or interconnection relationship between modules. It should be noted that the module in this application may refer to various functional modules, macro units, etc. in digital chip design.
[0081] Specifically, the architecture design tool 101 is also used to output the architecture design of the chip and the RTL code 102 corresponding to the architecture design. The architecture design can indicate the logical information and physical information of the chip. In some embodiments, the architecture design can be a physical architecture planning design, for example, including at least one of the following: the design of the shape, position, insertion of a register module for time synchronization, or routing between modules. The architecture design can also be a design exchange format (DEF).
[0082] In some embodiments, the architecture design tool 101 may have a graphical user interface (GUI) and may interact with user input using the GUI. For example, the architecture design tool 101 may receive user input based on gestures, contacts, stylus, or mouse pointers. Alternatively or additionally, the architecture design tool 101 may receive user input based on code instructions. For example, a user may input operations for modules to the architecture design tool 101 in the form of code commands, such as operations to increase or decrease modules, to generate an architecture design and output RTL code.
[0083] Specifically, the logic synthesis tool 103 is used to receive the RTL code 102 and output a circuit netlist 104 based on the RTL code.
[0084] Specifically, the physical implementation tool 105 is used to receive the circuit netlist 104 and perform steps such as layout and routing and clock tree synthesis based on the circuit netlist 104 to generate a layout 106 for chip manufacturing.
[0085] It is understandable that Electronic Design Automation (EDA) software is widely used in the functional design, synthesis, verification, simulation and other processes of chips. With the help of EDA software, engineers can easily carry out the design process of digital chips, such as: architecture design and register transfer level (RTL) code design, logic synthesis, design for test (DFT), physical development and signoff. In the architecture design and RTL code design stage, engineers determine the architecture design of the chip based on design requirements, such as the functions and initial layout planning of each module, and use hardware description languages (such as Verilog or VHDL) to write RTL code for describing the logic function of the circuit. In the logic synthesis stage, considering the specific way to realize the logic function of the circuit (for example, suitable units and processes), the RTL code is converted into a circuit netlist in the form of logic gates. In the physical implementation stage, engineers determine a more sophisticated physical layout plan and corresponding layout and routing based on the circuit netlist, thereby determining the final chip design, that is, generating a layout for chip manufacturing.
[0086] At present, chip safety verification usually tests the implementation of safety mechanisms through fault injection and evaluates the diagnostic coverage of chip safety mechanisms, so as to determine whether the chip meets the functional safety level assessment and generate a chip functional safety assessment report.
[0087] However, the existing safety verification method is to test ready-made chips after production, and generate a chip functional safety assessment report by judging whether the ready-made chips meet the predetermined indicators. However, this method requires adjusting the chip design and conducting repeated tests after the test results do not meet the predetermined indicators, resulting in longer testing time and lower testing efficiency.
[0088] In view of this, an embodiment of the present application provides a chip safety design method, which determines whether the diagnostic coverage of the chip meets the functional safety design conditions through error simulation. If not, the circuit design code is iteratively modified until the diagnostic coverage of the chip meets the functional safety design conditions, so as to improve the chip testing efficiency and ensure the safety of the chip.
[0089] See also Figure 2 , Figure 2 It is a flowchart of a chip security design method provided in an embodiment of the present application.
[0090] like Figure 2 As shown, the security design method of the chip includes:
[0091] Step S201: obtaining a first circuit design code, and parsing the first circuit design code to generate a circuit netlist.
[0092] Specifically, the first circuit design code includes a circuit RTL code, and the circuit RTL code is used to describe the logic function of the circuit. By parsing the circuit RTL code, for example, performing RTL synthesis on the circuit RTL code, a circuit netlist can be obtained.
[0093] It is understood that RTL synthesis is a key step in digital circuit design, which converts a high-level abstract design written in a hardware description language (HDL) into a specific gate-level logic representation. In some embodiments, RTL synthesis is performed by an EDA tool, such as Synopsys' Design Compiler or Cadence's Genus. By performing RTL synthesis on the circuit RTL code through the synthesis tool, a circuit netlist (netlist), that is, a gate-level netlist, can be obtained.
[0094] Step S202: Determine a register list according to the circuit netlist.
[0095] It is understandable that the circuit netlist is used to describe how to use specific logic gates and connections to implement the functions described in the original RTL. In addition, the circuit netlist is used to show in detail how the logic functions are implemented through a series of standard circuit units (such as logic gates, triggers, etc.) and the connections between standard circuit units. Among them, since registers in digital circuit design are usually implemented by triggers, registers usually appear in the form of triggers in the circuit netlist, for example, in the form of D triggers.
[0096] In some embodiments, by extracting registers from a circuit netlist through a script command, all registers in the circuit netlist can be obtained, and then a register list file can be obtained, and the register list file includes a register list list. For example, by parsing the circuit netlist file, all register-related information can be identified and extracted. Specifically, parsing the circuit netlist file to obtain a register list list can include the following steps:
[0097] (1) Use text search, regular expressions, or dedicated parsing tools to search for all trigger instances. For example, use the search function of a text editor or write a script (such as Python) to apply regular expressions to find lines that match the trigger naming rules to search for trigger instances.
[0098] (2) For each found trigger instance, extract relevant information, such as instance name, input signal, output signal, clock signal, reset or set signal.
[0099] (3) Determine the register based on the extracted trigger instance, wherein the instance name, input signal, output signal, clock signal, reset or set signal are used to identify the function of a single register and its role in the circuit, thereby identifying the register information. It can be understood that a register includes one or more triggers.
[0100] (4) The extracted register information is summarized into a register list, which is used to list key attributes of each register, such as name, type, clock signal, control signal, etc.
[0101] Step S203: extracting the error injection points of each module according to the register list to generate an error injection point list.
[0102] In some embodiments, the chip includes a processor chip, a memory chip, an application-specific integrated circuit chip, a network and communication chip, a sensor chip, a lidar chip, and other chips.
[0103] It should be noted that the chip includes multiple modules. Since the present application performs security design before chip production, the chip corresponds to the architecture design output by the architecture design tool. Therefore, the modules in the chip are functional modules in the architecture design, and the architecture design corresponding to the chip is used for chip simulation.
[0104] In some embodiments, each module includes multiple registers, and the register list is used to store the correspondence between each register of each module. For example, the register list stores the correspondence between each register of each module in the following format: Block_A.reg_A, Block_A.reg_B, Block_A.reg_C.
[0105] By extracting the error injection points from the register list, the error injection points corresponding to each module are configured. Since the number of registers of each module may be different, the error injection points in the register list may be extracted by different extraction methods.
[0106] It is understandable that Fault Injection Points refer to interfaces or paths that are deliberately reserved in the architecture design to intentionally introduce errors or abnormal conditions to simulate various faults that may occur in actual applications. By injecting errors or abnormalities into the Fault Injection Points, it is possible to verify and test the response of the chip or system when facing abnormal, erroneous or faulty conditions, thereby evaluating the robustness and fault tolerance of the chip.
[0107] Specifically, according to the register list, the error injection points of each module are extracted to generate an error injection point list, including:
[0108] All error injection points of each module in the register list are extracted to generate an error injection point list.
[0109] Alternatively, according to a preset extraction ratio, a number of error injection points of each module in the register list are extracted to generate an error injection point list.
[0110] Alternatively, random sampling is performed according to a preset sampling ratio to generate a list of error injection points.
[0111] In some embodiments, since the number of registers of different modules is different, one register may correspond to one or at least two error injection points. Therefore, the corresponding error injection points can be extracted according to the number of registers of each module, so that the module with a larger number of registers can extract more error injection points, for example: extraction is performed according to a preset extraction ratio, wherein the preset extraction ratio corresponding to each module can be the same or different, for example: the extraction ratio corresponding to each module is the same, then the number of error injection points extracted by each module = the number of error injection points of each module * the preset extraction ratio.
[0112] It can be understood that since the security levels of different modules are different, for example, the security level of the processor module is higher than the security level of the network module, the number of error injection points of the two modules can be set accordingly according to their security levels, so that the number of error injection points of the processor module is greater than the number of error injection points of the network module.
[0113] For details, please refer to Figure 3 , Figure 3 yes Figure 2 Detailed flowchart of step S203 in FIG.
[0114] like Figure 3 As shown, step S203 includes:
[0115] Step S231: Obtain the security level of each module.
[0116] Specifically, each module corresponds to the same or different security level. For example, the chip includes modules such as processor module, storage module, communication module, sensor interface module, etc., and the processor module corresponds to the first security level, the storage module corresponds to the second security level, the communication module corresponds to the third security level, and the sensor interface module corresponds to the fourth security level.
[0117] Step S232: Determine the extraction ratio of each module according to the security level of each module.
[0118] Specifically, assuming that the module corresponds to four different security levels, namely the first security level, the second security level, the third security level, and the fourth security level, the first security level corresponds to the first extraction ratio, the second security level corresponds to the second extraction ratio, the third security level corresponds to the third extraction ratio, and the fourth security level corresponds to the fourth extraction ratio. Among them, the security levels are in the order of first security level > second security level > third security level > fourth security level, then the first extraction ratio > second extraction ratio > third extraction ratio > fourth extraction ratio. For example: the first extraction ratio is set to 100%, the second extraction ratio is set to 75%, the third extraction ratio is set to 50%, and the fourth extraction ratio is set to 25%.
[0119] Step S233: extracting a number of error injection points of each module in the register list according to the extraction ratio of each module to generate an error injection point list.
[0120] Specifically, according to the extraction ratio corresponding to the security level of each module, a number of error injection points of the module are extracted from the register list, wherein the number of error injection points of the module = the total number of error injection points of the module * extraction ratio. By synthesizing all error injection points of each module, an error injection point list is generated.
[0121] Step S204: performing error simulation on the chip according to the error injection point list to determine the diagnostic coverage of the chip.
[0122] Specifically, according to the error injection point list, all error injection points in the error injection point list are injected by modifying the software code or the simulator configuration file in the circuit function simulation environment, and error simulation is performed based on the test platform to run the test platform using the simulation tool, and error injection is enabled through the configuration file or command line parameter. After the error simulation is completed, the error simulation result is obtained, wherein the error simulation result includes the error detection situation of each error injection point. By counting the error detection situation of each error injection point, the diagnostic coverage of the chip can be determined.
[0123] It can be understood that a circuit functional simulation environment is a collection of software and tools used to simulate and verify the functionality and behavior of electronic circuits without physically building the circuit. The circuit functional simulation environment can simulate the response of the circuit under different conditions and configurations to determine how the circuit will perform in actual applications.
[0124] For details, please refer to Figure 4 , Figure 4 yes Figure 2Detailed flowchart of step S204 in FIG.
[0125] like Figure 4 As shown, step S204 includes:
[0126] Step S241: Determine the diagnostic coverage of each module of the chip.
[0127] In some embodiments, the diagnostic coverage of each module is related to the error detection conditions of all error injection points of each module.
[0128] Step S242: Calculate the diagnostic coverage of the chip according to the diagnostic coverage of each module.
[0129] Specifically, each module corresponds to a weight, where the diagnostic coverage of the chip is the weighted sum of the diagnostic coverage corresponding to each module, that is, the product of the diagnostic coverage corresponding to each module and its corresponding weight is calculated, and the products of all modules are added together to obtain the weighted sum of the diagnostic coverage corresponding to each module, thereby obtaining the diagnostic coverage corresponding to the chip. It can be understood that the sum of the weights of all modules of the chip is 1.
[0130] For details, please refer to Figure 5 , Figure 5 yes Figure 4 A detailed flowchart of step S241 in FIG.
[0131] like Figure 5 As shown, step S241 includes:
[0132] Step S2411: In a circuit function simulation environment, inject error behavior into the error injection point of each module to determine the error detection status of each error injection point in each module.
[0133] Step S2412: Determine the diagnostic coverage of each module according to the error detection status of each error injection point.
[0134] Specifically, the diagnostic coverage of each module is calculated by counting the error detection situations of all error injection points of each module, wherein the diagnostic coverage of each module = the number of error injection points detected for the error detection situation / the total number of error injection points of the module.
[0135] Please refer to Figure 6 , Figure 6 yes Figure 5 A detailed flowchart of step S2411 in FIG.
[0136] like Figure 6 As shown, step S2411 includes:
[0137] Step S2401: In a circuit function simulation environment, inject error behavior into the error injection point of each module.
[0138] Specifically, the erroneous behavior is injected by directly modifying the HDL code corresponding to the module in the test platform or using conditional compilation instructions.
[0139] Step S2402: Obtain a signal corresponding to the error flag of each error injection point.
[0140] Specifically, each error injection point corresponds to an error flag bit, and the error flag bit is used to indicate whether the error behavior of the error injection point is correctly identified.
[0141] Step S2403: Determine whether the signal corresponding to the error flag is a valid signal.
[0142] Specifically, by judging whether the signal corresponding to the error flag is a valid signal, it is determined whether the error behavior of the error injection point is correctly identified. If the signal corresponding to the error flag is a valid signal, it is determined that the error behavior of the error injection point is correctly identified; if the signal corresponding to the error flag is an invalid signal, it is determined that the error behavior of the error injection point is not correctly identified.
[0143] If the signal corresponding to the error flag is a valid signal, proceed to step S2404.
[0144] If the signal corresponding to the error flag is an invalid signal, proceed to step S2405.
[0145] Step S2404: Determine that the error detection status of the error injection point is detected.
[0146] Specifically, if the signal corresponding to the error flag is a valid signal, it means that the error injection is correctly identified, and the error detection condition of the error injection point is determined to be detected. For example, according to the circuit design level and signal name of the error flag signal provided by the designer, the monitor can be entered in the simulation environment to confirm whether the error flag detects the error detection condition. For example, if the signal corresponding to the error flag is a valid signal, the error detection condition is determined to be detected, indicating that the error injection is correctly identified. If the signal corresponding to the error flag is an invalid signal, the error detection condition is determined to be undetected, indicating that the error injection is not correctly identified.
[0147] Step S2405: Determine that the error detection status of the error injection point is not detected.
[0148] Specifically, if the signal corresponding to the error flag is an invalid signal, it means that the error injection is not recognized, and the error detection status of the error injection point is determined to be undetected.
[0149] Furthermore, the error types corresponding to each error injection point may be the same or different, wherein the error types include fixed errors and transient errors, and the error injection points may be configured or programmed to simulate error behaviors of different error types. Therefore, the present application may simulate the error type of each error injection point to obtain the error detection situation of each error injection point.
[0150] Specifically, by determining the error type corresponding to each error injection point; according to the error type corresponding to each error injection point, simulating the error behavior of each error injection point; wherein the error type corresponding to each error injection point can be a fixed error, a transient error, or a fixed error and a transient error.
[0151] It should be noted that, by configuring parameters, the error injection point can be set to introduce fixed errors and / or transient errors. For example, the duration, frequency and triggering conditions of the error behavior can be set, and the error injection mode can be selected by using a script or command to trigger a specific type of error behavior, thereby introducing fixed errors and / or transient errors, wherein the error injection mode includes a fixed error mode and a transient error mode.
[0152] Further, after determining the error type corresponding to each error injection point, determining the error detection status of each error injection point in each module includes:
[0153] According to the signal corresponding to the error flag bit corresponding to each error injection point, the error detection situation corresponding to the error type of each error injection point is determined; wherein the error type corresponding to each error injection point includes a fixed error and / or a transient error.
[0154] Step S205: Determine whether the diagnostic coverage of the chip meets the functional safety design requirements.
[0155] Specifically, the functional safety design conditions are related to the functional safety level, for example: the functional safety level includes the ASIL (Automotive Safety Integrity Level) level, which is the automotive safety integrity level, a key concept defined in the ISO 26262 standard, used to evaluate and classify the safety requirements of automotive electronic systems and components. Among them, the ASIL level includes ASIL A, ASIL B, ASIL C and ASIL D. Among them, ASIL A corresponds to the lowest safety requirements and is applicable to functions with lower risks; ASIL B corresponds to medium safety requirements and is applicable to functions with medium risks; ASIL C corresponds to higher safety requirements and is applicable to functions with high risks; ASIL D corresponds to the highest safety requirements and is applicable to functions with extremely high risks.
[0156] Among them, each ASIL level corresponds to a diagnostic coverage threshold. For example, the diagnostic coverage threshold corresponding to ASIL C is 95%.
[0157] By judging whether the diagnostic coverage of the chip is greater than or equal to the diagnostic coverage threshold corresponding to the functional safety design condition, if so, it is determined that the diagnostic coverage of the chip meets the functional safety design condition; if not, it is determined that the diagnostic coverage of the chip does not meet the functional safety design condition.
[0158] If the diagnostic coverage of the chip meets the functional safety design conditions, proceed to step S207.
[0159] If the diagnostic coverage of the chip does not meet the functional safety design conditions, proceed to step S206.
[0160] Furthermore, since the error types of the error injection point include fixed errors and transient errors, the chip corresponds to a fixed failure coverage and a transient failure coverage, respectively. The present application can judge whether the diagnostic coverage of the chip meets the functional safety design conditions through the fixed failure coverage and transient failure coverage of the chip.
[0161] For details, please refer to Figure 7 , Figure 7 yes Figure 2 A detailed flowchart of step S205 in FIG.
[0162] like Figure 7 As shown, step S205 includes:
[0163] Step S2051: Obtain the fixed failure coverage and transient failure coverage of the chip.
[0164] It is understandable that in chip verification and testing, fixed failure coverage and transient failure coverage correspond to fixed failures (Intermittent Faults) and transient failures (Transient Faults) respectively. Fixed failures and transient failures are two different types of hardware failure modes, which differ in the persistence and repeatability of failures. For example:
[0165] Fixed failures are when a chip or circuit continues to fail under certain conditions, but may work properly under other conditions. This failure mode is usually caused by physical defects or design errors in the hardware, such as: Physical defects: such as cracks, oxidation or corrosion in metal lines, resulting in increased resistance or open circuits; Design errors: such as logic errors, timing problems or power management problems, which cause the circuit to not work correctly under certain conditions.
[0166] The characteristics of fixed failures are: persistence: once the failure condition is triggered, the fault usually persists until the failure condition is removed or repaired; repeatability: under the same conditions, fixed failures can usually be triggered repeatedly.
[0167] Transient failure refers to a short-term failure of a chip or circuit under certain conditions, but these failures usually do not persist and may disappear on their own without any intervention. This failure mode is usually caused by external interference or internal noise, such as: external interference: such as electromagnetic interference (EMI), voltage transients or temperature fluctuations; internal noise: such as thermal noise in the circuit, power supply noise or process changes.
[0168] The characteristics of transient failures are: short-term: the fault usually lasts only for a short time, perhaps only a few clock cycles or shorter; non-repeatability: under the same conditions, transient failures may not be triggered repeatedly, or the triggering conditions may be very difficult to reproduce.
[0169] Since the occurrence conditions of fixed failures and transient failures are different, it is necessary to calculate the fixed failure coverage and transient failure coverage, that is, the fixed error coverage and transient error coverage, respectively.
[0170] Specifically, the fixed failure coverage of the chip is obtained, including:
[0171] Obtain the fixed failure coverage of each module of the chip.
[0172] The fixed failure coverage of the chip is calculated based on the fixed failure coverage of each module of the chip. Each module corresponds to a weight, and the fixed failure coverage of the chip is the weighted sum of the fixed failure coverage corresponding to each module, that is, the product of the fixed failure coverage corresponding to each module and its corresponding weight is calculated, and the products of all modules are added together to obtain the weighted sum of the fixed failure coverage corresponding to each module, thereby obtaining the fixed failure coverage corresponding to the chip. It can be understood that the sum of the weights of all modules of the chip is 1.
[0173] Similarly, the transient failure coverage of the chip is obtained, including:
[0174] Obtain the transient failure coverage of each module of the chip.
[0175] According to the transient failure coverage of each module of the chip, the transient failure coverage of the chip is calculated. Among them, each module corresponds to a weight, and the transient failure coverage of the chip is the weighted sum of the transient failure coverage corresponding to each module, that is, the product of the transient failure coverage corresponding to each module and its corresponding weight is calculated, and the products of all modules are added together to obtain the weighted sum of the transient failure coverage corresponding to each module, thereby obtaining the transient failure coverage corresponding to the chip. It can be understood that the sum of the weights of all modules of the chip is 1.
[0176] In an embodiment of the present application, the fixed failure coverage and transient failure coverage of the chip are calculated by combining the fixed failure coverage and transient failure coverage of each module of the chip with the weight of each module. This can better determine the fixed failure coverage and transient failure coverage of the chip, which is helpful in determining whether the chip meets the functional safety design conditions.
[0177] Step S2052: Determine whether the fixed failure coverage of the chip is greater than or equal to a first coverage threshold.
[0178] Specifically, the first coverage rate threshold is a preset threshold, and the first coverage rate threshold is related to the functional safety level, and each functional safety level corresponds to a first coverage rate threshold, and the first coverage rate threshold is represented in the form of a percentage. It can be understood that the higher the functional safety level, the larger the first coverage rate threshold.
[0179] If the fixed failure coverage of the chip is greater than or equal to the first coverage threshold, the process proceeds to step S2053.
[0180] If the fixed failure coverage of the chip is less than the first coverage threshold, the process proceeds to step S805.
[0181] Step S2053: Determine whether the transient failure coverage of the chip is greater than or equal to a second coverage threshold.
[0182] Specifically, if the fixed failure coverage of the chip is greater than or equal to the first coverage threshold, it is further determined whether the transient failure coverage of the chip is greater than or equal to the second coverage threshold.
[0183] The second coverage rate threshold is a preset threshold, which is related to the functional safety level, and each functional safety level corresponds to a second coverage rate threshold, which is represented in the form of a percentage. It can be understood that the higher the functional safety level, the larger the second coverage rate threshold.
[0184] If the transient failure coverage of the chip is greater than or equal to the second coverage threshold, the process proceeds to step S2054.
[0185] If the fixed failure coverage of the chip is less than the first coverage threshold, the process proceeds to step S2055.
[0186] It is understandable that the order of determining whether the fixed failure coverage of the chip is greater than or equal to the first coverage threshold, or determining whether the transient failure coverage of the chip is greater than or equal to the second coverage threshold, may be different. For example, the transient failure coverage may be determined first, and then the fixed failure coverage may be determined. Alternatively, the determinations may be made simultaneously, and this application does not limit this.
[0187] It can be understood that the first coverage threshold is generally greater than the second coverage threshold. For example, at ASIL-B level, the first coverage threshold is 90% and the second coverage threshold is 60%.
[0188] Step S2054: Determine whether the diagnostic coverage of the chip meets the functional safety design requirements.
[0189] Specifically, if the fixed failure coverage of the chip is greater than or equal to the first coverage threshold, and the transient failure coverage of the chip is greater than or equal to the second coverage threshold, it is determined that the diagnostic coverage of the chip meets the functional safety design conditions.
[0190] Step S2055: Determine whether the diagnostic coverage of the chip does not meet the functional safety design requirements.
[0191] Specifically, if the fixed failure coverage of the chip is less than the first coverage threshold, or the transient failure coverage of the chip is less than the second coverage threshold, it is determined that the diagnostic coverage of the chip does not meet the functional safety design conditions.
[0192] In the embodiment of the present application, by comprehensively considering the fixed failure coverage and the transient failure coverage, the two are used to jointly confirm whether the diagnostic coverage of the chip meets the functional safety design conditions, which can better determine whether the chip meets the functional safety design conditions and is beneficial to ensuring the stability of the subsequently produced chips.
[0193] Step S206: modify the first circuit design code to obtain a second circuit design code.
[0194] It is understandable that different circuit design codes may correspond to different diagnostic coverages, and the first circuit design code is modified in order to improve the diagnostic coverage of the chip.
[0195] Error simulation is used to determine whether the chip's diagnostic coverage meets the functional safety design conditions. If not, the circuit design code is iteratively modified until the chip's diagnostic coverage meets the functional safety design conditions. This application can improve the chip's testing efficiency and ensure the chip's safety.
[0196] For details, please refer to Figure 8 , Figure 8 yes Figure 2 Detailed flowchart of step S206 in .
[0197] like Figure 8 As shown, step S206 includes:
[0198] Step S261: Obtain the chip test method.
[0199] Specifically, the chip test mode includes a first test mode, a second test mode or a third test mode;
[0200] Specifically, the chip testing method is a testing technology preset by the chip architecture design, such as STL (Software Test Library, STL) testing, BIST (Built-In Self-Test) testing, and PGC (Programmable Gate Array) testing.
[0201] In some embodiments, the first test mode includes an STL test, the second test mode includes a BIST test, and the third test mode includes a PGC test.
[0202] It can be understood that STL testing is a method used to test key functions and fault tolerance in chip design. STL testing is mainly used to verify the correctness and stability of the chip under various operating conditions to ensure that the chip can operate reliably in actual use. BIST testing is a testing technology integrated into the chip to automatically detect and verify the hardware functions of the chip. BIST technology enables the chip to perform self-testing without external testing equipment by embedding specialized test circuits and algorithms in the chip design. PGC testing is a testing method for programmable logic devices (such as FPGAs and CPLDs). PGC testing is mainly used to verify the correctness and stability of these programmable logic devices during configuration and operation.
[0203] Step S262: If the test mode of the chip is the first test mode, modify the first circuit design code to add a running program for testing to generate a second circuit design code.
[0204] Specifically, if the chip test method is STL test, the first circuit design code is modified so that the code about the running program in the first circuit design code is increased, or the code about the software configuration in the first circuit design code is increased to generate the second circuit design code. By adding the running program and / or software configuration for testing, more circuits are used for operation to identify the error behavior of the error injection point, which can improve the diagnostic coverage of the chip.
[0205] Step S263: If the test mode of the chip is the second test mode, modify the first circuit design code to add stimulus data for testing to generate a second circuit design code.
[0206] Specifically, if the chip is tested in a BIST test mode, the first circuit design code is modified so that the stimulus data used for the test is increased to generate the second circuit design code. By increasing the stimulus data used for the test, more circuits are used to run to identify the error behavior of the error injection point, which can improve the diagnostic coverage of the chip.
[0207] Step S264: If the chip test mode is the third test mode, modify the first circuit design code to increase the inspection data for the test and / or increase the number of test stimuli to generate a second circuit design code.
[0208] Specifically, if the chip test mode is PGC test, the first circuit design code is modified so that the inspection data for the test and / or the test stimulus for the test are used to generate the second circuit design code. By increasing the inspection data and / or the test stimulus for the test, more circuits are used to run to identify the error behavior of the error injection point, which can improve the diagnostic coverage of the chip.
[0209] In some embodiments, the test stimulus includes a pattern test stimulus, which refers to a series of predefined signal or data patterns used to activate and test specific parts of a chip or circuit to evaluate its performance, functional correctness, and / or tolerance (such as fault tolerance). These test stimulus patterns are designed to simulate situations that may be encountered in actual operation, or to trigger specific types of hardware behaviors to facilitate systematic discovery and diagnosis of problems.
[0210] In some embodiments, different modules may correspond to different test methods. Therefore, the code corresponding to the module in the first circuit design code may be modified according to the test methods corresponding to the different modules to obtain the second circuit design code. For example, if the test method of a module is the first test method, the code corresponding to the module in the first circuit design code may be modified to add a running program for testing; or, if the test method of a module is the second test method, the code corresponding to the module in the first circuit design code may be modified to add stimulus data for testing; or, if the test method of a module is the third test method, the code corresponding to the module in the first circuit design code may be modified to add inspection data for testing and / or increase the number of test stimuli.
[0211] It is understandable that when modifying the first circuit design code, the codes corresponding to at least two modules may be modified simultaneously or successively to achieve code adjustment of at least two modules and better improve the diagnostic coverage of the chip.
[0212] Step S207: Determine whether the chip meets the functional safety design requirements.
[0213] Specifically, if the diagnostic coverage of the chip is greater than or equal to the diagnostic coverage threshold corresponding to the functional safety design condition, it is determined that the chip meets the functional safety design condition.
[0214] Please refer to Fig. 9 , Fig. 9 It is a schematic diagram of the overall process of a chip security design method provided in an embodiment of the present application.
[0215] like Fig. 9 As shown in the figure, the overall process of the chip's security design method includes:
[0216] start;
[0217] Step S901: Obtain circuit RTL code.
[0218] Step S902: Perform RTL synthesis on the circuit RTL code to obtain a circuit netlist.
[0219] Step S903: extract all registers in the circuit netlist to obtain a register list.
[0220] Step S904: extract error injection points to obtain an error injection point list.
[0221] Specifically, the error injection points of each module are extracted, and the error injection points of each module are integrated to obtain the error injection point list of the chip.
[0222] Step S905: Building a circuit function simulation environment.
[0223] Specifically, a test platform is built next to the design circuit code, which includes an error stimulus generating unit, a result unit, a signal interconnection unit and other units to build a circuit function simulation environment, wherein the test platform is used to generate test vectors and check simulation results.
[0224] Step S906: traverse the error injection points to perform error simulation.
[0225] Specifically, the error injection points in the error injection point list are traversed, and error simulation is performed based on each error injection point to obtain an error simulation result for each error injection point.
[0226] Step S907: monitor the error flag of the error injection point.
[0227] Specifically, the error flag bit of the error injection point of each module is monitored.
[0228] Step S908: Count the error detection status of each module.
[0229] Specifically, according to the error flag bit of each error injection point of each module, the error detection status of each module is counted.
[0230] Step S909: Determine the fixed failure coverage of each module.
[0231] Step S910: Determine the transient failure coverage of each module.
[0232] Step S911: Determine whether the diagnostic coverage of the chip meets the functional safety design requirements.
[0233] Specifically, the fixed failure coverage of the chip is calculated based on the fixed failure coverage of each module, and the transient failure coverage of the chip is calculated based on the transient failure coverage of each module. The chip's diagnostic coverage is further judged based on the fixed failure coverage and transient failure coverage of the chip to determine whether it meets the functional safety design conditions. For specific judgment methods, please refer to Figure 8The description of the above-mentioned related contents will not be repeated here.
[0234] Finish.
[0235] In an embodiment of the present application, error simulation is used to determine whether the diagnostic coverage of the chip meets the functional safety design conditions. If not, the circuit design code is iteratively modified until the diagnostic coverage of the chip meets the functional safety design conditions. The present application can improve the testing efficiency of the chip and ensure the safety of the chip.
[0236] See also Fig.10 , Fig.10 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application.
[0237] like Fig.10 As shown, the electronic device 1000 includes one or more processors 1001 and a memory 1002. Fig.10 A processor 1001 is taken as an example.
[0238] The processor 1001 and the memory 1002 may be connected via a bus or other means. Fig.10 The example of connecting through bus is taken in the following.
[0239] The processor 1001 is used to provide computing and control capabilities to execute the chip security design method in any one of the above method embodiments, including:
[0240] Obtain a first circuit design code and parse the first circuit design code to generate a circuit netlist; determine a register list based on the circuit netlist; extract error injection points of each module based on the register list to generate an error injection point list; perform error simulation on the chip based on the error injection point list to determine the diagnostic coverage of the chip; if the diagnostic coverage of the chip does not meet the functional safety design conditions, modify the first circuit design code to obtain a second circuit design code, and repeat the error simulation until the diagnostic coverage of the chip meets the functional safety design conditions.
[0241] Error simulation is used to determine whether the chip's diagnostic coverage meets the functional safety design conditions. If not, the circuit design code is iteratively modified until the chip's diagnostic coverage meets the functional safety design conditions. This application can improve the chip's testing efficiency and ensure the chip's safety.
[0242] The processor 1001 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), a hardware chip or any combination thereof; it may also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.
[0243] The memory 1002, as a non-transient computer-readable storage medium, can be used to store non-transient software programs, non-transient computer executable programs and modules, such as program instructions / modules corresponding to the chip security design method in the embodiment of the present application. The processor 1001 can implement the chip security design method in any of the above method embodiments by running the non-transient software programs, instructions and modules stored in the memory 1002. Specifically, the memory 1002 may include a volatile memory (volatile memory, VM), such as a random access memory (random access memory, RAM); the memory 1002 may also include a non-volatile memory (non-volatile memory, NVM), such as a read-only memory (read-only memory, ROM), a flash memory (flash memory), a hard disk drive (hard disk drive, HDD) or a solid-state drive (solid-state drive, SSD) or other non-transient solid-state storage devices; the memory 1002 may also include a combination of the above types of memories.
[0244] The memory 1002 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage devices. In some embodiments, the memory 1002 may optionally include a memory remotely arranged relative to the processor 1001, and these remote memories may be connected to the processor 1001 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
[0245] One or more modules are stored in the memory 1002, and when executed by one or more processors 1001, the chip security design method in any of the above method embodiments is executed, for example, the above described Figure 2 The steps shown.
[0246] An embodiment of the present application also provides a non-volatile computer storage medium, which stores computer executable instructions, and the computer executable instructions are executed by one or more processors. For example, the one or more processors can execute the chip security design method in any of the above method embodiments, for example, execute the various steps described above.
[0247] The above-described device or equipment embodiments are merely illustrative, wherein the unit modules described as separate components may or may not be physically separated, and the components displayed as module units may or may not be physical units, that is, they may be located in one place, or may be distributed on multiple network module units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment.
[0248] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a general hardware platform, and of course, by hardware. Based on this understanding, the above technical solution can be essentially or in other words, the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute various embodiments or certain parts of the embodiments.
[0249] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Under the concept of the present application, the technical features in the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other changes in different aspects of the present application as above, which are not provided in detail for the sake of simplicity. Although the present application has been described in detail with reference to the aforementioned embodiments, a person of ordinary skill in the art should understand that the technical solutions described in the aforementioned embodiments can still be modified, or some of the technical features can be replaced by equivalents. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.
Claims
1. A chip security design method, characterized in that: The chip includes multiple modules, and the method includes: Acquire a first circuit design code, and parse the first circuit design code to generate a circuit netlist; Determine a register list according to the circuit netlist; Extracting the error injection point of each module according to the register list to generate an error injection point list; According to the error injection point list, error simulation is performed on the chip to determine the diagnostic coverage of the chip; If the diagnostic coverage of the chip does not meet the functional safety design conditions, the first circuit design code is modified to obtain a second circuit design code, and the error simulation is repeated until the diagnostic coverage of the chip meets the functional safety design conditions.
2. The method according to claim 1, characterized in that Extracting the error injection point of each module according to the register list to generate an error injection point list includes: Extracting all error injection points of each module in the register list; Alternatively, a plurality of error injection points of each module in the register list are extracted according to a preset extraction ratio.
3. The method according to claim 1, characterized in that Extracting the error injection point of each module according to the register list to generate an error injection point list includes: Get the security level of each module; According to the security level of each module, determine the extraction ratio of each module, wherein each security level corresponds to an extraction ratio; According to the extraction ratio of each module, a number of error injection points of each module in the register list are extracted to generate an error injection point list.
4. The method according to claim 1, characterized in that: Determining the diagnostic coverage of the chip includes: Determining the diagnostic coverage of each module of the chip; The diagnostic coverage of the chip is calculated according to the diagnostic coverage of each module.
5. The method according to claim 4, characterized in that Determining the diagnostic coverage of each module of the chip includes: In the circuit function simulation environment, error behavior is injected into the error injection point of each module to determine the error detection status of each error injection point in each module; Based on the error detection of each error injection point, the diagnostic coverage of each module is determined.
6. The method according to claim 5, characterized in that The step of injecting error behavior into the error injection point of each module and determining the error detection situation of each error injection point in each module includes: Get the signal corresponding to the error flag bit of each error injection point; According to the signal corresponding to the error flag bit corresponding to each error injection point, the error detection status of each error injection point is determined.
7. The method according to claim 6, characterized in that The step of determining the error detection status of each error injection point according to a signal corresponding to an error flag bit corresponding to each error injection point includes: If the signal corresponding to the error flag bit is a valid signal, then the error detection condition of the error injection point is determined to be detected; If the signal corresponding to the error flag bit is an invalid signal, it is determined that the error detection status of the error injection point is not detected.
8. The method according to claim 6 or 7, characterized in that: The method further comprises: Determine the error type corresponding to each error injection point; According to the error type corresponding to each error injection point, the error behavior of each error injection point is simulated; Determining the error detection condition of each error injection point in each module includes: Determine the error detection status corresponding to the error type of each error injection point according to the signal corresponding to the error flag bit corresponding to each error injection point; The error type corresponding to each error injection point includes a fixed error and / or a transient error.
9. The method according to claim 1, characterized in that: The modifying the first circuit design code to obtain the second circuit design code specifically includes: Acquire a test mode of the chip, wherein the test mode of the chip includes a first test mode, a second test mode or a third test mode; If the test mode of the chip is the first test mode, modifying the first circuit design code to add a running program for testing to generate a second circuit design code; If the test mode of the chip is the second test mode, modifying the first circuit design code to add stimulus data for testing to generate a second circuit design code; If the test mode of the chip is the third test mode, the first circuit design code is modified to increase the inspection data used for the test and / or the number of test stimuli is increased to generate the second circuit design code.
10. The method according to claim 1, characterized in that The diagnostic coverage of the chip includes fixed failure coverage and transient failure coverage, and the functional safety design condition includes a first coverage threshold and a second coverage threshold; The method further comprises: Determine whether the diagnostic coverage of the chip meets the functional safety design conditions, including: Determine whether the fixed failure coverage of the chip is greater than or equal to a first coverage threshold, and whether the transient failure coverage is greater than or equal to a second coverage threshold; If the fixed failure coverage of the chip is greater than or equal to the first coverage threshold, and the transient failure coverage is greater than or equal to the second coverage threshold, it is determined that the diagnostic coverage of the chip meets the functional safety design conditions; If the fixed failure coverage of the chip is less than the first coverage threshold, or the transient failure coverage is less than the second coverage threshold, it is determined that the diagnostic coverage of the chip does not meet the functional safety design conditions.
11. An electronic device, characterized in that: include: A processor and a memory, wherein the processor is used to execute an executable program code in the memory, and when the executable program code is executed, the processor executes instructions of the chip security design method as described in any one of claims 1 to 10.
12. A non-volatile computer-readable storage medium, characterized in that: The non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed, the chip security design method as described in any one of claims 1 to 10 is implemented.
Citation Information
Cited By
Chip testability design program code generation device and method
CN119337786A
Chip testability design program code generation device and method
CN119337786B
Method and device for improving diagnosis coverage rate, automobile chip and medium
CN119356928A
A method, device, automotive chip and medium for improving diagnostic coverage
CN119356928B
Method and device for improving diagnosis coverage rate in gate-level netlist stage
CN119378463A
