MDK-ARM Keil, MDK-ARM Datasheet - Page 151

• Manufacturer Part Number: MDK-ARM
• Description: KIT REALVIEW MCU DEVELOPMENT
• Manufacturer: Keil
• Type: Compiler and IDEr

Specifications of MDK-ARM

• For Use With/related Products: ARM MCUs
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

Getting Started: Building Applications with RL-ARM
151
Object Buffers
The internal architecture of a CAN controller comes in two varieties: Basic CAN
and Full CAN. Basic CAN has a single transmit and receive buffer. Full CAN
has multiple transmit and receive buffers.
Full CAN supports a more
sophisticated use of the CAN
protocol. It also allows higher
throughput of CAN messages.
In our first example, we used
the CAN_rx_object() function to
define the messages to be
received into the CAN
controller. We ignored the
channel parameter. In a full
CAN controller, the channel
parameter defines in which
receive buffer the message will
be stored. This provides both buffering in hardware and a more efficient access
to the new data. The final API call in the RL_CAN driver allows us to use the
same mechanism for transmitting messages.
CAN_tx_object (1, 2, 11, STANDARD_FORMAT);
Here, the channel number will specify which transmit buffer is used to hold a
given message frame. This allows several messages to be scheduled
simultaneously and ensures that a high priority message will be sent immediately.