Enabling Logs Causes DFU To Fail

[aa]

Hi,

I'm working on a bootloader based on the "secure_bootloader/pca10056_ble" example. Everything works fine until I send the new application binaries (.zip file) and the chip resets:

...

<debug> nrf_dfu_flash: Flash write success: addr=0x000FE000, pending 0

<debug> app: Resetting bootloader.

<info> nrf_dfu_settings: Backing up settings page to address 0xFE000.

<debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.

<info> app: Inside BL main?

After a lot of debugging I noticed that if I disable NRF_LOG_ENABLED, the updated app starts correctly.

Also, just by adding NRF_LOG_FLUSH() in nrf_bootloader_app_start.c right before the interrupts are disabled, the app also starts OK without having to disable the logs.

The NRF_LOG_DEFAULT_LEVEL is currently set to 4.

Is there any known reason for this behaviour?

Thanks.

[Edvin]

Hello,

What changes did you do to the bootloader project to make it compile with logging enabled in sdk_config.h? Or do you use the pca10056_ble_debug project?

Best regards,
Edvin