Firmware code review
Flagship offering for teams shipping bare-metal or lightly abstracted C on ARM, RISC-V, or legacy 8/16-bit parts.
Who it is for
Engineering leads who need an independent pass before factory programming, certification evidence, or a field trial. Typical clients have one to four firmware engineers and a hardware team in the same time zone or within a few hours of SAST.
Result you receive
A findings package your team can triage in a single sprint planning session: severity-ranked issues, file references, suggested test ideas, and a one-hour readout call with the assigned reviewer.
Scope
Included: designated Git directories at a tagged commit; peripheral drivers; interrupt and DMA paths; static memory map assumptions; unit-test gaps that affect safety monitors; coding patterns that conflict with your stated MISRA or CERT subset.
Excluded: cloud backends, mobile apps, mechanical drawings, and penetration testing of network services. We do not rewrite modules—we document what should change.
Provider & process
Thabo or Lindiwe leads depending on motor-control versus communications weight. After deposit and NDA, reviewers clone read-only, work through a checklist derived from your hazard analysis (if provided), and deliver PDF plus spreadsheet within the agreed window—usually five to eight business days for a medium tree.
Preparation
Send a one-page architecture note, linker script, and list of known flaky tests. Point us to the commit you intend to ship. Redact customer PII from logs you attach.
Constraints
We review source and build scripts you supply; we do not guarantee compliance with any standard unless explicitly scoped. Hardware-in-the-loop traces help but are optional.
Pricing basis
Quoted in ZAR from reviewer-day estimates on rates. Full-tree engagements start around R 62 000; focused modules from R 28 500.