Trust, but Verify: Keeping AI-Generated Embedded Code Correct, Safe and Compliant
AI assistants have moved from suggesting lines to acting on the codebase: today's agentic tools write, refactor, and run tests on their own. They can compress hours of embedded C/C++ work into minutes — but they raise an unavoidable question for any team shipping safety- or security-critical firmware: can you trust what the agent produced, and can you prove it?
This session looks at where productivity meets accountability. Starting from a realistic AI-assisted workflow, it shows how to keep verification in the loop rather than bolted on at the end: static analysis to catch defects and coding-standard violations early, runtime checking to expose errors that surface only during execution, automated testing for fast regression feedback, and MISRA/CERT compliance treated as a continuous gate. Examples use IAR's analysis and verification tooling (C-STAT, C-RUN) to make the principles concrete. For teams developing to ISO 26262, IEC 62304 or IEC 61508, the same discipline, backed by a certified compiler and the application of its functional-safety guide, is what lets AI-assisted code stand up inside a safety case.
Speaker: Dr. Marc THOMAS
Embedded Security Field Application Engineer – EMEA
IAR Systems France — A Qt Group Company