Process detail

  1. STAGE INPUT
  2. Programming setup

    Fixture wired, debug interface (SWD, JTAG, UART, USB-DFU) confirmed.

  3. Multi-image load

    Bootloader, application, file system, and manufacturing partition written in sequence.

  4. Provisioning

    Secure element key injection, X.509 enrollment, eFuse or OTP burn.

  5. Serial assignment

    MAC, UID, or unique serial assigned and written to device.

  6. Label application

    GS1 DataMatrix or QR label with serial, batch, manufacturing date.

  7. Traceability log

    Per-unit firmware hash, serial, provisioning timestamp committed to database.

  8. STAGE OUTPUT

Files we accept

  • Firmware binary (hex, bin, signed image)
  • Provisioning template
  • Label artwork
  • PKI root certificate (if custom)

Tolerances and specs

Interfaces
SWD, JTAG, UART, USB-DFU
Identity options
MAC (IEEE OUI), UID, EUI-64, custom serial
Label encoding
GS1 DataMatrix, QR (ISO/IEC 15415)

Frequently asked questions

Can you load and provision firmware in production?

Yes. In-line firmware loading during functional test and offline programming via dedicated fixtures. We support SWD, JTAG, UART, and USB-DFU interfaces, multi-image programming (bootloader, application, file system), and signed bootloader chains.

How do you handle embedded software and secure provisioning?

We support X.509 certificate enrollment, secure-element key injection (ATECC608, NXP EdgeLock), eFuse and OTP programming, and provisioning to AWS IoT Core, Azure DPS, and custom PKI. Private keys can be HSM-generated and never exposed to host systems.

How do you serialize and label units?

Per-unit MAC, UID, and serial number assignment with GS1 DataMatrix or QR labels. Polyimide or polyester label stock based on environmental requirements. Every label is logged against board lot, firmware hash, and test result for full traceability.

Discuss this capability

Share your BOM, gerbers, and CPL. Engineering reviews fit, throughput, and DFM, and replies within one business day.