Posted on March 21, 2018 at 08:27
When using an RTOS you need to think about the actions (inputs, outputs) that are taking place. CAN does a couple of things, receives and transmits. Therefore, you could specify 2 tasks, 1 for RX and the other for TX duties.
/**
* @brief All reception of CAN messages are processed
*
* Process is ran when the CAN RX interrupt passes the CAN_RX_ISR_FLAG. This
* represents at least a single packet on the FIFO. All mailboxes are processed
* and queued to the proper handler.
*
* @param argument task arguments - none needed
*/
void can_rx_process( void const * argument )
{
osEvent evt;
uint8_t data[8];
CAN_RxHeaderTypeDef rx_msg;
HAL_CAN_ActivateNotification(&hcan1, CAN_IT_RX_FIFO0_MSG_PENDING | CAN_IT_ERROR );
for( ;; )
{
evt = osSignalWait( CAN_RX_ISR_FLAG | CAN_ERR_ISR_FLAG, WDT_MAX_WAIT_TIME );
if( evt.value.signals & CAN_RX_ISR_FLAG )
....�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?
This is a CAN RX task that waits for the interrupt coming from messages pending.
/**
* @brief Transmission of all CAN messages originate from this task
*
* @param argument
*/
void can_tx_process( void const * argument )
{
osEvent evt;
CAN_TxHeaderTypeDef tx_msg;
uint8_t msg_data[8];
uint32_t mailbox;
osTimerStart( heartbeat_timer, CAN_HEARTBEAT_DELAY );
for( ;; )
{
evt = osMessageGet( can_tx_handle, WDT_MAX_WAIT_TIME );
if( evt.status == osEventMessage )
{
message_t *msg = (message_t*) evt.value.p;
....�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?�?
This is a task that waits for another task to send a `message_t` to it.
Yes there are some extras in there you don't need but the principles are the same. Both tasks wait for some work to perform. The RX task waits for the interrupt of messages pending, the TX task waits for another task to send it some message to send.
