RE: nRF52DK programmed and debugged ok within Segger Studio but dragging hex file to JLINK drive does not give the same result

Edvin — Wed, 21 Aug 2019 13:55:13 GMT

Hello,

The reason why the precompiled .hex file is bigger is that it contains the softdevice merged with the application.

I don't use the drag'n'drop too much, but it looks like it isn't too found of being programmed by two .hex files (softdevice and application). I am not quite sure why, but if you merge the application and the softdevice into one .hex file, it looks like it works.

To merge two .hex files, you can use mergehex, which is included in the Nordic Command Line Tools (same as nrfjprog).

To merge two files, use the command:

mergehex --merge <path to file 1> <path to file 2> --output <my_merged.hex>
For example:
mergehex --merge s132_nrf52_6.1.1_softdevice.hex ble_app_blinky_pca10040_s132.hex --output my_merged_application.hex

If the files are located in the folder from which you run your cmd line.

You should be able to drag'n'drop the file my_merged_application.hex.