Merged Hex File

RE: Merged Hex File

Vidar Berg — Fri, 13 Nov 2020 09:19:44 GMT

Please try to debug the nrf_bootloader.c::dfu_enter_check() function inside the bootloader to find out what's causing it to enter DFU mode.

RE: Merged Hex File

Aftab — Fri, 13 Nov 2020 09:03:17 GMT

Yes, the same app.hex works with same softdevice and bootloader. The only caveat is that the device needs to be power cycled after DFU update. The application, then runs normally.

In the above case, the device remains in DFU mode no matter how many times it's power cycled.

RE: Merged Hex File

Vidar Berg — Fri, 13 Nov 2020 08:40:46 GMT

Ok, I'm not sure if the problem is related to the Settings page then. Does the application run ok if you upload it through DFU instead of programming it directly with the debugger?

RE: Merged Hex File

Aftab — Thu, 12 Nov 2020 15:18:19 GMT

Nop, this change did not work as well.

RE: Merged Hex File

Vidar Berg — Thu, 12 Nov 2020 15:05:05 GMT

Sorry, I thought you were using the 52832, not the nrf52840. The "--family" argument must be set to NRF52840 instead of NRF52 then.

RE: Merged Hex File

Aftab — Thu, 12 Nov 2020 15:01:23 GMT

The %APPHEX% is defined only once and same is used on both occasions.

I tried using NO_VALIDATION instead of VALIDATE_GENERATED_CRC.

The issue remains the same.

RE: Merged Hex File

Vidar Berg — Thu, 12 Nov 2020 13:01:36 GMT

Did you use pass the same %APPHEX% file as the one you used in the merged image? The bootloader will only boot the application image if it its computed CRC is the same as the one that is stored in the bootloader settings. You could also try to replace VALIDATE_GENERATED_CRC with NO_VALIDATION to skip the boot validation check and see if it makes any difference.

The Bootloader versioning is up to you to decide. You can start with version 1 if you want.

RE: Merged Hex File

Aftab — Thu, 12 Nov 2020 12:38:54 GMT

I tried this, created bl_settings.hex file but still the issue remains same. What should be the BL_VERSION or bootloader version value should be? I have taken the bootloader from SDk16.0 secure bootloader example.

RE: Merged Hex File

Vidar Berg — Thu, 12 Nov 2020 07:23:43 GMT

Hello,

You need to generate and merge the Bootloader settings page as well. The settings page contains the information needed by the bootloader to verify and boot the application.

Here's an example of how you can generate it with nrfutil:

 nrfutil settings generate --family NRF52^
 --application %APPHEX%^
 --application-version-string "%APP_VERSION_STRING%"^
 --bootloader-version %BL_VERSION%^
 --bl-settings-version 2^
 --app-boot-validation VALIDATE_GENERATED_CRC^
 bl_settings.hex