Tagged fault-injection
3 pieces
- · 10 min read
Plant the Faults So the Harness Proves It Can See Them
A harness that has never detected a known fault has not been shown to detect anything. Injecting deliberate, known faults is the step that converts a green suite into a suite that can fail for the right reasons. This covers the fault classes worth planting in an extraction or retrieval pipeline, how each one should present, and why a planted fault is the positive half of a pair whose other half is the negative control.
- · 5 min read
ISO 26262 Mandates Fault Injection at ASIL D
Branch coverage is highly recommended at ASIL B, C and D; MC/DC and fault injection become highly recommended at ASIL D. The hardware side permits only about 1 percent residual single point faults at ASIL D, assessed through fault injection campaigns. Negative control discipline, written as a requirement.
- · 5 min read
Fault Injection for Firmware: Corrupt the Sensor and Confirm It Notices
Corrupt a sensor value, force an error return, flip a bit, drop a packet, delay an interrupt, and confirm the system detects it. This is the MCAS lesson, ISO 26262 makes it highly recommended at ASIL D, and Renode and QEMU let you run the campaign without hardware.