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.

CCS/EK-TM4C1294XL: CCS 7.3.0.00019 under windows 10 can select the wrong COM for SWO Trace receiver when XDS110 and XDS200 connected

Part Number: EK-TM4C1294XL

Tool/software: Code Composer Studio

On a windows 10 PC running CCS CCS 7.3.0.00019 with TI Emulators 7.0.48.0 had a XDS110 and XDS200 connected:

With the XDS110 connected to a EK-TM4C1294XL attempted to use the hardware trace analyser with SWO Trace, but no data was captured.

On looking at the Advanced Properties found that CCS has selected COM15 for the XDS110 SWO Trace Receiver, but COM15 is actually for the XDS200:

Manually changing to select COM30 as the COM port then allowed the hardware trace analyser to collect data.

When there are multiple debug probes connected which support SWO Trace, should CCS by default select the COM port for the SWO Trace for the debug probe which is being used for the active debug session?