RE: Defining a thread with a K_FOREVER dealy will cause a compile error

Ignacio — Fri, 04 Feb 2022 12:00:42 GMT

That works. Although latest Nordic documentation shows the same for k_thread_start

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/reference/kernel/threads/index.html?highlight=k_thread_start#c.k_thread_start

Zephyr latest version and 2.7.0 show the same info

https://docs.zephyrproject.org/2.7.0/reference/kernel/threads/index.html?highlight=k_thread_start#c.k_thread_start

Thus, it is my opinion that using K_FOREVER on the thread definition is the correct implementation. Setting value as "-1" should be a temporary workaround.

RE: Defining a thread with a K_FOREVER dealy will cause a compile error

Håkon Alseth — Fri, 04 Feb 2022 11:43:25 GMT

Hi,

You are viewing older documentation. The define itself takes in a int type, while the K_FOREVER is a type k_timeout_t.

Could you try providing "-1" as the delay? Similar to how its done here:

https://github.com/nrfconnect/sdk-zephyr/blob/v2.7.0-ncs1/samples/drivers/espi/src/espi_oob_handler.c#L28-L38

Kind regards,

Håkon