Firmware & configuration release
The right image.The right device.
Coordinate device identity, firmware revision and programmer setup for loose ICs or populated boards. Define verification before the lot is programmed.

01 / Device identity
Define the programmable device and its role.

Identify the device family first.
| Device family | Programming purpose |
|---|---|
| Microcontrollers (MCUs) | Embedded in a wide range of consumer and industrial electronics. They are programmed with firmware to control specific tasks. |
| Field Programmable Gate Arrays (FPGAs) | Configured with bitstream files to define complex logic circuits and hardware behavior. |
| Complex Programmable Logic Devices (CPLDs) | Programmed with logic equations for customizable hardware functions. |
| Flash Memories | Used to store firmware or data, which can be rewritten as needed. |
| EEPROMs | Electrically erasable programmable read-only memory for storing data with retention capabilities. |
Scroll the table to review all columns.
02 / Physical access
Choose the programming route and electrical interface.
Program on the board or before placement?
We offer two primary IC programming methods to meet different requirements in the product lifecycle: APTPCB offers both methods depending on your needs, whether you're in the development phase, production, or in-field maintenance.

Offline Programming
Match the electrical interface.
JTAG
SPI (Serial Peripheral Interface)
I2C (Inter-Integrated Circuit)
UART (Universal Asynchronous Receiver/Transmitter)
SWD (Serial Wire Debug)
Direct ISP
03 / Released state
Keep the programmed state tied to the build.
- 01
Identify
Confirm the exact device, board or loose-device lot, and approved image revision.
- 02
Configure
Review the interface, supported file and device-specific settings as one job.
- 03
Program and verify
Agree the verification method, failure handling and any additional functional test.
- 04
Retain the link
Associate the programmed configuration and result with the assembly or component lot.
04 / Firmware package
Release a file the selected device and tool can use.
Release a file the device and programmer can use.
We support various file formats necessary for programming different types of ICs. These formats ensure seamless communication between your firmware tools and the IC programmer: APTPCB ensures compatibility with these formats, allowing easy integration of your firmware with our programming systems.
| File format | Programming context |
|---|---|
| HEX Files | Contains executable code in hexadecimal format for programming memory. |
| JEDEC Files | Industry-standard format for programming flash and EEPROM memory devices. |
| SVF/STAPL Files | Used for JTAG-based programming sequences for FPGAs and microcontrollers. |
| BIT Files | Bitstream files used for configuring FPGAs and CPLDs. |
| BIX Files | Specific to Bytecraft tools, used for programming microcontrollers over JTAG. |
| IEEE 1532 Files | For programming IEEE 1149.1 compliant ICs via JTAG. |
Scroll the table to review all columns.
05 / Production setup
Confirm compatibility before choosing throughput.
Verify compatibility before throughput.
Supported ICs
Interfaces
Programming Throughput
File Format Support
Additional Functions
Software Compatibility
Choose the handling and programmer setup.
Desktop Programmers
Production Programmers
Gang Programmers
Automated Handlers
Field Programmers
In-System Programmers (ISP)
06 / Engineering handoff
Bring device, firmware and assembly requirements together.

PCB Assembly & IC Programming Services – APTPCB
Our IC Programming Services
Contact Us
Contact us today to discuss your IC programming requirements, or to learn more about how our services can optimize your production process.
ENGINEERING REFERENCE
Additional programming benefits and supplier-review notes
What the programmed image controls.
Without proper programming, ICs are just blank chips with no functionality. Programming gives them life and enables them to perform critical tasks in your devices.
Initialization and Boot-up
Defining Device Functionality
Configuration
Adaptability
Intellectual Property Protection
Inventory Flexibility
End-of-Line Production
Connect programming to the production plan.
Experienced Engineers
High-Volume Production
Flexible Solutions
Advanced Technology
Quality Control
PRACTICAL QUESTIONS
Before you release the work.
Which ICs can you program?
Do you support both ISP and offline programming?
What interfaces are available?
Can you verify every device?
How do you manage firmware files?
What should PCB assembly programming specify?
ENGINEERING & PRODUCTION REVIEW
Release a programming job for review.
Bring the device, firmware and access requirements together.
- Exact device part number and package
- Firmware/configuration file, format and revision
- Loose-device or board route and interface
- Quantity, verification method and assembly test scope