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.

TMDXIDK5718: AB9 pin Function

Part Number: TMDXIDK5718
Other Parts Discussed in Thread: AM5718

Hi Team,

Need your inputs on this. From our initial checks the AB9 pin on the TMDXIDK5718 seems to be the PRU receive interface pin used by R31 register. D26(uart2_txd) and AB9 seems to work like a loopback. But connecting D26 with D28(uart2_rxd) seems to be the way to go in making a loopback.

Can you help us clarify with our customer the function of AB9 pin in the TMDXIDK5718? Thanks in advance!


Kind Regards,

Jejomar

  • Hi,

    Each pin function is configured by MUXMODE in pinmux register.

    You can refer to the datasheet to see what is the available function configured for pin AB9.

    I assume you are trying to create a loopback for UART2 (RX <-> TX). It is fine to use D26 and D28 given that you configure the pinmux for those 2 pins as UART_RX and UART_TX respectively.

    For more information about pad configuration, please refer to technical reference manual Ch18.4.6.1 Pad Configuration.

    You can find datasheet and TRM from AM5718 product folder at ti.com.

    Regards,
    Stanley

  • Hi Stanley,

    Many thanks for looking into this! We've shared these to our customer and we have quite understood MUXMODE. In the AM571x EVM, AB9 is written ” MCASP5_FSX/PR2_PRU1_R31_2” . So I think the function of AB9 is PR2_PRU1_R31_2(PRU1 R31 Input), which we refer to "Table 30-2 PRU-ICSS2 I/O Signals" in page 7212 of TRM. However can you help us further clarify with our customer and help understand what purpose AB9 is set to PRU1 R31 Input?


    Kind Regards,

    Jejomar

  • Hi,

    It is basically 2 level of mux.

    At the first level, PRU mux can select which signal to connect at PRU boundary.

    The second level, PAD config can select which signal (from PRU, UART, or GPIO) to go out at the SoC boundary.

    Regards,

    Stanley