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.

TMDSEMU110-U: debug UART communication

Part Number: TMDSEMU110-U
Other Parts Discussed in Thread: TMDSHSECDOCK, SYSCONFIG, ENERGYTRACE

I am using an XDS110 debug probe along with an AM263x control card. Currently, I am not using the auxiliary connection pins, and the debugger is connected through the 14-pin JTAG.

One thing I observed is that if a debug UART is needed, then auxiliary connections are required, Please correct me if I am wrong. However, I'm uncertain about the purpose of these two connections

  • One thing I observed is that if a debug UART is needed, then auxiliary connections are required

    That's not correct. Debug UART uses the USB bridge. You can see that in the block diagram of the CC manual:

    To use Debug UART you open a Terminal in CCS and select (in your case) COM18. For more information, see User Guide (ti.com) 

    I'm not 100% sure but I guess the COM17 device is for the JTAG debug access.

  • Here the UART0 is connected to onboard debugger right? I have tried with onboard debugger it is working fine. But I am trying to communicate with the debugger connected to the docking station 

    using onboard debugger the console will print the output like this

    Moving onto external debugger probe console is just empty

  • By default, Debug UART works through UART0 so you (also) have to connect a USB cable to the micro-USB connector regardless of the debugger you're using.

  • Thanks that resolved my doubt, still that is going through COM15 what is the purpose of COM18

  • Apologies. I got this completely wrong since I did not read your question properly.

    When you said "XDS110 debug probe along with an AM263x control card" I incorrectly assumed you meant the onboard XDS110 but you mean the external debugger (TMDSEMU110-U) in combination with TMDSHSECDOCK.

    Let me try again.

    One thing I observed is that if a debug UART is needed, then auxiliary connections are required

    Now that I have read the manual, I agree. You do need the Auxiliary connections of the TMDSEMU110-U, pins 12 and 14.

    If you wanted to use those connections you would need to choose a different 'Debug Log' UART which maps to HSEC pins instead of the default UART0 in the SYSCONFIG which maps to the onboard USB bridge.

    Of course this means extra wires on your TMDSHSECDOCK where this would not be necessary if using the onboard UART0 / micro-USB interface.

    However, I'm uncertain about the purpose of these two connections

    UART(COM18) :This is of course the UART port that you select in the Terminal.

    Auxiliary Data Port(COM17) : I suspect this is used by EnergyTrace feature (and others) judging by the diagram here:

    still that is going through COM15 what is the purpose of COM18

    Since you have connected two debuggers (onboard and TMDSEMU110-U) both with USB/UART interfaces, you will now see 2 x UART COM ports.

    COM15 (onboard debugger USB/UART bridge) will definitely work out of the box but COM18 does not work right now because (presumably) you have not yet connected your selected Debug Log UART HSEC instance to your TMDSEMU110-U Aux interface.

  • Thank you very much Kier that made things much more clear, have a good day.