This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSPM0G3518-Q1: MSPM0G3518-Q1: PIN MAPPING SHEET

Part Number: MSPM0G3518-Q1
Other Parts Discussed in Thread: SYSCONFIG

Hello,

I am currently working on an automotive hardware design project using the MSPM0G3518-Q1 MCU (80-pin LQFP-PN package). The device is being used in a CAN/LIN-based control panel application targeting the Stellantis STLA BRAIN platform.

I would like to request the Pin Mapping Sheet for the MSPM0G3518-Q1, similar to what was shared in the following thread:

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1559678/mspm0g3518-q1-pin-mapping-sheet

The Excel-format sheet with all pin mux options (filterable by peripheral such as ADC, SPI, CAN, GPIO, etc.) would be very helpful during the schematic pin assignment phase.

Could you please share the pin mapping sheet for this MCU?

Thank you in advance.

  • Hi Emrecan,

    For the MSPM0G3518-Q1 80-pin LQFP PN package, the package-specific pin mux information is available in the MSPM0G351x-Q1 datasheet under the Pin Attributes and Signal Descriptions sections. Those tables are the controlling source for pin/function assignment during schematic design. The datasheet specifically directs users to those sections for the full pin configuration and functions for each package option.

    For interactive pin assignment, I also recommend using SysConfig. SysConfig can automatically resolve pinmux settings based on the selected peripherals and device/package, and it generates the corresponding configuration code for MSPM0 SDK projects.

    Regarding the Excel pin mapping sheet: this is not currently posted as a public download on the product page. In the prior E2E thread you referenced, the sheet was provided directly by email rather than attached publicly to the forum. I recommend following up with your field contact to get this to you in a timely manner. Hope this helps!

    -Brian