SLAAEN5 February   2025 MSPM0G1106 , MSPM0G1107 , MSPM0G1506 , MSPM0G1507 , MSPM0G1518 , MSPM0G1519 , MSPM0G3106 , MSPM0G3106-Q1 , MSPM0G3107 , MSPM0G3107-Q1 , MSPM0G3506 , MSPM0G3506-Q1 , MSPM0G3507 , MSPM0G3507-Q1 , MSPM0G3518 , MSPM0G3518-Q1 , MSPM0G3519 , MSPM0G3519-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
    1. 1.1 Bridge between CAN and SPI
  5. 2Implementation
    1. 2.1 Principle
    2. 2.2 Structure
  6. 3Software Description
    1. 3.1 Software Functionality
    2. 3.2 Configurable Parameters
    3. 3.3 Structure of Custom Element
    4. 3.4 Structure of FIFO
    5. 3.5 SPI Receive and Transmit (Transparent Transmission)
    6. 3.6 SPI Receive and Transmit (Protocol Transmission)
    7. 3.7 CAN Receive and Transmit
    8. 3.8 Application Integration
  7. 4Hardware
  8. 5Application Aspects
    1. 5.1 Flexible structure
    2. 5.2 Optional Configuration for SPI
    3. 5.3 Optional Configuration for CAN
    4. 5.4 CAN Bus Multinode Communication Example
  9. 6Summary
  10. 7References

5.4 CAN Bus Multinode Communication Example

CAN communication is a bus communication. Users can use this CAN-SPI bridge design to test the multinode communication of CAN bus. Figure 5-1 shows the basic structure. When the user sends a message to the CAN bus through any CAN-SPI bridge, the message is read back from other nodes immediately.

At least three LaunchPads must be used. Each CAN communication on the LaunchPad requires a transceiver. See Figure 4-3 to view the connection between the LaunchPad and the transceiver.

The CAN module of MSPM0 supports hardware filtering to select messages with specific IDs. Note that hardware filtering is not performed by default in this sample code. The user can configure hardware filtering. For specific configurations, see related documentation.

Basic Structure of Multinode Communication Figure 5-1 Basic Structure of Multinode Communication