The current radio drivers are basic and not designed for an RTOS.
We need to develop a wrapper for the radio driver to facilitate its integration with FreeRTOS.
To achieve this, we will need to conduct research and development to determine the best method for integrating the radio with various RTOS tasks.
Desired Operation
The radio should operate independently of any specific task, ensuring the radio code is non-blocking. This is crucial because the radio involves extended waiting periods, and we want to avoid CPU hogging during high communication traffic.
Possible Solution
One possible approach is to create a set of RTOS tasks dedicated to managing the radio resource. In this method, any task that wants to send data over the radio will enqueue its information, which will then be transmitted by the radio task.
Radio Driver Wrapper
Problem statement
The current radio drivers are basic and not designed for an RTOS. We need to develop a wrapper for the radio driver to facilitate its integration with FreeRTOS.
To achieve this, we will need to conduct research and development to determine the best method for integrating the radio with various RTOS tasks.
Desired Operation
The radio should operate independently of any specific task, ensuring the radio code is non-blocking. This is crucial because the radio involves extended waiting periods, and we want to avoid CPU hogging during high communication traffic.
Possible Solution
One possible approach is to create a set of RTOS tasks dedicated to managing the radio resource. In this method, any task that wants to send data over the radio will enqueue its information, which will then be transmitted by the radio task.