CAN module on CC35xx supports the
following functional requirements:
- Designed based on Bosch MCAN IP
- Conform with CAN Protocol 2.0 A,
B and ISO 11898-1:2015
- Supports AUTOSAR and SAE J1939
- Supports Bosch CAN 2.0 A/B protocol with up to 8 message bytes
- Supports up to 1Mbps communication rate in CAN2.0 mode
- Supports up to 32 dedicated transmit buffers
- Supports configurable transmit FIFO for up to 32 elements
- Supports configurable transmit queue for up to 32 elements
- Supports configurable transmit event FIFO for up to 32 elements
- Supports up to 64 dedicated receive buffers
- Supports two configurable receive FIFOs for up to 64 elements each
- Supports up to 128 filter elements
- 4KB embedded SRAM for message buffering
- Supports SECDED ECC (single error correction double error detection) mechanism
on message SRAM
- Supports internal and external loop back mode for self-test
- Supports time stamp counters
- Supports clock stop and wakeup feature
- Possiblity to access message RAM
and DCAN registers from debugger when DCAN operation is suspended due to CPU
halt
- Responds within 50ms to a wakeup CAN message
- Supports all necessary interrupt
conditions as implemented in DCAN core IP
- Implementation of 2 DMA triggers
for system DMA based data transfer with DCAN
- Have two clock domains - bus interface clock domain (HCLK) and CAN functional
clock (CCLK) for bit timing
- The bus interface clock (HCLK) have be same or higher frequency than CAN
functional clock (CCLK)
- Have internal clock prescaler to
generate lower functional clock frequencies for operation at lower bit rates
- Maintain clock continuity while
transitioning between data rates
- CAN interface clock is 80MHz and
provided by PRCM module when DCAN is enabled
- CAN functional clock is 80MHz and
provided by PRCM module
- Ability to operate alongside RF radio in regards to hardware implementation as
well as software handling