Quality Assurance
Industrial-grade firmware, proven by data
Gates only get stricter: coverage ratchet + fuzzing closed loop + dual-end cross-verification — built to run for the long haul.
Four pillars
A complete quality chain from coding to runtime
01
Industrial-grade safe coding
- Strict C89 + safety coding subset (-std=c89 -pedantic -Wall -Werror)
- One-way include direction; the contract layer must not depend on chip/RTOS
- Enforced file naming and directory conventions
02
Coverage ratchet gates
- Line 91%+ / branch 72%+ / MC-DC condition 55%+
- Baselines only rise, never fall; no gaming the baseline
- Coverage reports auto-collected and archived
03
Fuzzing closed loop
- libFuzzer + ASan across every parsing surface
- A crash requires "test case + fix + corpus commit" before the ticket can close
- Extended deep runs before release
04
Runtime reliability & security
- Global fault codes + watchdog + crash black box (with a symbolication tool)
- 1-Wire chip license token anti-clone; unauthorized = fail-closed
- SIP digest auth + SRTP media encryption
Dual-end cross-verification
The desktop simulator and target firmware share one widget catalog and protocol source (MQTT / TCP / SIP / RTP / Opus / bus codecs). Automated interop tests continuously enforce "pass simulation, match hardware".