Table 3-1. M_CAN subsystem external signals
Signal name Direction Description
M_CAN_0_Rx input M_CAN_0 CAN Rx signal
M_CAN_0_Tx output M_CAN_0 CAN Tx signal
M_CAN_1_Rx input M_CAN_1 CAN Rx signal
M_CAN_1_Tx output M_CAN_1 CAN Tx signal
3.2 Overview
The M_CAN module is the new CAN Communication Controller IP-module. The
M_CAN performs communication according to ISO11898-1 (Bosch CAN specification
2.0 part A,B) and to Bosch CAN FD specification V1.0. Additional transceiver hardware
is required for connection to the physical layer.
The message storage is intended to be a single- or dual-ported Message RAM outside of
the module. It is connected to the M_CAN via the Generic Master Interface. Depending
on the chosen device, multiple M_CAN controllers can share the same Message RAM.
All functions concerning the handling of messages are implemented by the Rx Handler
and the Tx Handler. The Rx Handler manages message acceptance filtering, the transfer
of received messages from the CAN Core to the Message RAM as well as providing
receive message status information. The Tx Handler is responsible for the transfer of
transmit messages from the Message RAM to the CAN Core as well as providing
transmit status information.
Acceptance filtering is implemented by a combination of up to 128 filter elements where
each one can be configured as a range, as a bit mask, or as a dedicated ID filter.
The M_CAN can be connected to a wide range of Host CPUs via its 8/16/32-bit Generic
Slave Interface. The M_CAN's clock domain concept allows the separation between the
high precision CAN clock and the Host clock, which may be generated by an FM-PLL.
3.2.1 Features
The following are the features of M_CAN.
• Conforms with CAN protocol version 2.0 part A, B and ISO 11898-1
• CAN FD with up to 64 data bytes supported
• CAN Error Logging
Chapter 3 Modular CAN (M_CAN)
MPC5777C Reference Manual Addendum, Rev. 1, 12/2015
Freescale Semiconductor, Inc. 23
To Next Page
Loading...
Need help?
General
