SPRAD59 October   2023 TMS320F280039

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1 Introduction
  5. 2 Key Differences Between DCAN and MCAN
  6. 3 Module Initialization
    1. 3.1 DCAN Initialization
    2. 3.2 MCAN Initialization
    3. 3.3 Initialization sequence
    4. 3.4 Code Snippets for Module Initialization
  7. 4 Bit Timing Configuration
  8. 5 Message RAM Configuration
  9. 6 Interrupt handling
    1. 6.1 MCAN Interrupt Sources
    2. 6.2 DCAN Interrupt Handling
    3. 6.3 MCAN Interrupt Handling
  10. 7 Transmitting data
    1. 7.1 Basic Transmission Process
      1. 7.1.1 Transmission with DCAN
      2. 7.1.2 Transmission with MCAN
    2. 7.2 MCAN Vs DCAN Transmit Procedural Differences
    3. 7.3 MCAN Transmit Concepts
      1. 7.3.1 Tx Event FIFO
  11. 8 Receiving Data
    1. 8.1 Introduction to Reception
    2. 8.2 Basic Reception Process
      1. 8.2.1 DCAN Reception
      2. 8.2.2 MCAN Reception
    3. 8.3 Filter Elements
      1. 8.3.1 Filter Element Structure
    4. 8.4 Rx Buffer
      1. 8.4.1 Receiving in Rx Buffer
    5. 8.5 Rx FIFO
      1. 8.5.1 Receiving in Rx FIFO
    6. 8.6 Receiving High Priority Messages
  12. 9 Avoiding network errors
  13. 10References

8.1 Introduction to Reception

In DCAN Message RAM, there are 32 configurable Message Objects that can be used for either transmission or reception. Receive Message Objects are used for storing received data. If needed by the application, acceptance filtering can be enabled for one or more message object(s). CPU read and write accesses to the Message RAM are done through three Interface Register (IFx) sets.

In MCAN, the Message RAM can be divided into sections to include Filter Elements, Rx Buffer Elements and Rx FIFO Elements. Filter Elements can be configured to be used with acceptance filtering and also determine where the corresponding matching frame is to be stored within the Message RAM. Rx Buffer and Rx FIFO are sections where the received frames are stored, with both having their own set of registers and interrupts. This structure provides flexibility to better serve different application needs. Message RAM can be read from directly using Driverlib APIs.