Hi all,
I would like to make use of the freertos i2c example to integrate it into the thread router eligible device program. The objective is to make a i2c slave freertos task in order to receive the data from a RP in a task way instead of in an interrupt way.
The questions are:
I show here some of the piece of code of the i2c freertos slave task prorities, tasks functions I need to allocate in the "frdmkw41z_wireless_examples_thread_router_eligible_device_freertos":
Task priority:
Task creation:
I2C Slave callback:
I2C Slave Task:
The difficulties I experience are that "frdmkw41z_wireless_examples_thread_router_eligible_device_freertos" router_eligible_device_app.c uses a queue of different subtask of the main program, so I do not know if I need to create general tasks to the i2c slave or tasks related to the app router_eligible_device program.
Regards,
Diego Comin
The slave callback function "i2c_slave_callback" remains to be an interrupt also with this i2c freeRTOS example?
Hello,
Sorry for the late reply, by any chance, have you checked the implementation for the rest of the peripherals such as the temperature read and the buttons and GPIO interruptions?
I believe if you use them as a guide your development will be easier as the only documentation available to achieve what you are trying to do it's the developer's application user guide where you can find more information regarding the task usage in the connectivity framework.
Regards,
Estephania