Hard fault - memset and printf

RE: Hard fault - memset and printf

Sigurd — Mon, 03 May 2021 21:07:51 GMT

[quote user=""]HARD FAULT at 0x00000000[/quote]

Is it always 0? I would have expected a valid PC value here, pointing to the code that is causing the hardfault.

Did you try turning off optimization?

I.e. in the makefile change "OPT = -O3 -g3" to "OPT = -O0 -g3".

If you are using SES, change from "Release" build to "Debug" build.

[quote user=""]and a log which is implemented with printf.[/quote]

If you are using e.g. NRF_LOG other places in your code, you should use NRF_LOG instead of printf

RE: Hard fault - memset and printf

Roei — Sat, 01 May 2021 20:15:27 GMT

Hi,

Thanks for you answer!

After disabling all logs, hard fault still occurs.

I already have hardfault_implementation.c and hardfault_handler_gcc.c in my project, and HARDFAULT_HANDLER_ENABLED set to 1.

However - DEBUG_NRF isn't defined in my project. Can you please explain how will it help?

Thanks!

RE: Hard fault - memset and printf

Sigurd — Mon, 26 Apr 2021 11:45:40 GMT

Hi,

I recommend using the nrf_log module for logging. If you use deferred mode, the log processing is then shifted to idle stage.

If you are still experiencing hardfaults after switching to the nrf_log module, then make sure that the hardfault library is used.

Add these to your projects:

$(SDK_ROOT)/components/libraries/hardfault/hardfault_implementation.c
$(SDK_ROOT)/components/libraries/hardfault/nrf52/handler/hardfault_handler_gcc.c

And set HARDFAULT_HANDLER_ENABLED to 1 in sdk_config.h, and add DEBUG_NRF in your preprocessor definitions.

RE: Hard fault - memset and printf

Nguyen Hoan Hoang — Sat, 24 Apr 2021 23:06:42 GMT

printf does not work well with softdevice. Use uart instead