C8051F060DK Silicon Laboratories Inc, C8051F060DK Datasheet - Page 225

• Manufacturer Part Number: C8051F060DK
• Description: DEV KIT FOR F060/F062/F063
• Manufacturer: Silicon Laboratories Inc
• Type: MCUr

Specifications of C8051F060DK

• Contents: Evaluation Board, Power Supply, USB Cables, Adapter and Documentation
• Processor To Be Evaluated: C8051F06x
• Interface Type: USB
• Silicon Manufacturer: Silicon Labs
• Core Architecture: 8051
• Silicon Core Number: C8051F060
• Silicon Family Name: C8051F06x
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant
• For Use With/related Products: C8051060, C8051F062 and C8051F063
• Lead Free Status / Rohs Status: Lead free / RoHS Compliant
• Other names: 336-1214

C8051F060/1/2/3/4/5/6/7
19.
Controller Area Network (CAN0, C8051F060/1/2/3)
IMPORTANT DOCUMENTATION NOTE: The Bosch CAN Controller is integrated in the C8051F060/1/2/3
devices. This section of the data sheet gives a description of the CAN controller as an overview and offers
a description of how the Silicon Labs CIP-51 MCU interfaces with the on-chip Bosch CAN controller. In
order to use the CAN controller, please refer to Bosch’s C_CAN User’s Manual (revision 1.2) as an accom-
panying manual to Silicon Labs’ C8051F060/1/2/3/4/5/6/7 Data sheet.
The C8051F060/1/2/3 family of devices feature a Control Area Network (CAN) controller that enables
serial communication using the CAN protocol. Silicon Labs CAN controller facilitates communication on a
CAN network in accordance with the Bosch specification 2.0A (basic CAN) and 2.0B (full CAN). The CAN
controller consists of a CAN Core, Message RAM (separate from the CIP-51 RAM), a message handler
state machine, and control registers. Silicon Labs CAN is a protocol controller and does not provide physi-
cal layer drivers (i.e., transceivers). Figure 19.2 shows an example typical configuration on a CAN bus.
Silicon Labs CAN operates at bit rates of up to 1 Mbit/second, though this can be limited by the physical
layer chosen to transmit data on the CAN bus. The CAN processor has 32 Message Objects that can be
configured to transmit or receive data. Incoming data, message objects and their identifier masks are
stored in the CAN message RAM. All protocol functions for transmission of data and acceptance filtering is
performed by the CAN controller and not by the CIP-51 MCU. In this way, minimal CPU bandwidth is
needed to use CAN communication. The CIP-51 configures the CAN controller, accesses received data,
and passes data for transmission via Special Function Registers (SFR) in the CIP-51. The CAN control-
, or CAN_CLK in the C_CAN User’s Guide) is equal to the CIP-51 MCU’s clock (SYSCLK).
ler’s clock (f
sys
Rev. 1.2
225