IoT firmware audit
Context & problem
An existing IoT product needed new features while several reliability and architectural issues remained unclear. Changing the firmware directly risked making the existing code more complex and introducing further behaviour that would be difficult to control.
Challenge & solution
A focused firmware audit: analysing the existing architecture, mapping the main functions, identifying risks, comparing requirements with the existing code and prioritising actions. Particular attention was paid to wireless communication, dependencies between functions and the product's overall operating cycle.
Outcome
A clearer understanding of the existing codebase, identified key risks and a prioritised action plan, enabling the team to resume development with a better-defined scope.
Is your firmware difficult to maintain and evolve?
Let's spend 30 minutes discussing your existing system: its context, the difficulties you face and some initial options. A simple conversation with no obligation.