RE: Flashing new bootloader settings along with an application.hex on top of an already existing bootloader

Sigurd — Mon, 11 Jun 2018 13:02:06 GMT

Hi,

From the blog post you linked to.

[quote]The bootloader uses its bootloader setting to detect if a valid application is flashed on the chip or not. CRC check will be performed when booting. If we simply flash the application with the bootloader using the programmer, the bootloader won't be able to detect there is a valid app already flashed and it will enter DFU mode, your application won't start.[/quote]

[quote userid="71948" url="~/f/nordic-q-a/35236/flashing-new-bootloader-settings-along-with-an-application-hex-on-top-of-an-already-existing-bootloader"]Does this mean every time I update the application I have to reflash a new merged bootloader and then a new application package?[/quote]

No, if you skip the integrity check, you don't need to do this. See this post. Also note that SDK 15 added optional skipping of application CRC check. CRC check can be skipped on wakeup from System Off or on special value written to GPREGRET2 register (when bit 1 (0-indexed) is set in the GPREGRET2 register).