Atmel Xplained Pro Evaluation Kit ATSAM4E-XPRO ATSAM4E-XPRO Data Sheet

Product codes
ATSAM4E-XPRO
Page of 1506
SAM4E [DATASHEET]
Atmel-11157D-ATARM-SAM4E16-SAM4E8-Datasheet_12-Jun-14
654
33.
Controller Area Network (CAN)
33.1
Description
The CAN controller provides all the features required to implement the serial communication protocol CAN defined
by Robert Bosch GmbH, the CAN specification as referred to by ISO/11898A (2.0 Part A and 2.0 Part B) for high
speeds and ISO/11519-2 for low speeds. The CAN Controller is able to handle all types of frames (Data, Remote,
Error and Overload) and achieves a bitrate of 1 Mbit/s.
CAN controller accesses are made through configuration registers. Eight independent message objects
(mailboxes) are implemented. 
Any mailbox can be programmed as a reception buffer block (even non-consecutive buffers). For the reception of
defined messages, one or several message objects can be masked without participating in the buffer feature. An
interrupt is generated when the buffer is full. According to the mailbox configuration, the first message received
can be locked in the CAN controller registers until the application acknowledges it, or this message can be
discarded by new received messages.
Any mailbox can be programmed for transmission. Several transmission mailboxes can be enabled in the same
time. A priority can be defined for each mailbox independently.
An internal 16-bit timer is used to stamp each received and sent message. This timer starts counting as soon as
the CAN controller is enabled. This counter can be reset by the application or automatically after a reception in the
last mailbox in Time Triggered Mode.
The CAN controller offers optimized features to support the Time Triggered Communication (TTC) protocol.
33.2
Embedded Characteristics
Fully Compliant with CAN 2.0 Part A and 2.0 Part B
Bit Rates up to 1 Mbit/s
8 Object Oriented Mailboxes with the Following Properties:
̶
CAN Specification 2.0 Part A or 2.0 Part B Programmable for Each Message
̶
Object Configurable in Receive (with Overwrite or Not) or Transmit Modes
̶
Independent 29-bit Identifier and Mask Defined for Each Mailbox
̶
32-bit Access to Data Registers for Each Mailbox Data Object
̶
Uses a 16-bit Timestamp on Receive and Transmit Messages
̶
Hardware Concatenation of ID Masked Bitfields To Speed Up Family ID Processing
16-bit Internal Timer for Timestamping and Network Synchronization
Programmable Reception Buffer Length up to 8 Mailbox Objects
Priority Management between Transmission Mailboxes
Autobaud and Listening Mode
Low Power Mode and Programmable Wake-up on Bus Activity or by the Application
Data, Remote, Error and Overload Frame Handling
Write Protected Registers