Loading Firmware during Manufacturing

[arif_tahmo]

We have an old product that uses NRF52832 and we're building new units. Some of the documentations are not clear and I have the following question:

What files do we need to load the firmware onto the chip before manufacturing? 

These are the files we have:

• manifest.json  (1Kb)
• nrf52832_xxaa.bin  (53Kb)
• nrf52832_xxaa.dat   (1Kb)

And what is the order, if any? 

I am not sure what the manufacturer is using to burn the firmware. 

Thanks for your help. 

[Vidar Berg]

Hello,

For production you will usually have one or more *.hex files which contain the FW image(s) for the device. But the files you listed are from a DFU update package and will not include all the data needed for the initial programming of the device, unfortunately.

DFU packages are made to be distributed to end users to allow them to update FW on the device over Bluetooth or Serial (USB/UART), but not for programming in production.

What files do we need to load the firmware onto the chip before manufacturing? 

I am not sure what the manufacturer is using to burn the firmware. 

If the manufacturer is already doing the programming of your FW in production, is it necessary to do any pre-programming? 

Best regards,

Vidar