Workshops: Agentic Coding by Tech Stack

Embedded C/C++ & Firmware with AI Agents: Workshop

Firmware leaves little room for error: tight memory, real-time constraints, hardware that behaves differently from the datasheet and coding standards such as MISRA. Coding agents can still save embedded teams a lot of time, as long as they work inside a strict feedback loop of compilers, static analysis and tests. This workshop shows how to build that loop and where the agent's knowledge ends at the hardware boundary.

Who is this workshop for?

  • Embedded software engineers writing C and C++ for microcontrollers
  • Firmware leads responsible for coding standards and reviews
  • Teams working with an RTOS such as Zephyr or FreeRTOS, or on bare metal
  • Test engineers for unit, integration and hardware-in-the-loop tests
  • Quality and safety engineers who need to assess AI-assisted development

What you will take away

  • Connect agents to your cross-compiler and build system, with warnings as errors as non-negotiable feedback.
  • Have agents write code against MISRA or CERT rules and use static analysis results to correct it.
  • Build host-based unit tests with mocks for hardware abstractions so the agent can test without a board.
  • Use datasheets, reference manuals and register descriptions as context instead of trusting the agent's memory.
  • Define which tasks the agent may take on and how AI-assisted changes are documented in safety-relevant processes.

Agenda

  1. Module 1

    Agents in embedded projects

    • Claude Code, GitHub Copilot, Cursor and OpenAI Codex with cross-toolchains and CMake
    • Rules for memory, interrupts, volatile and dynamic allocation
    • Typical agent mistakes in C and C++ firmware
  2. Module 2

    Standards and static analysis

    • MISRA C, MISRA C++ and CERT as agent guidelines
    • clang-tidy, cppcheck and your commercial analyser as a feedback loop
    • Handling deviations and their justification
  3. Module 3

    Testing without hardware

    • Exercise: a driver behind a HAL interface with host-based unit tests
    • Frameworks such as Unity, CMock or GoogleTest
    • Emulation with QEMU or Renode where it fits
  4. Module 4

    At the hardware boundary

    • Datasheets and register descriptions as context
    • Interpreting logic analyser traces and HIL logs with the agent
    • What must be verified on real hardware
  5. Module 5

    Process and safety

    • Traceability from requirement to code and test
    • AI assistance under IEC 61508, ISO 26262 or IEC 62304: what auditors ask
    • Review rules for timing-critical and safety-related code

The hardware boundary

An agent cannot see your board. It does not notice when a peripheral needs an extra clock cycle, when an erratum applies or when a pin is wired differently than the schematic suggests. Everything it knows about your hardware comes from the context you give it and the tests it can run.

That is why we keep agents where feedback is fast and deterministic: compilation, static analysis, host-based tests and emulation. Results from real hardware flow back as logs and measurements and are interpreted together with an engineer.

Safety-relevant software

In functional safety, AI coding tools are generally not qualified tools, and generated code gets no shortcut through your verification process. We show how teams document AI assistance, keep traceability intact and focus reviews where the risk is highest. We explain what standards such as IEC 61508, ISO 26262 and IEC 62304 require of your process; the formal assessment stays with your safety and quality organisation.

Source code confidentiality

Firmware is often core intellectual property. If code must not leave the company, we work with sandbox repositories or discuss self-hosted models and their quality trade-offs. The workshop runs remotely or on-site, in English or German, with neooutput AI Code Engineers; jocapps, the company behind neooutput, is ISO 27001 certified.

Frequently asked questions

Can agents write MISRA-compliant code?

They follow many rules if you state them clearly and run a static analyser on every change. Compliance is demonstrated by your analysis tool and review, not by the agent's claim.

Is the workshop useful for embedded Linux?

Partly. The focus is on microcontroller firmware and RTOS-based systems. Build systems, static analysis and testing apply to embedded Linux as well, and we can shift the emphasis on request.

Is the workshop industry-specific?

No. It covers firmware engineering practice that applies equally in industrial automation, consumer electronics, medical devices and automotive. For industry-specific process requirements we offer separate formats.

Workshop

Get in touch

Want agents to speed up your firmware work without compromising on safety?

Tell us roughly how many people will join and pick dates that work – we will get back to you within 24 hours with a proposal for content, format and schedule.

Prefer to talk first?

15 minutes, free and without obligation – with our AI Trainers and AI Code Engineers.

Book a call for free (opens in new tab) +49 761 519 751 50 (24/7)

Request a training / workshop

Workshop: Embedded C/C++ & Firmware with AI Agents: Workshop · 1 day

Dates that work for you (optional)

Suggestions about 2 weeks ahead – pick as many as you like

Reply usually within 24 hours · jocapps is ISO 27001 certified · Privacy