event data disappears in app_scheduler()

RE: event data disappears in app_scheduler()

Mike Voytovich — Tue, 02 Feb 2016 17:58:37 GMT

Actually it looks like the implementation of app_sched_event_put copies the data into the event queue, so calling it with a stack variable is OK:

               memcpy(&m_queue_event_data[event_index * m_queue_event_size],
                   p_event_data,
                   event_data_size);

RE: event data disappears in app_scheduler()

Doug_H — Wed, 02 Sep 2015 02:54:07 GMT

Thank you very much. All fixed now!

RE: event data disappears in app_scheduler()

RK — Wed, 02 Sep 2015 02:16:34 GMT

tag_evt_t * p_tag_evt;

Two errors there - firstly you're allocating a pointer to the data, but not allocating actual space for the data, that pointer starts pointing to some random piece of memory. You're fortunate that you're not getting a hard fault writing to illegal memory or writing over your code. You want

tag_evt_t tag_evt;

and pass the address of it to your function &tag_evt

But that's no good either as that variable is on the stack, it's local to the function, so as soon as you leave the function the memory is no-longer valid. By the time your event handler is called the stack will have overwritten the data, probably.

If you only have one at any time, make the variable static, else use malloc() and free()

static tag_evt_t tag_evt;