• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 300 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.

LAUNCHXL-CC1352P: Can't use debug session/COM ports of two LAUNCHXL's at same time

Alex Lin
Prodigy 10 points
Part Number: LAUNCHXL-CC1352P

Tool/software:

Hi,

I am using a CC1352P7-1 Launchpad and a CC1354P10-1 Launchpad, both which appear to have the XDS110 emulator. I need to have both boards plugged into my PC so I can communicate with them via their different COM ports. When I plug in the CC1352, I can see data coming over its port. However, the moment I plug in the CC1354 as well, data ceases on the CC1352's comport (the CC1354 works fine). Both boards' comports are recognized by Windows device manager.

Additionally, when I try flashing/initializing a debug session on the CC1352 when both boards are plugged in, I will either get the following message in CCS:

Error initializing emulator:
(Error -260 @ 0x0)
An attempt to connect to the XDS110 failed.
The cause may be one or more of: no XDS110 is connected, invalid
firmware update, invalid XDS110 serial number, or faulty USB
cable. The firmware and serial number may be updated using the
xdsdfu utility found in the .../ccs_base/common/uscif/xds110
directory of your installation. View the XDS110SupportReadMe.pdf
file there for instructions.
(Emulation package 9.13.0.00201)

or I manage to successfully load code, but this message pops up in the console:

Cortex_M4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.13.0.00201)
Cortex_M4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.13.0.00201)

In this scenario, I can connect to the CC1354 perfectly fine. When I unplug the CC1354 and try to connect to the CC1352 again, it works.

This is the output of xdsdfu -e, right after both boards are plugged in (Device 0 here is CC1352, Device 1 is CC1354):

After attempting to connect to the CC1352, this is the output (it is just the CC1354):

Here are my target configuration options for both boards:

I am not sure what's going on or why this would not work -- any help would be greatly appreciated!

Thank you,

Alex