• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 79 subscribers
  • Views 1191 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Using PinMux - no port numbers?

Kevin Keegan
Prodigy 30 points


Trying to use on-line PinMux to select timer outputs to specific PORTS on MSP432401R launchpad.

It appears one get to select specific PINS on the processor to which to connect a timer output.

However without more work - I don't see how one knows which PORTS each pin represents.

Remember - the boards have the PORTS (e.g. 1.2, 1.3, etc) silk screened at the connectors - not the processor pins numbers.

Am I missing something (could be - I'm new)?

Do we really have to go to ANOTHER document to see what PORT is connected to what PIN before we place a timer output on a PIN?

  • 0
    TI__Guru**** 219717 points

    Hello Kevin,

    After adding a peripheral you can view the generated files on the right-hand side of the PinMux tool (baremetal_pin_mux_config.c, driverlib_pin_mux_config.c, PinmuxConfigSummary.csv) to see the correlation between pin number, port designation, and assigned functionality.

    A getting started video is also provided for the PinMux Cloud tool:  

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 30 points

    Hello Ryan, thanks for response.

    Short ans: I think a feature is missing: being able to easily know what port.bit one is picking when one picks a pin. This could be easily improved by making the “pin” list dropdown include the “other information” about that pin (port.n, other fixed functions, etc).

    Use case: I want to assign a timer output signal to a P2.1 (if possible or other possible) labelled on the 432 LaunchPad header. Not easy to find what port.bit and 432 pin numbers are POSSIBLE for given timer output.

    Please correct me if I misunderstand.

    Kevin

    Ryan Brown1 said:

    Hello Kevin,

    After adding a peripheral you can view the generated files on the right-hand side of the PinMux tool (baremetal_pin_mux_config.c, driverlib_pin_mux_config.c, PinmuxConfigSummary.csv) to see the correlation between pin number, port designation, and assigned functionality.

    A getting started video is also provided for the PinMux Cloud tool: (Please visit the site to view this video) 

    Regards,
    Ryan

    Ryan Brown1 said:

    Hello Kevin,

    After adding a peripheral you can view the generated files on the right-hand side of the PinMux tool (baremetal_pin_mux_config.c, driverlib_pin_mux_config.c, PinmuxConfigSummary.csv) to see the correlation between pin number, port designation, and assigned functionality.

    A getting started video is also provided for the PinMux Cloud tool: (Please visit the site to view this video) 

    Regards,
    Ryan

  • 0 in reply to Kevin Keegan
    TI__Guru**** 219717 points
    Hi Kevin,

    For your case you would either hover over the pins shown in the Pin Layout diagram until you found the port number you are looking for or reference the MSP432 datasheet to figure out what the pin number is for P2.1 (17). You would then use the PinMux Requirements tab to see if pin 17 can be mapped to the TIMER_A peripheral (it can be).

    Regards,
    Ryan
  • 0 in reply to Ryan Brown1
    Prodigy 30 points

    Hello Ryan, 

    Thanks again for your response.

    Yes- I understand how this must be (slowly) done with the tool as is.

    Hope you agree it would be simple / very much a user time saver to incorporate the suggestion I made.

    I'll mark this answered.

**Attention** This is a public forum