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.

MSP Touch Pro GUI with other COM-Ports than "MSP430 Application UART" ?

Other Parts Discussed in Thread: MSP430FR5989, MSP-FET

Hello,


Is there a way to use any other COM-Port than the "MSP430 Application UART" to connect a Board with a MSP430FR5989 to the Touch Pro GUI?

I'm using a custom Board, which does not have a wired COM-Port but Bluetooth. Software on the MSP is already adapted to use Bluetooth, in Windows the Bluetooth emulates a COM-Port, and through Putty I verified that there ist actually data coming in through this port.

The Problem is that the Touch Pro GUI does not recognize this port. I refreshed the COM-Port list multiple times (with Putty open and closed). It only shows the two COM-Ports of my MSP-FET tool. Neither the physical COM-Port of my PC, nor the virtual Bluetooth-COM-Port are listed.

Is there any workaraound to get the Bluetooth port working?

Best Regards,

Andreas

  • Andreas,

    It depends on how your COM port emulator is registering itself with the Windows registry. The TouchPro GUI attempts to present the user with a list of valid MSP430 FET USB COM ports. The process it goes through is:

    1. Look through the keys in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB

    2. For each of those keys, find the sub-keys whose "Friendly Name"  contains "(COM". These COM ports are presented as options to the user.

    There is an argument to be made that the tool should just allow the user to enter any COM port number, but the decision was made that most users would prefer a list of known-good options.

    -tim

  • Hello Tim,

    So basically in the current version there is no way to use alternative COM ports?
    It would be a good thing if there was at least a way to override the filtering of the ports. For example a "show all COM ports" button. Considering that this software is intended for hardware designers one could expect the users to bear the added complexity.

    I'm using bluetooth to rule out common mode errors, and I guess others might try to do similar things. For now I hacked together my own tool to analyse the data, but maybe you guys can add that feature in future versions.

    Best Regards,
    Andreas
  • Andreas,


    I have submitted this as an enhancement for the next version of the tool.

    Thanks for using TI.

    -tim

**Attention** This is a public forum