Help understanding assertion in secure serial DFU

RE: Help understanding assertion in secure serial DFU

Amanda Hsieh — Thu, 18 Mar 2021 06:58:58 GMT

Hi Andres,

Happy to know you fix the issue. Yes, please create a new support case for another issue.

-Amanda H.

RE: Help understanding assertion in secure serial DFU

Andres — Wed, 17 Mar 2021 21:51:25 GMT

Hi Amanda,

I figured out the source of one problem: I needed to remove the NRF52 define in the Keil's "Options for Target-C/C++" tab

It was loading an include file for the nRF52832 instead of the corresponding include for the nRF52833. This last chip is the one I am using and it has two GPIO ports, P0 and P1. My custom board is using P1.03 for the reset button. And only with the correct include file, the P1 pins can be used.

I do have another problem still, but I think it is better that I open a new ticket for it.

Thank you.

RE: Help understanding assertion in secure serial DFU

Amanda Hsieh — Tue, 16 Mar 2021 13:56:01 GMT

Hi Andres,

Is the secure DFU Bootloader over UART or USB? Does your board connect with UART or USB?

If you define DEBUG in your preprocessor definitions, the app_error_handler() will be called instead of the app_error_handler_bare() in main.c whenever an APP_ERROR_CHECK(err_code) receives an err_code != 0. If you need more information, you can look at the __WEAK implementation of app_error_fault_handler() in app_error_weak.c to print more information.

-Amanda H.