FreeRTOS: Cube generates FreeRTOS application code stubs, which limits program modularity

[tygamvrelis]

Cube places all the task stubs, queues, etc in freertos.c, which reduces modularity. A better approach is using Cube to generate the peripheral drivers, and adding the FreeRTOS application code ourselves.

To resolve this issue, the Cube project should be modified to contain no data about our FreeRTOS application structure. This way, we can move around FreeRTOS threads, and structures such as queues, without needing to worry about these things being regenerated each time we run the Cube utilities.

[tygamvrelis]

It has now been learned that Cube can simply generate function declarations while allowing the functions themselves to be implemented solely by the user. With this in mind, we have decided that it would be best to use Cube to track the resources used by FreeRTOS.