MDK-ARM Keil, MDK-ARM Datasheet - Page 147

• 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
level API and message buffering. The second file,
level code for a specific CAN peripheral. Both modules have an include file,
CAN_cfg.h
configuration options in RL-ARM,
graphically displayed in the µVision Configuration Wizard. Each supported
microcontroller has its own version of
Therefore, you must take care to add the correct files to your project. In each of
your program modules, you must include the
the CAN driver functions.
The configuration options in
being used. As a minimum, you will need to define the number of transmit and
receive objects. This is, in effect, the size of the transmit and receive queue
available to the CAN controller. If the microcontroller has more than one CAN
peripheral, the
to use. Finally, depending on the clock structure of the microcontroller, you may
need to define the input clock value to the CAN controller. This is necessary for
the API functions to accurately calculate the CAN bit timing rate.
CAN Driver API
The CAN driver API consists of eight functions as shown below.
The first three API functions are used to prepare a CAN controller to send and
receive messages on the network.
CAN_init (1, 500000);
CAN_rx_object (1, 2, 33, STANDARD_FORMAT);
CAN_start (1);
, which is used to provide custom settings. Like all the other
CAN_cfg.h
file will have options to enable the controllers you wish
CAN_cfg.h
CAN_cfg.h
RTX_CAN.c
vary depending on the microcontroller
is a template file, which is
RTX_CAN.h
,
CAN_hw.c
CAN_hw.c
header file that defines
, and
, provides the low
CAN_cfg.h
file.
147