Nrf52 Hang during continuous operation

RE: Nrf52 Hang during continuous operation

Susheel Nuguru — Fri, 18 Nov 2022 08:53:35 GMT

[quote user="asv"]If device is in loop mode USB interupt or timer interupt may work (Done in threading operation in controller). am i right?[/quote]

Interrupts should work if the application managed to run till the point where the peripheral is configured correctly. But if the application faults or deadlocks before that point, then the peripheral is not configured to generate interrupts. Also make sure that you are compiling your project with no optimizations on code size and speed so that the code is generated for best debug experience.

[quote user="asv"]if device is in hardfault or some error condition appear can we restart the controller from default location (Similar to WDT)[/quote]

The fault handler should allows the application to handle the faults in a custom way. You are free to edit the default fault handling of the fault by the system.

RE: Nrf52 Hang during continuous operation

asv — Thu, 17 Nov 2022 15:49:18 GMT

Thanks for the feedback.
We added log in maximum possible locations but unfortunately we cant pointed out the issue In debug environement.

[quote userid="6207" url="~/f/nordic-q-a/93984/nrf52-hang-during-continuous-operation/396168"]loop/hardfault/hanged. [/quote]

If device is in loop mode USB interupt or timer interupt may work (Done in threading operation in controller). am i right?
if device is in hardfault or some error condition appear can we restart the controller from default location (Similar to WDT)

RE: Nrf52 Hang during continuous operation

Susheel Nuguru — Thu, 17 Nov 2022 10:17:22 GMT

Hi Vijay,

It is a bit hard in this case to even get a direction of suspects which could be causing issue in your case as it is too little information to process.

[quote user=""]But in some cases we feel it device is got hanged [/quote]

You should add more logs into your application to get a sense of application running or stuck in a loop/hardfault/hanged. This is particularly important since connecting the debugger seems to make the problem go away. There could be some timing issues as well in your application just based on the fact that you see issues only when debugger not connected.