Service
Firmware Loading
Firmware loading turns an assembled board into a functioning unit. We load firmware on the line through dedicated programming fixtures, supporting multi-image programming and signed bootloader chains for security and supply-chain integrity. When the customer test plan requires functional test alongside flashing, the unit moves to a partner test house with the firmware already loaded.
What this service includes
- Firmware loading on the line through dedicated fixtures
- SWD, JTAG, UART, and USB-DFU interface support
- Multi-image: bootloader, application, file system, manufacturing partition
- Signed bootloader and secure-boot enforcement
- Per-unit firmware hash and version logged against serial
- Rollback safety: power-loss tolerant loading sequences
Production workflow for this service
- INPUT FILES
-
Firmware handoff
Binary received with version, hash, and signing key reference.
-
Fixture setup
Programming fixture wired to assembled board, debug interface confirmed.
-
Loading sequence
Bootloader first, then application, then any manufacturing partition.
-
Verification
Read-back hash compared to expected value before unit moves to test.
-
Logging
Per-unit firmware version, hash, and provisioning timestamp written to traceability database.
- OUTPUT
Right fit when
- Your product needs to ship with firmware already on the board.
- You need signed firmware enforcement to meet security requirements.
- You want every shipped unit traceable to a specific firmware version.
Frequently asked questions
Can you load and provision firmware in production?
Yes. Firmware loading runs on the line through dedicated programming fixtures. We support SWD, JTAG, UART, and USB-DFU interfaces, multi-image programming (bootloader, application, file system), and signed bootloader chains. When the customer test plan calls for functional test alongside flashing, the unit moves on to a partner test house with the firmware already loaded.
Do we need a written test plan?
Yes when functional test is in scope. A production test plan defines pass and fail criteria, FCT vectors, calibration steps, and serialization rules. We help draft one if your team has not written one yet, based on your firmware behavior and target field performance. The test plan is handed to the partner test house we coordinate with for FCT.
How do you support Cyber Resilience Act (CRA) readiness for connected devices?
Production-side CRA support includes signed firmware enforcement, per-unit serialization for SBOM tracking, secure provisioning workflows, and documented test records. Product-side CRA obligations (vulnerability handling, security updates) remain with the OEM.
Quote firmware loading
Send your BOM, gerbers, and CPL. We respond within one business day. NDA on request.