sd_app_evt_wait() cause HardFault_Handler

RE: sd_app_evt_wait() cause HardFault_Handler

Inspectron — Tue, 14 Apr 2015 08:57:01 GMT

Aryan This solved my problem wih the HardFault.

RE: sd_app_evt_wait() cause HardFault_Handler

Susheel Nuguru — Tue, 14 Apr 2015 06:57:15 GMT

If you are telling me that the hardfaults occurs while stepping after hitting the breakpoint, then this is expected. The real time constraints of the softdevice are broken once you hit the breakpoint, at which time the MPU is stalled not allowing softdevice timer handlers to execute, so next time when you step then there could be unpredictable behaviour. It might allow you to step for some time or could hardfault depending on what the softdevice was doing at the moment.

I recommend you to go through the following if you want to understand it in more. devzone.nordicsemi.com/.../

RE: sd_app_evt_wait() cause HardFault_Handler

Meh05 — Mon, 13 Apr 2015 20:15:47 GMT

Yes, I removed optimizations (level 0). After deleting power_manage() function from main for loop it goes to hard fault also. When I set breakpoint to empty for loop and debug step by step it seems ok but when I run it free it goes to hard fault. So it seems that problem is not in this specific function but general.

RE: sd_app_evt_wait() cause HardFault_Handler

Inspectron — Mon, 13 Apr 2015 11:14:18 GMT

I have the same problem now. My main will be run only once. After it reaches the sd_app_evt_wait() function it will stuck in the HardFault_Handler. My Optimization level is 0.

RE: sd_app_evt_wait() cause HardFault_Handler

Susheel Nuguru — Mon, 13 Apr 2015 09:24:29 GMT

sd_app_evt_wait() would translate to simple __WFE instruction, and I am not sure why it would cause a hardfault. If you have come to conclusion that it hardfaults at this place from Keil debugger, have you removed all optimizations in the compiler? It is possible the the instructions before this call might have caused the hardfault and Keil's call stack is messed up.