• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 31 subscribers
  • Views 564 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.

MSPM0G3507：How to set up GPIO pin multiplexing functionality?

Robert Liu
Prodigy 60 points
Part Number: MSPM0G3507
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

嗨，TI

在我的设计中，我将 PA19 引脚用于以下两者：

  1. 监控按钮状态（通常为高电平，按下时变为低电平）

  2. MCU_SWDIO函数（调试的默认高级别）

我需要有关如何在 .syscfg（TI SysConfig 工具）中正确配置此内容以避免冲突的指导。

感谢您的支持！

  • +1
    TI__Mastermind 26575 points

    Hi Robert,

    As this is worldwide formu, please use English as the default language. For Chinese support, you can visit https://e2echina.ti.com/ 

    The reason it shows the error is that you enable dual functions for the single pin, you can disable SWD and then configure its function:

    Important Note: After disable SWD interface, it will be locked with disable untill next BOOTRST. So in development stage, recommend you add some delay before disable SWD interface, then it will reserve a time window for user to re-download the new firmware. Or, you might need some special opeation to connect the device.

    B.R.

    Sal

  • 0 in reply to Sal Ye
    Prodigy 60 points

    Hi Sal,

        Thank you very much for your prompt and helpful response. Your explanation perfectly resolved my issue with the pin configuration conflict.
         I sincerely apologize for the Chinese text in my initial query—I unintentionally submitted the question using a web translation tool. I’ll ensure future communications are in English by default, as required by the forum guidelines. 

    Best regards,
    Robert

  • 0 in reply to Sal Ye
    Prodigy 60 points

    Hi Sal,
        I followed your advice last time and added a delay before disabling the SWD interface, but the programming is not 100% successful.
        What modifications should I make next? I look forward to your suggestions.


        Best regards,
        Robert

  • 0 in reply to Robert Liu
    TI__Mastermind 26575 points

    Hi Robert,

    When it run the application code, it will imediately do initialization and disable SWD interface. The minus delay won't work.

    Unfortunately, after I check TRM, I find it requries POR to reset the SWD property, even if click on the force reset it only generate around 600ms low signal in NRST, which is not sufficient to trigger POR and reset SWD interface:

    So, I recommend you add a large dealy (seconds level), and manually trigger POR before load new firmware (force NRST low more than 1s).

    B.R.

    Sal

  • 0 in reply to Sal Ye
    Prodigy 60 points

    Hi Sal,

        Implementing this functionality with a second-level delay may not be easy to achieve during batch programming in the factory. I want to enable the programming function through an instruction, and I've added the following program to the example:

    The reason is based on the settings in the chip manual：

    I want to achieve the ability to perform batch programming through button presses or instruction settings, so that colleagues in the factory can do it. However, this method has failed. After I pressed the button and completed the programming:

    I wonder if you have any other methods. I look forward to your guidance.

     
    Best regards,
        Robert

  • +1 in reply to Robert Liu
    TI__Mastermind 26575 points

    Hi Robert,

    After you disable SWD port, you need generate POR reset to let it recover. So, enable it in software code does not help on the case.

    Sal Ye said:
    Unfortunately, after I check TRM, I find it requries POR to reset the SWD property

    My suggestion is that check a pin status to design whether disable SWD or not after device power up, so that you can set a unique pin status and then make the device programmable in the factory.

    B.R.

    Sal

  • 0 in reply to Sal Ye
    Prodigy 60 points

    Hi Sal

    In my design, I am using the PA19 pin for both:
    monitoring the key status and MCU_SWDIO.

    My current idea is to enable SWD in .syscfg, then use a timer to delay for 2-3 seconds, disable SWD, and finally configure PA19 as a key input pin via code.
    I want to know if there might be any conflicts between these operations.

    Thank you for your assistance.

    Best regards,
        Robert

  • +1 in reply to Robert Liu
    TI__Mastermind 26575 points

    Hi Robert,

    This looks good.

    B.R.

    Sal