Firmware Flashing
Firmware flashing is programming the board's software into the microcontroller's memory on the production line and recording its version. Flashing is mostly done via the programming header on the board or through the production test fixture, and at the end the version is read back and verified.
Carrying out this step with discipline in production directly determines the quality of support in the field.
- Version record: which software version was loaded onto which serial-numbered board is recorded. Without this record it cannot be known which version a field problem affects.
- Verification: after flashing, the memory is read back or the checksum value is compared; one does not settle for the assumption that "it was loaded".
- Protection: at the end of production, read protection is enabled to make it harder to copy the software off the board.
- Factory parameters: together with the software, default settings and, if needed, calibration values are written into non-volatile memory.
The flashing step comes before the functional test, because testing the board already requires the software to be running. In some production flows a simple production software is loaded first and the tests are carried out, and at the end the final software version is programmed; this approach allows the hardware to be driven in more detail during testing.
The context in which this term is used: Our Services