Programming before assembly removes a production step, protects your firmware and gives you a board that is ready for functional test when it comes off the line.
Programming options
| Parameter | Capability |
|---|---|
| Pre-programming | Device programmed before placement, with verification |
| In-circuit programming | Programming through the assembly test fixture |
| Serialisation | Unique IDs, MAC addresses or keys written and logged |
| Firmware control | Version, checksum and file revision recorded per build |
| Verification | Read-back and checksum comparison after programming |
| Labelling | Serial or version labels applied to the board or bag |
What we need from you
- Firmware imageHex, bin or vendor project file, plus the exact version to use.
- Programming specificationDevice, interface, security settings and read-back requirements.
- Serialisation rulesFormat, starting number, allocation and logging expectations.
- Test coverageWhat the board should do after programming so we can verify it.
Treat firmware as a controlled build input. Send the image and revision with the purchase order, and we will archive it with the build record.
Frequently asked questions
Can you program parts for a consigned assembly?
Yes. We can program before placement or through the test fixture, depending on the package and access.
Do you keep firmware confidential?
Yes. Firmware is treated as customer confidential information and stored with access limited to the programming team.
Can you program after the board is assembled?
Yes, if the device is accessible and the interface is brought out to a header or test pads.