Prototype works, pilot batch fails
Units pass bench tests yet fail after vibration, brown-out, or long idle periods. We correlate power sequencing, watchdog configuration, and flash wear patterns with your manufacturing notes.
Situations we are called into
New silicon, old timeline
MCU migration or second-source part landed on your roadmap with unchanged deadlines. We port drivers, validate timing on the logic analyser, and document assumptions for your internal team.
RTOS or bare-metal crossroads
Growing feature set outgrew the super-loop. We help you choose FreeRTOS, Zephyr, or stay bare-metal with a structured scheduler—matched to your certification path and RAM budget.
Flagship engagement
Our Firmware Stabilisation Engagement is a fixed-scope rescue for teams with a defined symptom—reset loops, communication drop-outs, ADC noise, or OTA failures—and a hardware revision we can access on the bench or via your J-Link in Gqeberha.
Typical duration: two to six weeks. Deliverables include a written fault tree, patched firmware branches, and a handover session with your firmware engineers. Travel within the Eastern Cape is included; other provinces are quoted per visit.
Read the full scope and exclusions →Additional consulting areas
From recent engagements
They traced our Modbus timeouts to a DMA buffer alignment issue we had masked with retries. The fix was small; the write-up for our ISO auditor was the part we kept.
— Nomsa K., instrumentation lead, Port Elizabeth