nRF52 Hardfault implementation doubts

RE: nRF52 Hardfault implementation doubts

Susheel Nuguru — Tue, 23 Jun 2020 10:52:35 GMT

Hi Dave,

[quote user="davege"][/quote]

is there any good summary of what and how those switches enable when they are defined? I think it would be very useful to engineers during development.
I'd like to understand in the code

Unfortunately, there are no document to describe them.
DEBUG_NRF is only valid for the macro ASSERT(x). If DEBUG_NRF is defined to 1, then all calls to ASSERT(x) would assert in app_error_fault_handler. This is somewhat same to APP_ERROR_CHECK (but the latter is not depending on DEBUG_NRF). There are lots of examples where WEAK implementation of app_error_fault_handler has been overridden in the main.c to let the application handle errors as they suit them.

[quote user="davege"]I'd like to understand in the code where p_stack is set to NULL in the code...? Is it in the assembly function implementing the low level HardFault_Handler?[/quote]

Yes, you are right, there is a low-level implementation of the HardFault exception. Please take a look in SDK_17.0.0_9d13099\components\libraries\hardfault\nrf52\handler\hardfault_handler_gcc.c to understand how p_stack value is pushed as argument. If you are using different compiler, then please look into the relevant implementation in the given path.

RE: nRF52 Hardfault implementation doubts

davege — Sun, 21 Jun 2020 15:26:43 GMT

Hi Susheel.

Thanks for your reply.

So coming back to my first request:

is there any good summary of what and how those switches enable when they are defined? I think it would be very useful to engineers during development.
I'd like to understand in the code where p_stack is set to NULL in the code...? Is it in the assembly function implementing the low level HardFault_Handler?

Thanks!

RE: nRF52 Hardfault implementation doubts

Susheel Nuguru — Thu, 18 Jun 2020 12:41:15 GMT

[quote user=""]What's the difference between DEBUG and DEBUG_NRF[/quote]

You seems to be right, the initial idea was to keep DEBUG_NRF for NRF libraries and drivers related debug capabilities, like asserts etc. And DEBUG was supposed to be for common assert handling. But unfortunately, it looks like this two are merging in logical use.