Merge firmware .hex with DFU Key

RE: Merge firmware .hex with DFU Key

Vidar Berg — Wed, 09 May 2018 11:06:13 GMT

Hello, the order doesn't matter when you merge hex files. Are you able to share your merged hex files so I can try it here. Alternatively, read out the cpu registers, it may give an indication on where and why it fails. You can use the --readregs option in nrfjprog for this: nrfjprog --readregs

RE: Merge firmware .hex with DFU Key

AmiguelS — Wed, 09 May 2018 10:56:57 GMT

Hello, I'm sorry for insisting on this, but I'd just like to confirm that the order App > Settings > Bootloader > Softdevice is the correct one. Although I'm able to merge all the files and flash them, there is no device boot. Not event the bootloader starts...

RE: Merge firmware .hex with DFU Key

Vidar Berg — Thu, 03 May 2018 07:24:20 GMT

Hi, documentation for the "mergehex" tool can be found here: http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.tools/dita/tools/nrf5x_command_line_tools/nrf5x_mergehex.html?cp=5_1_2. The procedure is the same regardless of toolchain.

e.g.,

mergehex -m APPLICATION.hex SETTINGS.hex BOOTLOADER.hex -o APPBL.hex // mergetool can merge 3 hex files at a time.

mergehex -m APPBL.hex SOFTDEVICE -o FINAL.hex

RE: Merge firmware .hex with DFU Key

AmiguelS — Wed, 02 May 2018 13:05:55 GMT

Hello!

Could you please clarify what procedure should be followed to merge the complete .hex (using the settings page generated from the link you mentioned)? Is the procedure the same when using gcc?

Thanks.

RE: Merge firmware .hex with DFU Key

Vidar Berg — Tue, 24 Apr 2018 13:49:35 GMT

Hi, did you check out the link I referred to? Bootloader needs to know the checksum value of the application image in order to validate it on boot, and will fall back to DFU mode if it is unable to verify it. The checksum value along with other flags are stored in the bootloader settings page.

RE: Merge firmware .hex with DFU Key

Toyman — Tue, 24 Apr 2018 07:09:23 GMT

I have exactly the same issue: I need to find a way to flash SD+Bootloader + app alltogether or at least one after another, but "by wire".

Do I understand correctly, that it's a lack of the settings page that prevents the bootloader from launching the app that was flashed and not OTA-ed?

RE: Merge firmware .hex with DFU Key

Vidar Berg — Tue, 24 Apr 2018 06:29:17 GMT

Hello,

The thread you linked to explained how to generate the settings page for the old bootloader, but this approach has changed for the new secure bootloader. Please refer to Appendix 1 in this blog post for instructions on how to generate and merge the setttings page: https://devzone.nordicsemi.com/b/blog/posts/getting-started-with-nordics-secure-dfu-bootloader