For the full functionality of this website cookies are needed. Please activate cookies and refresh your browser. After the refresh a cookie management dialog will be shown.

This website uses cookies for functional, comfort and statistics purposes. You can change this setting at any time by clicking on „change settings“. If you consent to this use of cookies please click „Yes, I agree“. Our cookie policy




M_CAN and M_TTCAN IP module

The M_CAN is a CAN IP module that can be realized as a standalone device, as part of an ASIC, or on an FPGA. It performs communication according to ISO11898-1:2015. It supports classical CAN and CAN FD (CAN with Flexible Data-rate). 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 integration, multiple M_CAN controllers may share the same message RAM. The Host CPU is connected via the 32-bit Generic Slave Interface.

C_CAN FD8 IP module

The C_CAN FD8 is a CAN IP module that can be implemented as a standalone device, as part of an ASIC, or on an FPGA. It is software compatible to the well known C_CAN IP module.

The C_CAN FD8 performs communication according to ISO11898-1:2015. It supports classical CAN and CAN FD (CAN with Flexible Data-rate) communication with up to 8 byte data fields. For connection to the physical layer additional transceiver hardware is required.

For communication on a CAN network, up to 32 Message Objects can be configured. The Message Objects and Identifier Masks for acceptance filtering of received messages are stored in the Message RAM. All functions concerning the handling of messages are implemented in the Message Handler. Those functions are acceptance filtering, transfer of messages between the CAN Core and the Message RAM, and handling of transmission requests as well as the generation of the module interrupt. The register set of the C_CAN FD8 can be accessed directly by an external CPU via the module interface. These registers are used to control/configure the CAN Core and the Message Handler and to access the Message RAM. The Module Interfaces delivered with the C_CAN FD8 module can easily be replaced by a customized module interface adapted to the needs of the user.



CAN FD (CAN with Flexible Data-rate) was introduced by Bosch in 2012 to overcome the Classic CAN's bit rate limitation to 1 Mbps and to expand the number of data bytes per CAN frame from up to 8 to up to 64, thereby closing the gap between Classic CAN and other protocols. This is achieved by a modified CAN frame format where the bit rate can be switched to faster value inside the CAN frame and by a new data length coding.

CAN FD is standardized as ISO11898-1:2015. CAN FD protocol controllers are also able to perform classical CAN communication.

CAN protocol

The CAN Protocol is developed by Robert Bosch GmbH and is patented.

In addition to the CAN IP modules offered by Bosch, a CAN Protocol License is required. The CAN Protocol License is also required for self-developed CAN modules, or for CAN modules purchased from other vendors.


VHDL Reference CAN

The VHDL Reference CAN is intended for semiconductor designers/manufacturers who want to build their own implementation of a classical CAN or CAN FD device using VHDL as hardware description language.

Plug-and-Secure Communication for CAN

Plug-and-Secure Communication for CAN (PnS for CAN) is a novel approach for establishing and refreshing symmetric cryptographic keys in CAN networks in a plug-and-play manner.

This is done by exploiting special properties of the CAN physical layer. The approach excels in its low complexity, its low bandwidth requirements and its seamless integration into the existing CAN ecosystem.

Read more about PnS for CAN in two recent articles published in the December 2015 issue of CiA's CAN Newsletter as well as at the International CAN Conference 2015 in Vienna, Austria:


CAN literature