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.

CCS6 and selecting 1 from multiple CC3200XL attached

Other Parts Discussed in Thread: CC3200

I am using latest version of CC6 on Windows 8.1 I have 5 different CC3200 LaunchPads (each have different sensors) attached at the same time to my development machine. When a new version of cose is built, it is done for all 5 different.build configurations.

The problem comes up when I try to start an interactive debug sessions with a specific Launchpad, up to now I have had to unplug all the "extra" devices, exit CCS and then restart CCS to get it to select the single remaining attached Launchpad.

This is becoming a MAJOR problem since every time I detach them they restart and all history and logs are lost.. I have now placed a separate powered USB hub in between the dev machine and 4 of the LaunchPads, this way I can unplug the 4 devices without them rebooting.

The problem now is that unplugging the USB hub also terminates the MultiTab Putty connections to these 4 launchpads, and all console status/error messages are lost.

Is there ANY WAY that all the launchpads can remain connected and that the specific COMxx used can be selected at debug session time?

Thanks

  • Hi,

    Unfortunately no. CC3200 launchpad uses ICDI as its JTAG debugger, but multiple ICDIs cannot be used at the same time.

    Reference:
    e2e.ti.com/.../686354

    I apologize for the inconvenience,
    Rafael
  • For those that are interested, I have found a solution. I am using a SILEX DS-510 USB device server and the SX-Virtual Link software. With this solution up to 14 devices can be connected using 2x 7-port USB hubs connected to the 2x USB ports on the DS-510.

    With the software provided any specific device connected to one of the ports can be selected. The device will be recognised by CCS and used for debugging. It will also allow the LaunchPads to be accessed from any of a number of development stations, either local or remote, via the network.

    Only problem is a lack of support for Linux, and the current software does not support OSX El Capitan.

    All in all, a superb solution.