So our CAN handler will slap all inbound CAN messages in a queue to be processed later on, since it is interrupt driven. We need a higher level task that can pop a CAN message off and route it accordingly to be processed. This not only decouples the CAN driver from the RTOS application but also allows more efficient processing and giving the RTOS more control to do its thang
So our CAN handler will slap all inbound CAN messages in a queue to be processed later on, since it is interrupt driven. We need a higher level task that can pop a CAN message off and route it accordingly to be processed. This not only decouples the CAN driver from the RTOS application but also allows more efficient processing and giving the RTOS more control to do its thang