SLAAEQ4 July   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.   Trademarks
  3. 1Introduction
    1. 1.1 Features Supported
    2. 1.2 CAN Frame Format
    3. 1.3 SPI Message Frame Format
  4. 2Implementation
    1. 2.1 SPI Message Format
      1. 2.1.1 SPI Commands
      2. 2.1.2 Instruction Set
    2. 2.2 Timeout Feature
    3. 2.3 Error Indication
    4. 2.4 Busy Status Indication
    5. 2.5 Message RAM Configuration
    6. 2.6 Test Environment
  5. 3References

Introduction

Controller Area Network (CAN) and Serial Peripheral Interface (SPI) are two widely adopted communication protocols in modern microcontroller units (MCUs). While CAN protocol dominates automotive applications due to the robust error handling and reliability, many low-end microcontrollers and sensors lack CAN support. In contrast, SPI is nearly universal across MCU devices. To bridge this technological gap, SPI-CAN interfaces enable seamless communication between SPI-based devices and CAN networks, allowing low-cost sensors and microcontrollers to integrate with CAN-based systems.

The SPI-CAN bridge functionality is implemented using the MSPM0G3507 device, which acts as an interface between an external SPI controller and a CAN network. When the external SPI controller initiates communication frames, the MSPM0G3507 translates these into CAN protocol instructions and transmits them across the CAN network.

Figure 1-1 illustrates the system architecture, showing the interconnections between the MSPM0G3507 device and the external interfaces. The device communicates with the external controller using 4-wire SPI protocol, while connecting to the CAN bus through a CAN physical layer transceiver (CAN-PHY).

MSPM0G3507 Block Diagram of SPI-CAN
                    Bridge Figure 1-1 Block Diagram of SPI-CAN Bridge