How to map Port-Style Pins (i.e. PTE15) to MPC5777C 416-ball Pins (i.e. AD21)

cancel
Showing results for 
Search instead for 
Did you mean: 

How to map Port-Style Pins (i.e. PTE15) to MPC5777C 416-ball Pins (i.e. AD21)

489 Views
rsating
Contributor III

In the MBDT for the MPC5777C MCU, for configuring peripherals, for example in SPI_Config below, pin names have port-style names (i.e. PTE15, PTN20, PTC30, PTH16)

MBDT_SPI_Config_mpc5775C.png

However, the 417-Ball MAPBGA diagram for MPC5777C use a different naming convention (i.e. AD21, AE22, AE23, etc)

NXP_MPC5777C_417-Ball_MAPBGA.png

Also, the S32DS SDK example "PDC_5775B_SDK_Z7_0" uses the same convention as the 417-Ball diagram in Component Inspector for Routing and Functional Properties as shown below:

S32DS_PDC_5775B_SDK_Routing_DSPI.png

S32DS_PDC_5775B_SDK_Func-Prop.png

The same naming convention is used for the pins in the schematic in RDVCU5775EVM_SCH.pdf

RDVCU5775EVM_SCH_MCU-pins-snippet.png 

Given the different naming conventions, how do we know which pins to choose in MBDT?

Is there a cross-reference that could help connect the name spaces?

0 Kudos
1 Reply

480 Views
rsating
Contributor III

I eventually noticed noticed the translation is as follows:

PH[11] --> PTH11
PH[12] --> PTH12
PH[13] --> PTH13
etc.

It was easy to miss this when looking if one is in a hurry.

So the SDK example in the MPC5775 EVM User Guide holds the key to mapping MBDT pin names to those used on the schematic and the microcontroller data sheet. 

Still, it would be nice to have an excel worksheet or other cross-reference for this.

0 Kudos