K_TIMER() - HARD_FAULT - Data Access Violation - nrf9160

Question

Hi, 
 
 Currently we working on a project that uses:

nRF9160 
 Zyphre OS 
 Segger Embedded Studio for Arm (Nordic Edition) V5.10d 
 SDK v1.4

We need to handle multiple timeouts, to handle our processes, but we have a problem that we think occurs when our K_TIMERS expire. We are looking for restrictions on using multiple timers but we do not find any, the functions we are using are the following:

k_timer_init(timer, NULL, NULL); 
 k_timer_start(timer, K_MSEC(timeout), K_NO_WAIT);

And this is the error:

Is this a known bug? 
 Does anyone know of any restrictions that can cause this? 
 What could we be doing wrong?

Thanks a lot.

ReneDelgado · Accepted Answer

Hello H&aring;kon, Sorry for the delay, I have the most popular virus from this year. Yes regarding to our sequence is like you mentioned, but regarding to spinlock.h#L92 we do not calling this function explicit neither we are using recursive functions. As note, we are using mutex as the documentation suggest. 
 Also note that if I enable the segger system view this cracks earlier. 
 
 CONFIG_SEGGER_SYSTEMVIEW =y 
 CONFIG_USE_SEGGER_RTT =y 
 CONFIG_TRACING =y 
 
 If you want I can send you an email with a basic sample of the code. 
 Thanks, 
 Ren&eacute; D.

ReneDelgado · Answer

Hello H&aring;kon, 
 I removed all the printk() and all printf() functions, an now we are using our own debug functions. 
 And now, we are using LOG=y and LOG IMMEDIATE=n, with that changes, we do not have hard faults now. But, now we are in and infinity loop in timeout.c. It seems that the timers never ends.

Have you any idea to how solve this behavior? 
 
 Thanks, 
 Ren&eacute; D.

K_TIMER() - HARD_FAULT - Data Access Violation - nrf9160

Top Replies