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.

LAUNCHXL-F28377S: 40-PIN CONNECTION

Part Number: LAUNCHXL-F28377S

I can't understan Gautam's reply comparing with

  • Hi,

    First of all let me link others to this thread to get the background: e2e.ti.com/.../572808

    You are missing few more headers J5, J7 and J6, J8.
    Also, I would suggest you to refer the schematics to get the complete the header details and map the SPI modules accordingly.

    Regards,
    Gautam
  • Thanks for your support. I have checked the schematics according to your instruction and have some questions: in the schematics GPIO 16, 17, 18, 19 are indicated Timer Capture, GPIO66 is I2C, GPIO69 I2S, GPIO71 analog In, What do these indications mean?
  • Please refer datasheet for Muxing details. The Pin naming on the launchpad schematics uses only one Muxing scheme.
  • Because it's multiplexing scheme it's difficult to figure out which pin is reserved i.e. users can't configure. Can you provide me with a easy source?
  • Jingtai,

    The tables in the launchpad user guide show you which pins are available at each position of the BP headers. anything that isn't power or ground, or NC is connected to the MCU. You can verify this by looking at the schematic embedded in the User Guide. Basically, if the pin is a GPIO or ADCIN , it has some level of configurability.

    For example in Table 2 of the User Guide, GPIO16 is shown on J4, pin 36. The Table shows some of the possible muxing configurations such as SPISIMO, CANTXB, and OUTPUTXBAR7. You can cross-reference the F28377S Data Manual for the complete Muxing table. Using that table, you can see that EPWM9A, SD1_D1 and UPP-D6 are also available on that pin.

    The F28377S device does have many GPIO muxing options for most GPIOs, perhaps only showing a subset of the available options can be confusing. I will take this as feedback and see if it can be improved.

    Does this help?

    Thanks,
    Mark
  • I've got it after your explanation. Otherwise I would take long time to figure out. Thank you very much.