CN113535547B - Test method based on functional safety - Google Patents
Test method based on functional safety Download PDFInfo
- Publication number
- CN113535547B CN113535547B CN202110682645.8A CN202110682645A CN113535547B CN 113535547 B CN113535547 B CN 113535547B CN 202110682645 A CN202110682645 A CN 202110682645A CN 113535547 B CN113535547 B CN 113535547B
- Authority
- CN
- China
- Prior art keywords
- safety
- test
- failure mode
- coverage rate
- security
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/26—Functional testing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3676—Test management for coverage analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
Abstract
The invention provides a test method based on functional safety, which comprises the following steps: s1, inputting the security module to be tested; s2, searching a chip security mechanism library and a functional security test case library; s3, selecting all safety mechanisms and test case tables of the safety modules to be tested; s4, determining fault models and failure modes corresponding to all safety mechanisms to be tested; and S5, generating all fault injection test scripts of the selected safety module to be tested by using the fault model and the test script template file corresponding to the safety mechanism. The invention has the beneficial effects that: the invention is based on the requirements of the functional safety testing process, greatly shortens the time of functional safety testing of the same type of chips by establishing the chip safety mechanism library, the functional safety testing case library, the fault injection testing script library and the failure mode library, considers the method applied in the functional safety testing process and provides the method for deriving the safety mechanism diagnosis coverage rate.
Description
Technical Field
The invention belongs to the field of ASIL (automatic test of automobile functional safety) grade testing, and particularly relates to a testing flow method of application software based on a functional safety chip.
Background
With the rapid development of intelligent networked automobiles and automatically driven automobiles, automobile electronic systems with high reliability and safety are increasingly concerned by all parties, and a safety mechanism realized by application software is of great importance in order to ensure the safety of the automobile electronic systems. In the functional safety standard GBT 34590 for automobiles, the diagnostic coverage of safety mechanisms is required to be different for different functional safety ASIL levels, and the safety mechanisms with high diagnostic coverage are required to cover failure modes for elements assigned to functional safety ASILC or ASILC levels. When the elements fail, the control chip detects the failure, but the application software does not execute corresponding safety behaviors, and the failure can influence the safe driving of the whole vehicle and even harm the personal safety. Therefore, testing of the application software is necessary to verify the correct configuration and implementation of the application software. The invention mainly aims at a test flow method of application software, a functional safety test flow for detecting the behavior of the application software by applying virtual prototype test equipment and forming failure through fault injection test scripts, and a method for determining the diagnostic coverage rate of a safety mechanism. The invention introduces the functional safety test concept and provides essential support for the reliability and safety of the automotive electronic application software.
Disclosure of Invention
In view of the above, the present invention is directed to a method for testing functional safety, so as to solve the above-mentioned problems.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
a test method based on functional safety comprises the following steps:
s1, inputting the security module to be tested;
s2, searching a chip security mechanism library and a functional security test case library;
s3, selecting all safety mechanisms and test case tables of the safety modules to be tested;
s4, determining fault models and failure modes corresponding to all safety mechanisms to be tested;
s5, generating all fault injection test scripts of the selected safety module to be tested by using the fault model and the test script template file corresponding to the safety mechanism;
s6, importing the application software to be tested and the fault injection test script into a virtual prototype test platform for testing;
s7, capturing the application software behavior after fault injection, and recording the passing and failing safety mechanisms and the corresponding failure modes of the test;
s8, analyzing the test result, comparing the failure mode corresponding to the safety mechanism passing the test with the failure mode library, and determining the diagnosis coverage rate of the safety mechanism;
and S9, generating a test report, wherein the test report comprises the test passing/failing condition, the safety mechanism diagnosis coverage rate and the fault response time interval.
Further, the security module to be tested in step S1 includes all security modules corresponding to the application software that implement the relevant security mechanisms according to the determined ASIL level, and the security module to be tested is tested and verified to meet the functional security requirements.
Further, the chip security mechanism library described in step S2 is the sum of all security mechanisms implemented by the selected chip, and is derived from the chip security manual;
the functional safety test case library is the sum of functional safety test case tables corresponding to all safety mechanisms realized by the selected chip.
Further, the test case table in step S3 includes a security mechanism number, a function module, a test purpose, a function description, a failure mode, a case number, a test item, an operation step/test data, an expected result, a software implementation security mechanism behavior, and a determination result.
Further, the fault model described in step S4, which is represented by a failure mode caused by a fault, is to create a fault injection test script and determine fault models corresponding to all safety mechanisms to be tested, where the fault models include an open-circuit fault, a stuck-at fault, a bridge fault, a single-event upset, and a unit inversion;
the failure mode described in step S4 is the failure mode of the element or related item, and the failure mode of the element or related item refers to the functional safety standard GBT 34590.
Further, the fault injection test script described in step S5 is written in Python language, and the test script covers fault models corresponding to the security mechanisms of all the security modules to be tested.
Further, the application software to be tested in step S6 selects the security mechanism of the corresponding security module according to the different levels of the functional security ASILA, ASILB, ASILC, and ASILD to implement the software code.
Further, the application software behavior described in step S7, the action taken by the application software after the occurrence of the detected fault, indicates that the test passes when the application software has an expected action behavior at the fault injection point, otherwise, the test fails, and records the test result, and the application software behavior includes reset, interrupt, and alarm.
Further, in step S8, the failure mode corresponding to the security mechanism may be one security mechanism corresponding to a plurality of failure modes, or may be all failure modes in which a plurality of security mechanisms cover one element;
the coverage rate of the safety mechanism is an evaluation mode of the safety mechanism on the coverage degree of the failure mode.
Further, the evaluation method of the coverage rate of the security mechanism is as follows:
a1, judging whether the fault type passing the test belongs to a failure mode library, recording the fault type which does not belong to the failure mode library, classifying the failure modes if the fault type passing the test belongs to the failure mode library, wherein the types comprise a low coverage rate failure mode, a medium coverage rate failure mode and a high coverage rate failure mode, and recording each failure mode of the corresponding type;
a2, evaluating safety mechanism diagnosis coverage rate, wherein the high coverage rate failure mode comprises a low coverage rate failure mode and a medium coverage rate failure mode, the medium coverage rate failure mode comprises a low coverage rate failure mode, and if the recorded failure mode is equal to the high coverage rate failure mode, the safety mechanism coverage rate can reach 99%; if the recorded failure mode is equal to the medium coverage rate failure mode, the coverage rate of the safety mechanism can reach 90 percent; if the recorded failure mode is equal to the low coverage failure mode, the coverage rate of the safety mechanism can reach 60 percent; if the recorded failure modes are not in the three ranges, the coverage rates are other coverage rates;
a3, the other coverage determination methods are as follows: if the recorded failure mode is more than the low coverage rate failure mode but less than the medium coverage rate failure mode, the coverage rate of the safety mechanism is 60 percent; if more failure modes are recorded than the medium coverage failure mode, but less than the high coverage failure mode, the safety mechanism coverage is 90%.
Compared with the prior art, the test method based on functional safety has the following beneficial effects:
the invention provides a testing method and a testing device based on functional safety based on the requirements of a functional safety testing process. By establishing the chip safety mechanism library, the functional safety test case library, the fault injection test script library and the failure mode library, the time for functional safety test of chips of the same type is greatly shortened, a method applied in the functional safety test process is considered, and a safety mechanism diagnosis coverage rate derivation method is provided. The invention provides essential support for solving ECU level functional safety test, including the guidance of test flow and technical method, and also provides reference basis for failure rate calculation and functional safety ASIL grade evaluation in the functional safety hardware development stage.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate an embodiment of the invention and, together with the description, serve to explain the invention and not to limit the invention. In the drawings:
FIG. 1 is a schematic diagram of a security mechanism library of a PMS module according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a test case table of the PMS module according to an embodiment of the present invention;
FIG. 3 is a functional security based test method of the present invention;
FIG. 4 is a security mechanism diagnostic coverage evaluation strategy of the present invention.
Detailed Description
It should be noted that the embodiments and features of the embodiments may be combined with each other without conflict.
The present invention will be described in detail below with reference to the embodiments with reference to the attached drawings.
In this embodiment, the PMS module security mechanism library includes 22 security mechanisms, as shown in fig. 1. The test was performed for the failure modes corresponding to the safety mechanisms SM8 and SM18, i.e., the failure modes were a high threshold (overvoltage) where the output voltage is above a prescribed range and a low threshold (undervoltage) where the output voltage is below the prescribed range. The PMS module functional security test case representation is shown in fig. 2, for example. The test content comprises a VEXT overvoltage test and a VEXT undervoltage test, and after a fault occurs, alarm information is generated, and application software resets the Core0 and starts the Core1-Core5 in a power-down state.
The following is a specific process:
step 3, selecting all safety mechanisms and test case tables of the PMS module;
and 4, determining fault models and failure modes corresponding to all safety mechanisms to be tested of the PMS module, wherein the safety mechanisms to be tested of the PMS module are determined to be a VEXT power supply safety monitoring mechanism, and the serial numbers of the safety mechanisms are SM [ HW ]: PMS: VEXT _ MONITOR and SMC [ SW ]: PMS: Vx _ MONITOR _ CFG. The injected fault model is that a given VEXT is greater than 5V and a given VEXT is less than 2.97V, or that a fault is injected by a given SM Flag ALM9[3] and SM Flag ALM9[5 ]. The failure modes are a high threshold (overvoltage) where the VEXT output voltage is above a specified range and a low threshold (undervoltage) where the VEXT output voltage is below a specified range.
And 5, generating a fault injection test script of the PMS module, and generating the fault injection test script by using a Python language according to the fault model and the test script template file in the step 4).
Step 6, importing the application software for realizing the VEXT power supply safety monitoring mechanism and the fault injection test script into a virtual prototype test platform for testing;
and 7, capturing the application software behavior after fault injection, resetting the Core0 and starting the Core1-Core5 in a power-down state by the application software of the example, judging that the test is passed if the expected behavior action of the application software at the fault injection point occurs, and otherwise, judging that the test is not passed and recording the test result.
Step 8, after the test is passed, recording failure modes corresponding to the test items, and if the injection fault type belongs to a PMS failure mode library, classifying the failure modes by the failure mode library; and if the injection fault type does not belong to the PMS failure mode library, recording the fault type. The failure modes of the PMS module in this embodiment include a high threshold (overvoltage) where the output voltage is above a prescribed range, a low threshold (undervoltage) where the output voltage is below a prescribed range, an output voltage affected by a spike (power spike), an output voltage accuracy that is too low (drift), and an output voltage that oscillates within a prescribed range (oscillation). Wherein the low coverage failure modes include over-voltage and under-voltage; medium coverage failure modes include overvoltage, undervoltage and drift; high coverage failure modes include over-voltage, under-voltage, drift, oscillation, and power supply spikes. Failure modes of the VEXT overvoltage test item and the VEXT undervoltage test item in the embodiment are classified into failure mode libraries, SC _ PMS _001 and SC _ PMS _002 belong to a low coverage failure mode, a medium coverage failure mode and a high coverage failure mode at the same time, and the failure modes are recorded. Comparing the failure modes recorded in the embodiment, and determining that the recorded failure modes are equal to the low coverage failure mode, the coverage of the VEXT power supply safety monitoring mechanism in the embodiment can reach 60%.
And 9, generating a test report by the PMS module, wherein the VEXT overvoltage test item and the VEXT undervoltage test item of the embodiment pass the test, and the diagnostic coverage rate of the VEXT power safety monitoring mechanism is 60%.
In summary, the invention provides a testing method and device based on functional safety based on the requirement of functional safety testing process. On the basis of ensuring the integrity of the functional safety test flow, a method applied in the functional safety test process is considered at the same time, and a safety mechanism diagnosis coverage rate deriving method is provided.
Those of ordinary skill in the art will appreciate that the elements and method steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of clearly illustrating the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
In the several embodiments provided in the present application, it should be understood that the disclosed method and system may be implemented in other ways. For example, the above described division of elements is merely a logical division, and other divisions may be realized, for example, multiple elements or components may be combined or integrated into another system, or some features may be omitted, or not executed. The units may or may not be physically separate, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment of the present invention.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; such modifications and substitutions do not depart from the spirit and scope of the present invention, and they should be construed as being included in the following claims and description.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (9)
1. A test method based on functional safety is characterized by comprising the following steps:
s1, inputting the security module to be tested into the test system;
s2, searching all safety mechanism libraries and all functional safety test case libraries in the test chip;
s3, selecting all safety mechanisms and test case tables related to the safety module to be tested from all safety mechanism libraries and all functional safety test case libraries;
s4, setting corresponding test fault models for all safety mechanisms to be tested, and setting corresponding failure modes;
s5, generating all fault injection test scripts of the selected safety module to be tested according to the test fault model and the test script template file corresponding to the safety mechanism;
s6, importing the application software to be tested for realizing the safety module to be tested and all fault injection test scripts of the safety module to be tested into a virtual prototype test platform for testing;
s7, capturing the behavior of the application software to be tested after the fault is injected into the virtual prototype test platform, and recording the passing and failing safety mechanisms and the corresponding failure modes of the test;
s8, analyzing the test result, comparing the failure mode corresponding to the safety mechanism passing the test with the failure mode library, and determining the diagnosis coverage rate of the safety mechanism;
s9, generating a test report, including a test passing/failing condition, a safety mechanism diagnosis coverage rate and a fault response time interval;
in step S8, the method for determining the safety mechanism diagnostic coverage rate is as follows:
the evaluation method of the safety mechanism diagnosis coverage rate comprises the following steps:
a1, judging whether the fault type passing the test belongs to a failure mode library, recording the fault type which does not belong to the failure mode library, classifying the failure modes if the fault type passing the test belongs to the failure mode library, wherein the types comprise a low coverage rate failure mode, a medium coverage rate failure mode and a high coverage rate failure mode, and recording each failure mode of the corresponding type;
a2, evaluating safety mechanism diagnosis coverage rate, wherein the high coverage rate failure mode comprises a low coverage rate failure mode and a medium coverage rate failure mode, the medium coverage rate failure mode comprises a low coverage rate failure mode, and if the recorded failure mode is equal to the high coverage rate failure mode, the safety mechanism diagnosis coverage rate can reach 99%; if the recorded failure mode is equal to the medium coverage rate failure mode, the diagnostic coverage rate of the safety mechanism can reach 90 percent; if the recorded failure mode is equal to the low coverage failure mode, the safety mechanism diagnosis coverage rate can reach 60%; if the recorded failure modes are not in the three ranges, the coverage rates are other coverage rates;
a3, the other coverage determination methods are as follows: if the recorded failure mode is more than the low coverage rate failure mode but less than the medium coverage rate failure mode, the diagnostic coverage rate of the safety mechanism is determined to be 60 percent; if more failure modes are recorded than the medium coverage failure mode, but less than the high coverage failure mode, the safety mechanism diagnostic coverage is given as 90%.
2. The functional safety-based testing method according to claim 1, wherein: in step S1, the security module to be tested includes all security modules corresponding to the application software to be tested, which implement the relevant security mechanisms according to the determined ASIL level, and the implemented application software to be tested tests and verifies whether the security module to be tested meets the functional security requirements.
3. The functional safety-based testing method according to claim 1, wherein: in step S2, the chip security mechanism library is the sum of all security mechanisms implemented by the selected chip and derived from the chip security manual;
the functional safety test case library is the sum of functional safety test case tables corresponding to all safety mechanisms realized by the selected chip.
4. The functional safety-based testing method according to claim 1, wherein: in step S3, the test case table includes the security mechanism number, the function module, the test purpose, the function description, the failure mode, the case number, the test item, the operation step/test data, the expected result, the software-implemented security mechanism behavior, and the determination result.
5. The functional safety-based testing method according to claim 1, wherein: in step S4, the fault model is generated according to the possible faults, and the fault models corresponding to all the safety mechanisms to be tested are determined, and then all the fault injection test scripts are created according to the fault models and the fault injection test script template file, wherein the fault models include open-circuit faults, stuck faults, bridging faults, single event upset and unit reversal;
the failure modes described in the step S4 include element failure or related item failure, and the element failure or related item failure refers to the functional safety standard GBT 34590.
6. The functional safety-based testing method according to claim 1, wherein: in step S5, a test script is injected into the fault, and written in Python language, where the test script covers the fault models corresponding to the security mechanisms of all the security modules to be tested.
7. The functional safety-based testing method according to claim 1, wherein: in step S6, the application software to be tested is implemented by selecting the security mechanism of the corresponding security module according to the different levels of the functional security ASILA, ASILB, ASILC, and ASILD.
8. The functional safety-based testing method according to claim 1, wherein: in step S7, the behavior of the application software, the actions the application software takes after detecting the fault, when the application software has the expected behavior at the fault injection point, it indicates that the test passes, otherwise, the test fails, and records the test result, and the behavior of the application software includes reset, interrupt and alarm.
9. The functional safety-based testing method according to claim 1, wherein: in step S8, the security mechanism corresponds to a failure mode, where the failure mode is that one security mechanism corresponds to multiple failure modes, or that multiple security mechanisms cover all failure modes of one element;
the safety mechanism diagnosis coverage rate is an evaluation mode of the safety mechanism on the coverage degree of the failure mode.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110682645.8A CN113535547B (en) | 2021-06-18 | 2021-06-18 | Test method based on functional safety |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110682645.8A CN113535547B (en) | 2021-06-18 | 2021-06-18 | Test method based on functional safety |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113535547A CN113535547A (en) | 2021-10-22 |
| CN113535547B true CN113535547B (en) | 2022-08-02 |
Family
ID=78125256
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110682645.8A Active CN113535547B (en) | 2021-06-18 | 2021-06-18 | Test method based on functional safety |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113535547B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111381578A (en) * | 2018-12-29 | 2020-07-07 | 长城汽车股份有限公司 | Vehicle control unit operation method and system and electronic control unit |
| CN112181800A (en) * | 2019-07-05 | 2021-01-05 | 现代自动车株式会社 | Vehicle function testing device and control method thereof |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE102016220670A1 (en) * | 2015-11-06 | 2017-05-11 | Ford Global Technologies, Llc | Method and system for testing software for autonomous vehicles |
| US10983897B2 (en) * | 2018-01-30 | 2021-04-20 | International Business Machines Corporation | Testing embedded systems and application using hardware-in-the-loop as a service (HILAAS) |
| CN108595340B (en) * | 2018-05-11 | 2021-06-08 | 重庆大学 | Automatic generation method for test scene of automobile active safety system |
| CN109240277B (en) * | 2018-11-13 | 2021-02-26 | 重庆长安新能源汽车科技有限公司 | Control system diagnosis function real vehicle test automation platform and test method |
| US10866885B2 (en) * | 2019-03-29 | 2020-12-15 | Intel Corporation | Programmatically generating software test libraries for functional safety |
| CN112684423B (en) * | 2020-12-30 | 2024-08-23 | 东风汽车有限公司 | Automatic driving function test system and test method |
-
2021
- 2021-06-18 CN CN202110682645.8A patent/CN113535547B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111381578A (en) * | 2018-12-29 | 2020-07-07 | 长城汽车股份有限公司 | Vehicle control unit operation method and system and electronic control unit |
| CN112181800A (en) * | 2019-07-05 | 2021-01-05 | 现代自动车株式会社 | Vehicle function testing device and control method thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113535547A (en) | 2021-10-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8543286B2 (en) | Vehicle hardware integrity analysis systems and methods | |
| US10495691B2 (en) | System architecture method and apparatus for adaptive hardware fault detection with hardware metrics subsystem | |
| US7168009B2 (en) | Method and system for identifying errors in computer software | |
| US4829520A (en) | In-place diagnosable electronic circuit board | |
| US9898379B2 (en) | Method for measuring the effect of microscopic hardware faults in high-complexity applications implemented in a hardware electronic system, and corresponding system and computer program product | |
| CN112326070B (en) | Temperature sensor fault diagnosis method and device, electronic equipment and storage medium | |
| US8482307B2 (en) | Method and apparatus for the prevention of untested or improperly tested printed circuit boards from being used in a fire pump control system | |
| CN113535547B (en) | Test method based on functional safety | |
| CN105653455A (en) | Program vulnerability detection method and detection system | |
| CN111552584B (en) | Testing system, method and device for satellite primary fault diagnosis isolation and recovery function | |
| Walter | Evaluation and design of an ultra-reliable distributed architecture for fault tolerance | |
| Steimann et al. | A simple coverage-based locator for multiple faults | |
| Yang et al. | The effect of time-between-events for sequence interaction testing of a real-time system | |
| CN115470132A (en) | Test method, device, equipment and medium for automatic driving data recording system | |
| CN114879647A (en) | ECU fault code test system, electronic controller and car | |
| JPH09185519A (en) | Debugging device for ic test program | |
| CN105335177A (en) | Test method, test device and test system of embedded system | |
| Lim et al. | Efficient testing of self-adaptive behaviors in collective adaptive systems | |
| Yeon et al. | Fault detection and diagnostic coverage for the domain control units of vehicle E/E systems on functional safety | |
| KR101584717B1 (en) | Method and Apparatus for testing software fail processing module mounted on embeded system for aerial Vehicle | |
| Peti et al. | A quantitative study on automatic validation of the diagnostic services of Electronic Control Units | |
| CN116779012A (en) | Chip functional safety ASIL grade assessment method | |
| Sini et al. | Towards an automatic approach for hardware verification according to ISO 26262 functional safety standard | |
| CN117664598A (en) | Software and hardware testing method for automobile function safety | |
| US20220067238A1 (en) | Computer-implemented method and computerized device for testing a technical system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |