SLAAET4 April   2025 MSPM0G3506 , MSPM0G3507 , MSPM0G3518 , MSPM0G3519

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
    1. 1.1 MCAN Features
  5. 2Sysconfig Configuration for MCAN Module
    1. 2.1 MCAN Clock Frequency
    2. 2.2 MCAN Basic Configuration
      1. 2.2.1 Transmitter Delay Compensation (TDC)
      2. 2.2.2 Bit Timing Parameters
      3. 2.2.3 Message RAM Configuration
        1. 2.2.3.1 Standard and Extended ID Filter Configuration
          1. 2.2.3.1.1 How to Add More Filters
        2. 2.2.3.2 TX MSG RAM
        3. 2.2.3.3 RX MSG RAM
    3. 2.3 Advanced Configuration
    4. 2.4 Retention Configuration
    5. 2.5 Interrupts
    6. 2.6 Pin Configuration and PinMux
  6. 3Demo Project Descriptions
    1. 3.1 TX Buffer Mode
    2. 3.2 TX FIFO Mode
    3. 3.3 RX Buffer Mode
    4. 3.4 RX FIFO Mode
  7. 4Debug and Design Tips to Resolve/Avoid CAN Communication Issues
    1. 4.1 Minimum Number of Nodes Required
    2. 4.2 Why a Transceiver is Needed
    3. 4.3 Bus Off Status
    4. 4.4 Using MCAN in Low Power Mode
    5. 4.5 Debug Checklist
      1. 4.5.1 Programming Issues
      2. 4.5.2 Physical Layer Issues
      3. 4.5.3 Hardware Debug Tips
  8. 5Summary
  9. 6References

2.2.3.1 Standard and Extended ID Filter Configuration

Figure 2-5 shows what parameters are included in Standard and Extended ID Filter configuration block.

Standard and Extended ID Filter Configuration Figure 2-5 Standard and Extended ID Filter Configuration
  • Std ID Filter List Start Address: each standard ID filter takes 4 message RAM address.
  • Number of Standard ID Filters: up to 128 filter elements can be configured for 11-bit standard IDs. SysConfig currently does not support configuration of more than one filter. More filters can be added in the user application, however make sure that enough RAM is allocated during initialization
  • Standard ID Filter configuration → Filter Element Configuration: all enabled filter elements are used for acceptance filtering of standard frames. Acceptance filtering stops at the first matching enabled filter element or when the end of the filter list is reached. Options for this parameter are shown below.
    • 0x0: disable filter element
    • 0x1: store in Rx FIFO 0 if filter matches
    • 0x2: store in Rx FIFO 1 if filter matches
    • 0x3: reject ID if filter matches
    • 0x4: set priority if filter matches
    • 0x5: set priority and store in FIFO 0 if filter matches
    • 0x6: set priority and store in FIFO 1 if filter matches
    • 0x7: store into Rx Buffer, configuration of standard filter type ignored
  • Standard ID Filter configuration → Filter Type: standard filter type configuration. Options for this parameter are shown below.
    • 0x0: range filter from SFID1 to SFID2 (SFID2 ≥ SFID1)
    • 0x1: dual ID filter for SFID1 or SFID2
    • 0x2: classic filter: SFID1 = filter; SFID2 = mask
    • 0x3: filter element disabled
  • Standard ID Filter configuration → Filter ID 1 (SFID1): Standard Filter ID 1. When filtering for Rx buffers, this field defines the ID of a standard message to be stored. The received identifiers must match exactly, and no masking mechanism is used.
  • Standard ID Filter configuration → Filter ID 2 (SFID2): Standard Filter ID 2. This ID has different definitions depending on the filter element configuration. If the filter element configuration is from 0x1 to 0x6, then SFID2 is the second ID of standard ID filter element. If the filter element configuration is 0x7, then SFID2 is a filter for Rx buffers.

The configuration for the Extended ID filter is shown below.

  • Extd ID Filter List Start Address: each extended ID filter takes 8 message RAM addresses.
  • Number of Extended ID Filters: up to 64 filter elements can be configured for 29-bit extended IDs. SysConfig currently does not support configuration of more than one filter. More filters can be added in the user application, however make sure that enough RAM is allocated during initialization.
  • Extended ID Filter configuration → Filter Element Configuration: all enabled filter elements are used for acceptance filtering of extended frames. Acceptance filtering stops at the first matching enabled filter element or when the end of the filter list is reached.
    • 0x0: disable filter element
    • 0x1: store in Rx FIFO 0 if filter matches
    • 0x2: store in Rx FIFO 1 if filter matches
    • 0x3: reject ID if filter matches
    • 0x4: set priority if filter matches
    • 0x5: set priority and store in FIFO 0 if filter matches
    • 0x6: set priority and store in FIFO 1 if filter matches
    • 0x7: store into Rx Buffer or as debug message, configuration of extended filter type ignored
  • Extended ID Filter configuration → Filter Type: extended filter type configuration. Options for this parameter are shown below.
    • 0x0: range filter from EFID1 to EFID2 (EFID2 ≥ EFID1)
    • 0x1: dual ID filter for EFID1 or EFID2
    • 0x2: classic filter: EFID1 = filter, EFID2 = mask
    • 0x3: range filter from EFID1 to EFID2 (EFID2 ≥ EFID1), Extended ID and Mask not applied
  • Extended ID Filter configuration → Filter ID 1 (EFID1): extended Filter ID 1. First ID of the extended ID filter element. When filtering for Rx buffers, this field defines the ID of an extended message to be stored.
  • Extended ID Filter configuration → Filter ID 2 (EFID2):Extended Filter ID 2. This ID has different definitions depending on the extended filter element configuration. If the extended filter element configuration is from 0x1 to 0x6, then EFID2 is the second ID of extended ID filter element. If the extended filter element configuration is 0x7, then EFID2 is a filter for Rx buffers.