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/LAUNCHXL-F280049C: Errors while using XDS110 Debug probe

Part Number: LAUNCHXL-F280049C
Other Parts Discussed in Thread: C2000WARE

Tool/software: Code Composer Studio

Hello,

I have just received the LAUNCHXL-F280049C launchpad. The launchpad uses XDS110 debug probe. I have connected the launchpad and observed the factory loaded code output. Then I have changes the settings of boot mood switches for SCI boot to load the led blinking code, then the debugger told to update the firmware and I have updated it. Then I have again tried to debug but receiving error shown in image_1. Then I have open the target configuration file and changed the properties in advance settings for XDS110. (please refer image_2). It also not working and giving same error. 

After that I have changed the probe from XDS110 to XDS560 debug probe,2-pin cJTAG withe external converter. That has started giving new error (refer image_3). Then I have referred the "XDS110 Support Notes" and executed the commands mentioned in that document, still receiving the same errors. In XDS110 Support Notes it is mention that use the 2.3.0.15 or 2.3.0.17 version and not the 2.3.0.16. But in my case its 2.3.0.16. please find (image_3). 

Please tell how to solve this problem. This issue is creating delay in our system development. 

Please tell which debug probe should be selected in target configuration file. 

Regards,

Nisha

  • Nisha,

    The XDS110 is the correct probe to select in the target configuration file.  

    Do you know what version of the TI Emulators feature is installed?  There is an issue with F28004x and some versions of that software.  If you go to Help -> About in CCS and then select Installation Details you can see the version:

    If you are just getting started with CCS  I would suggest using CCSv9.0.1 as it has that issue corrected.

    Regards,

    John

  • Thank You John!

    It worked with CCS V9 and using XDS110 cJTAG 2 pin advanced mode in target configuration file. 

    Thanks & Regards, 

    Nisha Gosavi

  • John,

    When I import code in CCS V9 from C2000ware for F280049C, it has XDS100 configuration by default in target configuration and every time I have to change that file. It was never seen previously . Why is it so for F280049C ?

    Nisha

  • NIsha,

    I just imported one of the F280049C examples as well and it has the debug connection set as XDS100v2.  That is just the way the examples have been setup.  Likely because historically the C2000 LaunchPads used XDS100v2's on them.  Given that this LaunchPad has the XDS110 on it the examples really should use that instead.  I will inform the C2000 team.

    Regards,

    John