• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 81 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.

TMS320F28384S: GPIO issue calling InitGpio() twice

luca mattonai
Intellectual 690 points
Part Number: TMS320F28384S


Tool/software:

Hi

I have a strange behaviour with SCIA in polling mode, the problem is present only starting the app from bootloader nor debugging it. The bootloader program SCIA for character i/o then it transfer the app from an external flash to internal ram and jump to the app entry point.

the app setup processor again and setup again SCIA then print the app version on the terminal. Starting from bootloader this will function only if a put a small delay before print the version or I don't call the InitGpio() function in the app, otherwise wrong character are printed out.

Best Regards 

   

  • 0
    TI__Expert 4960 points

    Can you confirm you’re not overwriting the pin configuration for SCIA pins by calling InitGpio()? This behavior is likely due to pin multiplexing and GPIO configuration conflicts between the bootloader and your application. The InitGpio() function typically resets all GPIO pins to default states. If you call InitGpio() after SCIA is initialized, SCIA TX/RX pins may get reset to GPIO mode. You may re-apply your SCIA pinmux configuration after calling InitGpio() to see if it helps.

    Best Regards,

    Masoud

  • 0 in reply to Masoud Farhadi
    Intellectual 690 points

    Hi Masoud

    After calling InitGpio() I set again pinmux and uart settings...

    Best Regards

    Luca