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/CC3220SF-LAUNCHXL: CCS/CC3220SF-LAUNCHXL: Error connecting to device

Part Number: CC3220SF-LAUNCHXL
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

I'm trying to push the sample Amazon FreeRTOS IoT example using Publish / Subscribe.  I've successfully compiled via Composer and ready to run the application.

Note: I originally tried using the supplied TI IoT plugin sample application, but had compilation issues with that solution.

Now that I've got things compiling, I attempted to run the sample application and am failing on running in Debug with the following error:

---

CS_DAP: Error connecting to the target: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed. The cause may be one or more of: no XDS110 is connected, invalid firmware update, invalid XDS110 serial number, or faulty USB cable. The firmware and serial number may be updated using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of your installation. View the ReadMe.txt file there for instructions. (Emulation package 8.0.27.9) 

---

I tried using the Test Connection via Composer and got this error.

I made an attempt to possibly update the firmware via UniFlash.  I have it installed on Mac OSX and it gives me the following error when attempting to Connect.

So far, I'm really close from getting this to get things to push to the device, but having difficulties connecting to this device.  I'm using a Mac, but it seems even via UniFlash I can't connect.

Is it that I need to upgrade the firmware?  If so where is that located or do I need to download a bin or service pack file.

We just purchased the device and the box has a seal date of 03/16/17

  • Hi Nick,

    Yes, it seems like your computer is having trouble communicating with the XDS110 that is built into the LaunchPad. UniFlash ImageCreator uses the XDS110 behind the scenes for programming the CC3220x devices, so both failures probably have the same root cause.

    What we will probably need is to get the firmware version of the XDS110 on the board updated. This will be through a different utility (not UniFlash). There are some instructions here:

    processors.wiki.ti.com/.../XDS110

    It is recommended that you perform the update with a Windows host if possible.

    Do you have access to a Windows host? Also, can you share your exact Mac OS version?

    I'll check with our tools team to see if you might run into any issues updating with your Mac.

    Best Regards,
    Ben M
  • I don't directly have a Windows machine, but I'll get access to one and try it.

    It would be great to get this working on a Mac with UniFlash and/or Composer since I'm predom

    I wonder if a virtual machine will running Windows on a Mac will work.  Any thoughts?

  • Hi Nick,

    We should be able to get it working on the Mac. I just want to make sure that the XDS is at the latest firmware version in case any bugs relating to the Mac OS were fixed. The Windows machine will give us a better starting point.

    Can you please provide your exact Mac OS version?

    Thanks,
    Ben M
  • Sorry about that.

    OS X 10.13.5

    There is a 10.13.6 update available that I haven't upgraded too.  If you think that'll help let me know and I'll upgrade.

    I'm working with a local TI rep on the side if needed.

  • Hi Nick,

    No worries. I checked on the possibility of using a Virtual Machine - this will not be a reliable approach. There can be timing issues that occur due to the virtualization.

    I see you mentioned that you have a direct TI contact. If you can't get access to a Windows machine on your own, see if your TI contact can help you get the firmware updated. I'll also get in contact with him to see how we can help support you with that.

    Best Regards,
    Ben M
  • Ok, I downloaded and installed CCS on Windows (to get at the command line tools) for the xdsdfu command.

    I ran the "xdsdfu -e" command and it says...

    ---
    USB Device Firmware Upgrade Utility...
    Copyright....

    Scanning USB buses for support XDS110 devices...

    Found 0 devices
    ----

    So far, I haven't see it ever connected. I made sure CCS wasn't running as well possibly causing conflicts? maybe.


    Pin 1 is set on the board if that may be the problem?


    Also, I'm wondering where the bin file is for the right firmware version that I need would help too.

    Thanks again for all of the help.
  • Hi Nick,

    I don't believe CCS running would cause a conflict unless you were already connected to the target. "fimrware.bin" should be an actual file in the ccsv8\ccs_base\common\uscif\xds110 folder.

    Do you not see it?

    By "Pin 1" do you just mean the digital I/O? That shouldn't be a problem.

    What do you see under your ports in your device manager? Do you see two "XDS110 Class ..." ports show up?

    Thanks,
    Ben M
  • Yes, I found the firmware bin file in that location.

    I was changing the SOP pins.  The pin is currently at position 0, but really not sure if that's helping or hurting.  I found some forum thread that suggested moving the pin, but maybe that was for something completely not related.  If I need to switch to the proper location of the SOP pin let me know.

    I'll report back on trying to reconnect and update the firmware via Windows soon.

  • Hi Nick,

    Ah, thank you for clarifying about the SOP pin. Yes, for UniFlash the jumper should be placed on either position 2 or position 1. For using CCS, it should be set to one of the modes that allows for the proper JTAG or SWD mode to be enabled. A full description of what these positions mean can be found in section 5.10 of the CC3220 datasheet.

    www.ti.com/.../cc3220.pdf

    Best Regards,
    Ben M
  • Hi Nick,

    I haven't heard back from you in a while. I'm going to go ahead and close this thread, but you can reopen it if needed by posting a reply. If the thread has locked, please open a new thread and we will continue supporting you there.

    Best,
    Ben M