PHASE 05 ยท FIRMWARE

Firmware.
Small, safe and ready for the field.

You arrive with a board, a prototype or a development kit. You leave with tested, documented firmware on Arm Cortex-M or RISC-V, or on an MCS-51 (8051) for small control tasks, built to be maintained and, where the hardware allows, updated safely in the field.

Henrik Andersen development loop: enter anywhere, stay as long as you need, exit anytime

At a glance.

You bring
  • A board, prototype or development kit
  • Requirements or a feature list
  • An existing code base
  • Or firmware that needs a review
I do
  • Firmware architecture
  • Drivers, RTOS and communication stacks
  • Secure boot and OTA update
  • Static analysis and tests
You get
  • Source code in your repository
  • Release builds and bootloader
  • Test results and CI setup
  • Release notes and documentation

What is included.

Ten building blocks. Take them all, or just the ones you need.

EU CYBER RESILIENCE ACT

Ready for the Cyber Resilience Act.

The EU Cyber Resilience Act (Regulation (EU) 2024/2847) sets cybersecurity requirements for products with digital elements. Its vulnerability and incident reporting obligations apply from 11 September 2026; the essential requirements and CE marking under the Act apply from 11 December 2027. Firmware decides most of it, so I build it in from the start.

Whether and how these rules apply depends on your product. This is engineering support, not legal advice.

HOW INTEGRATION IS CHECKED

Integration and continuous integration.

Every change is built, tested and run on real hardware automatically, so incompatibilities between hardware revisions, firmware and software show up as they evolve, long before a release.

Integration and continuous integration. Top: the pipeline that runs on every change, commit, reproducible build, unit tests, hardware in the loop and integration report. Middle: an integration matrix of four builds, 118 to 121, on three hardware revisions, A to C. All combinations pass except build 120 on revision A: a sensor driver change no longer suited those boards; the hardware-in-the-loop run found it and build 121 fixed it before any release. Principles: same build everywhere, real hardware, fast feedback, no broken merges. Right: the typical outputs, reproducible builds, regression results and integration reports.

What you get.

Source code Git repository, documented
Firmware release Binaries + version history
Bootloader Secure boot, OTA update
Test report Unit and integration tests
Static analysis MISRA C findings
Developer guide Build, flash, debug
Duration

Agreed in your proposal

Enter with

A board, prototype or development kit

Exit with

Working firmware

Payment

After your approval

Where to next.

Continue with me through the next phases to start of production, or leave with what you came for.

Previous phase04 HardwareSchematic, PCB layout and hardware review. Next phase06 PrototypeWorking units, brought up, debugged and measured.

CONTACT

Ready to start at phase 05?
Or hand over the complete development? Just ask.

A new product to develop from scratch, a design that needs a second look, or a prototype that does not work yet: a few lines are enough to start.

  • A personal reply within one working day
  • No cost and no commitment up front: you only pay for work you approve
  • Your idea stays confidential, NDA on request (how I keep your project confidential)

Write to me

info@siliconmeetscode.com
Write an email

Helpful to mention: what the product does, where it is today, and your timeline. The email opens with these questions ready to fill in.

Working from Belgium and Germany with clients across Europe and Asia