LAUNCHXL-CC1352R1: XDS-200 Debugger

Try the CTI20-ARM10 since I believe we use the ARM10 connector on the Launchpad.

Hi TER,

Thanks. ARM 10 connector worked.

I have a couple of question, 

I get a firmware update warning while flashing the code and when clicked on Update I see the following error even though only one XDS200 probe is connected ->

When I click on Retry (Proceed without the update), It works properly. But trying to update the package doesn't work and eventually brings back the pop up in the screenshot.

I even tried the command line update functionality which is given in the following link - https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds200.html#updating-the-xds200-firmware

But I got stuck on step 3. 

I can't figure out what I am doing wrong here, any help on the above is appreciated?

2) I aim to use Energy trace ++ functionality and with this XDS200 debugger, for which i followed this link-> (http://dev.ti.com/tirex/content/simplelink_cc13x2_sdk_2_30_00_45/docs/ti154stack/html/energy-trace/energy-trace.html)

But when I go in the EnergyTrace section (Windows -> Code Composer Studio -> Advanced Tools -> EnergyTrace Technology), In the drop-down for selecting the Target configuration, I am not able to see XDS 200 (Screenshot below).

Even in the Energy Trace window, the EnergyTrace++ option is disabled. 

Is it possible that ques1 and ques 2 are interrelated?

If not, how can I enable the Energy Trace ++ functionality?

Thanks and Regards,

Yash.

1) Do you only have CCS running on your PC and not SmartRF Studio, Flash Programmer 2 etc? 

2) I'll check

2) Have you checked that XDS200 actually supports EnergyTrace? I found no indication that this is the case when I did a quick search. 

Hi TER,

1) Only CCS is running.

2) I looked into Energy Trace and found that the debugger must be set to 4-pin cJTAG mode. Since I had an XDS 200
and it provides 4-wire interface, I though it would work.

As you mentioned, you found no indication that XDS200 actually supports EnergyTrace. Is there any specific reason for that?
And what would you recommend instead?

Thanks and Regards,
Yash.

Looking more into it, I found this ->

So, according to the above screenshot, XDS110 is capable of supporting EnergyTrace++. But while doing so I am getting the following error.

As the above error suggests, I changed the pin mode to 4pin Standard mode in Target Configuration -> Advanced -> JTAG Mode.

I got a different error saying ->

Can you point out where I might be going wrong and how can I make ET++ work with on-board XDS110?

Thanks and Regards,

Yash