I plugged my SensorTag CC2650 and DevPack Debugger together and got them working in CCS 6.1. However, SmartRF Flash Programmer 2 v1.6.2 cannot seem to recognize if fully. It detects the XDS110 part, but not the CC2650.
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.
I plugged my SensorTag CC2650 and DevPack Debugger together and got them working in CCS 6.1. However, SmartRF Flash Programmer 2 v1.6.2 cannot seem to recognize if fully. It detects the XDS110 part, but not the CC2650.
Hi JXS,
I tried the suggested solution in that link (disconnect USB, remove battery, insert battery, insert USB) but it did not work. Can you think of any other possible solutions?
I don't think it's in the FW Upgrade Mode since I've had that problem before and I solved it by following the CLI procedures from: e2e.ti.com/.../432761
After following the procedure, CCS was able to correctly detect the debugger:
Full output here: http://pastebin.com/raw.php?i=GKnMMQgW
There are two USB devices associated with the DevPack, a data transfer port and a debugger, so maybe only the debug probe is working and the data port is still stuck in FW Upgrade Mode?
Hi,
I'm having the same problem, and the above procedure didn't work for me either. I have the SmartRF Flash Programmer 2 version 1.7.0.
In Windows Device Manager the DevPack is shown correctly (I think):
The SensorTag has firmware version 1.12 running, which I installed through the Android app's OAD feature.
cheers
-Mikko
I had the same problem recently
https://e2e.ti.com/support/wireless_connectivity/f/538/p/435274/1612764#1612764
I am using a self-implemented copy of the LAUNCHXL-CC2650 In this design I have wired JTAG from the '1294 debugger uP directly to the CC2650 without the '245 lever translator/buffers.
Thanks YiKai. I had already verified the items under Initial Board Bringup. Skipping CMD_PING, I am now at this step: "To rule out any IDE (IAR/CCS) related issues, use SmartRF Flash Programmer 2 with a supported debugger to check whether the device can be recognized or not. "
I verified activity on TRESET, TMS and TCK. Comparing the behavior of the circuits, the XDS110 on my board (top two photos) TMS and TCK go high and remain high for 1 second after TRESET releases on USB connection. By contrast, the CC2650 Launchpad produces a TMS high-going pulse of 50ms after reset releases and TCK remains low for 1 second before communication begins. It seems that target identification requires only TMS and TCK and only happens at power on. This behavior coupled with the XDS110 revision 2.3.0.1 to 2.2.5.1 makes me think the XDS110 firmware could be the problem.