nRF52840 constantly resets when application starts

RE: nRF52840 constantly resets when application starts

mrask — Thu, 09 Nov 2023 13:59:47 GMT

Issue resolved:

uBlox NINA-B301 module had external inductors for DC/DC. Original code was for that, so the resets were caused by enabling the DC/DC1 without having that capability.

RE: nRF52840 constantly resets when application starts

Sigurd — Fri, 03 Nov 2023 12:11:29 GMT

Hi,

[quote user="mrask"]I removed everything from my main function and it still resets but only once.[/quote]

If you test on the nRF52840-DK or NINA-B301, do you see this same behavior there?

RE: nRF52840 constantly resets when application starts

mrask — Fri, 03 Nov 2023 11:58:47 GMT

Update: I removed everything from my main function and it still resets but only once. I've tried using the same iar_startup and system_nrf52840 files from the example and it still does not work.

Does this point anyone in the right direction for debugging?

RE: nRF52840 constantly resets when application starts

mrask — Thu, 02 Nov 2023 12:56:15 GMT

Hi,

I have gotten hardfaults if I restart the debug session if I'm already in one. How should I add that hardfault handler to my project if I do not have a sdk_config.h? I don't see any macro similar to HARDFAULT_HANDLER_ENABLED. I also do not have any output logs right now.

RE: nRF52840 constantly resets when application starts

Sigurd — Thu, 02 Nov 2023 12:49:08 GMT

Hi!

Do you have any log output from when this happens, that might give us some ideas about what is happening ?

Maybe you could you try to add the hardfault handler library to your project, and see if you can get any more information based on that?

When adding the HardFault handling library to your project

Add these to your projects:

$(SDK_ROOT)/components/libraries/hardfault/hardfault_implementation.c
$(SDK_ROOT)/components/libraries/hardfault/nrf52/handler/hardfault_handler_gcc.c (variant here depends on your toolchain)

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

You should then be able to get more information about the hardfault when it triggers.