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.

TMS320F28388D: GPIO muxing and XBAR settings - before or after peripheral initialization?

Part Number: TMS320F28388D
Other Parts Discussed in Thread: SYSCONFIG

Hello TI Tech Support,

To avoid IO glitches, it appears to me that it would be good practice to configure the GPIO muxing and XBAR settings for INPUTS before a peripheral is initialized, and to configure GPIO serving as OUTPUTS only after the peripheral has been initialized.

Would you concur, and does TI provide any specific guidance for given peripherals?

Also, in case of a dual-core device, such as the F28388D, are there are any recommendations in terms of when CPU1 should be making GPIO muxing and XBAR configurations for a peripheral that is assigned to, and initialized by CPU2?

Thank you in advance,

Beat

  • Would you concur, and does TI provide any specific guidance for given peripherals?

    This is ALWAYS application specific. Sometime people like to configure the PINMUX first, then configure the peripheral. Most times this is the case. But there are times that users configure a peripheral, run the peripheral, then switch the pinmux. But yes what you mentioned is a very common usage.

    Also, in case of a dual-core device, such as the F28388D, are there are any recommendations in terms of when CPU1 should be making GPIO muxing and XBAR configurations for a peripheral that is assigned to, and initialized by CPU2?

    Again, usually, the pinmux is assigned to peripheral, then to CPU2. Then after that CPU2 configures and uses the peripheral.

  • Hi Nima - thank you very much for your response.

  • Beat,

    Have you tried the C2000 SysConfig that can generate your initialization code for you? It would help setting up the device faster.

    Nima