Combining bootloader, softdevice, and application in single hex

RE: Combining bootloader, softdevice, and application in single hex

Dhiraj — Fri, 01 Sep 2017 02:55:24 GMT

Thanks for the reply. I followed this link: devzone.nordicsemi.com/.../

Merged the valid setting hex file to bootloader,softedevice, and application hex using merge hex tool. It worked :)

RE: Combining bootloader, softdevice, and application in single hex

Nguyen Hoan Hoang — Thu, 31 Aug 2017 12:19:53 GMT

you can find more info here http://infocenter.nordicsemi.com/index.jsp Source code of the DFU is in the SDK

RE: Combining bootloader, softdevice, and application in single hex

Jørgen Kvalvaag — Thu, 31 Aug 2017 10:40:16 GMT

app_valid_settings.hex contains information the bootloader needs to verify that the application on the chip is valid. If it is missing or incorrect, the bootloader will not find a valid app, and enter bootloader mode. The app_valid_settings.hex must be generated every time you recompile application.hex. To generate use the python tool nrfutil, which you find here: https://github.com/NordicSemiconductor/pc-nrfutil

RE: Combining bootloader, softdevice, and application in single hex

Dhiraj — Thu, 31 Aug 2017 05:02:03 GMT

Thanks for the reply. I tried the mergehex tool and srec_cat tool. In both case device doesn`t advertise. When I try to switch to dfu mode, it switches perfectly and advertise as "DFUtarg". Is the app_valid_setting.hex different for different SDK and softdevices? What exactly that hex files contains?

RE: Combining bootloader, softdevice, and application in single hex

Nguyen Hoan Hoang — Thu, 31 Aug 2017 04:00:09 GMT

if you read that thread via your link, you'll see that the tool require to merge is mergehex not srecord.