HardFault on saadc_init();

[Proton]

Hello! When I start the s132 device, it freezes from time to time. In debug mode, it does not exit the saadc_init () function;

I connected "hardfault.h" and "hardfault_genhf.h", pressed further and still does not exit saadc_init (), but stops at ses_startup_nrf52.s

What is the reason and how can I get rid of this problem?

[Proton]

When the power is completely turned off and turned on again, this problem may temporarily disappear, but from the same address 00000A60 I can fall down here

[Vidar Berg]

Hello,

Can you upload a minimal version of your project so I can try to debug this here?

The MBRs hardfault handler is at address 0xA60 and SES adds a breakpoint there by default, but if you continue execution you should en up inside the app's fault handler.

[Proton]

app's fault handler with a transition to startup.s does not give an understanding of why this is happening

handlebug.zip

[Vidar Berg]

Seems like the fault was caused by the fact that the app attempted to log messages before initializing the logger module.  Another issue which led to an assertion inside the SAADC driver was that the SAADC configuration parameter was not zero-initialized.

Modified project:

handlebug.zip

[Proton]

Yes, thanks, it made life so much easier !! But this did not completely eliminate the problems.
When I first start it, I can wait for the drv_rtc_init () function to fire for a very long time, up to 15 seconds. When any twi device is connected, read and write functions work for a very long time.
If I stop running the program several times, I fall back to 00000A60.
Am I having something wrong with the timing initialization?

[Vidar Berg]

Glad it helped some. Are you running this on a custom board, or a nordic DK?

Proton said:

If I stop running the program several times, I fall back to 00000A60.

The Softdevice will trigger an assertertion if you continue execution after halting CPU. This is because the Softdevice will detect that its real time requirements have not been met. Try to disable breakpoint on hardfault as shown below and see if your program ends up in the app error handler.

 

[Proton]

I am running this on a custom board. But twi is just 2 hooked wires.
With this project code on the nordic DK, such problems are not observed, is the timing correct?

Thank you, I don't fall out at 00000A60 now.

[Vidar Berg]

I didn't notice any delays, but maybe that's as expected since I don't have the sensor or the external flash connected. Are you able to tell where the program gets delayed for 15 seconds?

[Proton]

The drv_rtc_init function contains a line for outputting the log NRF_LOG_INFO ("RTC: Uninitialized.");
It may take 15 seconds until it appears in the terminal. But there are times when it is repeated many times in the terminal.

As a result, I dump here

[Proton]

Another way to get into HardFault (00000A60) was found with a subsequent reboot. This will happen if you uncomment the lines

[Vidar Berg]

I don't see any reference to the RSSI function in the code you uploaded earlier.

Proton said:

It may take 15 seconds until it appears in the terminal. But there are times when it is repeated many times in the terminal.

 Looks like it's going in a bootloop. Assume it's reset by the app_error_fault_handler() function?