MSPM0G3519: Multi function pin assignment

Part Number: MSPM0G3519
Other Parts Discussed in Thread: SYSCONFIG

Hi TI supporter,

I'm using the MSPM0G3519 in my design with 32-pin RHB.
I have the sensor that has multi interface like this. ( my sensor has jumper to select SPI / I2C)

pin1 Input I2C_SCL/ SPI_CLK
pin2 Input I2C_SDA / SPI_SDI
pin3 Output I2C_SA0 / SPI_SDO
pin4 input CS

I'm got the trouble when trying to assign the MCU pin for sensor.
ex: with the pin 1, I found the pin 15 that has both I2C_SCL and SPI_SCL, it acceptable, but with the I2C_SDA / SPI_SDI, I can not find any acceptable. 
image.png

Please leave me a hand.

Thank you,
Long Le

  • Hi Long,

    I would recommend that you first decide whether you would like to interface with I2C or SPI, then search for the MCU pins to use.

    If you choose I2C, you can then take a look at table 6-10 in the datasheet to see which pins enable each I2C functionality. This table simply shows which signals are available on each pin for each package.

    If you choose SPI, then you can take a look at table 6-14 in the datasheet to see which pins enable each SPI functionality. 

    After you've checked which pins enable each functionality, you can wire those pins from your sensor to the MCU. You can then configure the device to communicate with the sensor using these pins for the proper pin functionality. There are examples for how to initialize pins for I2C and SPI in our SDK - i would recommend that you start with one of these examples and adjust it in sysconfig to communicate on the correct pins and then perfect the configuration from there.

  • Hi Dylan,
    Thank for your recommend! 

    Can the SPI0_POCI work as SPI0_PICO cuz I saw the signal type is IO ?

  • Hi Long, 

    SPI_POCI cannot be used as SPI_PICO. The SPI instance can be configured as a peripheral, or as a controller, which is why the pin is marked as an IO. 

  • Thank you Dylan, 

    Long Le