Hi, I had a question regarding the device driver modelling in Zephyr. I see that most device drivers in Zephyr are not 'thread sensitive'. That is, there is a possibility of some unintended behaviour

This will help, Andy. Thanks for your inputs! Regards, Raj

Hi, This is a question related to thread scheduling. Imagine you have 2 custom threads in addition to the “main thread”. The custom threads are created static (K_THREAD_DEFINE) and are cooperative thr

Thanks Carles. This is what I had in my mind too. This is already done for the generic spi flash driver (drivers/flash/spi_nor.c). I’ll hope that’s all that’s required. Thanks again. Regards, Raj

Hi Carles, Guess this mail got buried while you were away. Please help me out here. Regards, Raj

The stack is not allocated in your example when you are using k_thread_create. Use the below code instead. static K_THREAD_STACK_DEFINE(threadStack1, 1024); static struct k_thread thread1; k_thread_cr

Hi Carles, I am trying to build Zephyr to fit in a memory constrained device of 64kB. My device doesn’t require multithreading and hence I disabled multithreading to save on the memory. However, this

Thanks Carles. I made CONFIG_INIT_STACKS=y and used stack_unused_space_get to get what I wanted. Regards, Raj

Hi, Is there a way to get the remaining stack space of a thread in Zephyr? For e.g. if a thread is configured to use a max stack space of 512 bytes, is there a way to find out the actual stack used by

Thanks Marti. Will get back to you if I have any more questions. Regards, Raj

Hi Marti, I see that you have modified the “debug”, “debugserver” and “flash” scripts to make it OS agnostic. I am working on an xtensa board and I have a dedicated script for this board which is diff