Put all can handler task functionality into its own file
The FDCAN1 module is still initialized in main, and its handle is externed as necessary
This could be further extended to initialize the hardware inside of the module as well, to completely block peripheral access
Likewise, can_handler.h provides a busQueue handle. All other threads which wish to write to the CAN bus should create a canlib can_msg_t object, populate it with the canlib API functions, and send it to busQueue using the native FreeRTOS API
See canlib PR for more context on the canlib implementation for the STM
@ManavToor can you please test this code and verify that both the send and receive functions work?
Joe-Joe-Joe-Joe
commented
2 months ago
externedas necessarycan_handler.hprovides a busQueue handle. All other threads which wish to write to the CAN bus should create a canlibcan_msg_tobject, populate it with the canlib API functions, and send it to busQueue using the native FreeRTOS API