Re: [riot-devel] rtc alarm running with threads

Hi Paula, It is likely that the debug print in the sale_test function overflows the ISR stack. You can increase that stack size by adding CFLAGS += -DISR_STACKSIZE=1024 to your Makefile. The interrupt service routines on cortex m have a separate stack which is set to 512 bytes by default. Usually

Re: [riot-devel] rtc alarm running with threads

Hi Kaspar, I'm running on stm32-l1, board nucleo-152RE Paula 2017-10-20 18:13 GMT-03:00 Kaspar Schleiser : > Hi Paula, > > on which platform are you running your application? > > Kaspar > > On 10/20/2017 09:45 PM, Paula Ortega Cancino wrote: > > Hi Oleg, > > > > Thanks for

Re: [riot-devel] rtc alarm running with threads

Hi Paula, on which platform are you running your application? Kaspar On 10/20/2017 09:45 PM, Paula Ortega Cancino wrote: > Hi Oleg, > > Thanks for your help. I should mention that i'm working on the 2017.07 > release. This is the main functions of the code, the behavor i'm > expecting is to

Re: [riot-devel] rtc alarm running with threads

Hi Oleg, Thanks for your help. I should mention that i'm working on the 2017.07 release. This is the main functions of the code, the behavor i'm expecting is to trigger the alarm every TIME_WAITING seconds, run sale_test() and the go back to the control thread. However i get a kernel panic or run

Re: [riot-devel] rtc alarm running with threads

Dear Paula, can you share the code of your application somewhere? That might help to find the issues. I would suppose that the interrupt handler is faulty or consumes too much memory or something like this. I think start debugging with a basic application that just prints some text whenever a

[riot-devel] rtc alarm running with threads

Hi, I've been working on an application that activates rtc alarms every few seconds, when the alarm is activated it sends a message to a thread. This msg is used in a thread that in its turn sends messages over gnrc. However, after a while sending messages, it stops and the mcu only gets in in