• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 14412 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.

CCS: How to install XDS100 driver without installing CCS

Li-Lynn
Prodigy 170 points
Other Parts Discussed in Thread: CC3200

Tool/software: Code Composer Studio

Hi,

The XDS100 installation instructions on TI wiki says installing the CCS will install the XDS100 driver, but is there any other way to install the XDS100 driver? I do not want the CCS be installed on PC, I just need the XDS100 driver so that my PC application can detect and talk to the board with a CC3200 on it, via USB.

Thanks!

  • 0
    TI__Guru**** 162895 points
    Li-Lynn,

    Instead of installing CCS you could install the XDS Emulation Software Package:
    processors.wiki.ti.com/.../XDS_Emulation_Software_Package

    Regards,
    John
  • 0 in reply to JohnS
    Prodigy 170 points

    Hey John,

    I did try to install the XDS Emulation Software Package, but it also included many other drivers right? What if i just want the XDS100? Or, can you point me which files inside the package are essential for detecting and communicating with the CC3200 launchpad?

    Thank you very much! :)

  • 0 in reply to Li-Lynn
    TI__Guru**** 162895 points
    Yes the package would include the support files for other probes like the XDS110, XDS200, Stellaris ICDI and XDS560 as well as files for various different device architectures.

    Note that the CC3200 has a version of the ICDI debug probe on it and not the XDS100. They are both based on the FTDI chip but use different software.

    I do not have a list of files that would be required. I would suggest stripping out groups of files at a time and checking after each group that things still work.

    For example you could remove all files with 560 in the name from the \drivers folder. In the \gel folder you could remove all files for devices other than the one you are using. In the analysis\bin folder you should be able to remove the decoders. In \tpi you could remove the tpi and disassembler files for architectures other than the one you are using.

    John