Thanks @​martinlesyo! Glad you found it useful.

Glad it helped :)

Glad you found it useful!

You're welcome!

Hello there!

Glad they’re helping! :)

You're welcome :)

You're welcome. Glad it helped. 😎

You're welcome

Oooh good question. It depends on if you want to use a work thread to do the work versus a dedicated or other thread. I'll noodle on it some more.

I would submit another work task at the end of the work task in question. You should be able to queue the next task within the current work function.

Thanks for the clarification Aaron

@@CircuitDojo Great video though! Just something I had to look into to explain behavior I was seeing.

Hi Pavitra, One thing that you can do is save the uptime before and after the execution of the function you'd like to check. k_uptime_get is the API call for it. It returns the # of milliseconds since boot. That may not be useful though for faster execution functions. You may need to enable the tracing functionality to get more fine grained information about your execution environment. I've played with it in the past a little but didn't get too far with it. If there's enough interest maybe I'll do a video on that in the future.

Great suggestion. It’s tough on those smaller chips. (It was tough with the original SDK!) I’ll see what I can come up with. 😎

@@CircuitDojo thank you so much for consideration

That allows you to allocate a message queue which can be helpful for moving data from one thread to another in a safe manor. I often use it to pass a specific event struct for processing/publishing.