• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 29 subscribers
  • Views 5350 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Missing XDS110 debugger support in CCS 6.01 when using new LaunchPad for TMS570LS12x

Art Mezins
Prodigy 110 points
Other Parts Discussed in Thread: HALCOGEN

I recently got a TMS570LS12X LaunchPad ("hot off the assembly line") and then installed the latest CCS (6.0.1.00040) and HALCoGen (04.02.00).

However, CCS cannot access my new LaunchPad. I traced the problem to the statement "You must have TI Emulators version 5.1.635.0 or later to use the XDS110 emulator." on "http://processors.wiki.ti.com/index.php/LAUNCHXL2_TMS57012:_Project_0". So (apparently) my CCS install did not have the "latest" XDS110 driver. In fact, I cannot determine whether any emulator drivers are installed as none are listed as described in the Wiki info at processors.wiki.ti.com/images/3/3d/Updating_ccs_for_xds110.png as my "installation details" shows no "TI Emulators" section! But it was obvious I have some emulator drivers, since I am able to control my older TMS570LS04x/03x LaunchPad just fine. The TMS570LS04x uses a standard FTDI chip for the USB interface, but the newer TMS570LS12X uses a TI TM4C129 micro instead of the FTDI chip (which must be why THIS is the new XDS110). I have searched all over in as many ways as I can imagine for the new driver but it is nowhere to be found. I've wasted a couple of days on this now.  

Also, when I connect the new LaunchPad, the PC device manager shows 4 unknown devices each listed as "XDS110 (02.02.04.00) with CMSIS-DAP" (obviously from the USB installation handshake). The page http://processors.wiki.ti.com/index.php/XDS100 makes no reference to an XDS110 and there is no equivalent wiki page for the XDS110.

So, how do I get the XDS110 driver so I can use my new TMS570LS12X LaunchPad?

UPDATE: I found the link to the new drivers here: "http://software-dl.ti.com/dsps/forms/self_cert_export.html?prod_no=ti_emupack_setup_5.1.636.0.exe&ref_url=http://software-dl.ti.com/dsps/dsps_public_sw/sdo_ccstudio/emulation". 

After installing that I now had the XDS110's four drivers. Two are under Ports:

XDS110 Class Application/User UART (COMx)

XDS110 Class Auxiliary Data Port (COMy)

 Two are under Texas Instruments Debug Probes:

XDS110 Class Data Port

XDS110 Class Debug Probe

However, when I tried to change my project settings from XDS100 V2 (which I used on the TMS570LS04x/03x project and was the default on this one before I found out I needed XDS110) there is still no XDS110 listed in the choices. So, I "guess" I only made Windows happy, but something the corresponding plugin for the XDS110 which "may" to be related to a missing .CCXML file if my guess is right (I am completely new to the Eclipse platform which has way too many "knobs").

When I posted this somewhere else (and was told to repost here) someone indicated that I should have an XDS110 folder in my C:\ti\ccsv6\ccs_base\common\uscif folder (since I used the default tool path), but I don't. They also said: " There should be a file 'dbgjtag.exe' in this folder. You can right click on it in windows explorer and bring up the file properties. On the "Details" tab of file properties, you can see the version listed in 'Product version'." I did that and it shows "File version 35.34.40.0, Product version 5.1.507.0" for what it's worth.

So the updated emulator package did not update CCS and I still can't load & debug any code on my new launchpad (which I need since THAT is the one I need to use on my "real" project).

  • 0
    TI__Guru 65600 points

    Art,

    Sorry to hear you're having this much trouble.

    5.1.507 wouldn't have support for the XDS110.

    I think you got the correct package from the TI download site, although the link doesn't work for me so I can only go by the name of the .exe:  ti_emupack_setup_5.1.636.0.exe.

    This isn't the 'expected' way for you to get the update.  You should have been able to get the update through CCS by asking it to "Check for Updates".

    But it's OK to use the standalone installer,  it's just *tricky* because the default directory that the standalone installer picks is wrong.

    It picks "C:\ti" by default and if you used that then I think you will see a folder "C:\ti\ccs_base" which is where the install went.  You can/should delete this folder.

    It needs to be changed to install to C:\ti\ccsv6  and you have to add the ccsv6 manually... since you are running  ti_emupack_setup_5.1.636.0.exe. 
    (If you let CCS run it through the update process it would handle the directory fix for you...) 

    I think if you try again, but pick CCSv6, you will be ok.  

    It is definitely important that your update process works, because we also release new device XML files for Hercules MCUs periodically.  Are you having trouble perhaps w. the proxy settings (are you behind a firewall when you try to update?) 

  • 0 in reply to Anthony F. Seely
    Prodigy 110 points
    Manually coping the stand-alone emulator driver files into the CCS 6 path fixed the issue with this driver.

    I guess I still have issues relating to our firewall to address here. I never found out what ports are used for updating so that I might get the IT guys to unblock those ports to allow updates. One more possible twist is that when I installed CCS, virus scanning was on since I am not "permitted" to disable it.
  • 0 in reply to Art Mezins
    TI__Guru 65600 points
    Thanks Art, glad to hear you got past this for now.
    Still sounds like you need to get the update issue resolved though, or you'll fall behind again.

    Just looking at it quickly I think the download link you posted and the update site are on the same basic url, http://software-dl.ti.com/ <something> so if you could download manually through your web browser, then CCS should be able to also (without being blocked by your firewall).

    I think the issue is just that you need to setup the proxy settings in CCS. processors.wiki.ti.com/.../Updating_CCSv6 (scroll down the page to the section on proxy settings). Should be able to use the same settings that your web browser uses (the browser you used to download manually)