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.

CC3220SF-LAUNCHXL: Cannot Connect to Target/ Security Error

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

Hello all,

I've recently been working with the CC3220SF-LAUNCHXL. I've been testing/ and debugging my program from CCS7 without any issues, but yesterday, I tried to connet to the board, but I got the following error in CCS7:

Error connecting to the target:
(Error -241 @ 0x0)
A router subpath could not be accessed.
A security error has probably occurred.
Make sure your device is unlocked.
(Emulation package 7.0.48.0)

I also tried to use Uniflash to erease the memory, but I get the same message. Nothing changed software-wise from when the board was working to when it stopped, the only issue is that I was probing around with an oscilliscope, and I'm worried that I might have caused some kind of hardware failure.

Anyone have a solution for this issue?

  • Hi Mike,

    For a quick sanity check, lets put some known good code with known good project configuration on the device. To do so, open Uniflash and:

    1. Click on Manage Projects
    2. Select Import Zip
    3. Navigate to C:\ti\simplelink_cc32xx_sdk_1_40_01_00\examples\rtos\CC3220SF_LAUNCHXL\demos\out_of_box\uniflash
    4. Select OOB_SF_tirtos.zip
    5. Then connect and flash the device as normal

    If this works successfully, please try debugging your code again to see if problems persist.

    Sincerely,
    Bryan Kahler
  • Hi Bryan,

    Thanks for the suggestion. Unfortunately I tried that but it didn't work. I get the same exact message.

    Thanks again,

    Mike

  • Hi Bryan, your instructions helped me to find out that my board and debugger do work properly.

    With Uniflash this all worked out perfectly fine, but I get problems doing so with CCS. When CCS tries to connect to the target during the debugging starting procedure, it says I should do an update (see the picture I added). When I start the update it says it is unable to connect to the target and I get error -265. What am I supposed to do now?

  • Hi Markus,

    1. Are you getting the same error on other USB ports or with other USB cables?
    2. Try debugging with CCS Cloud and see if you get the same error. This is an easy way to test with another computer as well to see if the issue is your setup or your LaunchPad.
    3. If you have another LaunchPad around, test that as well with your setup.

    Best regards,
    Sarah
  • Hi Sarah,

    the only hope I still have left came up when you answered my question.

    I am completely frustrated, spent about 5 hours with no outcome... I've never had any problems like that with other boards, and I've used quite a few so far.

    1.) I tried every single port on my laptop, also with another USB cable

    2.) I tried this now. TI Cloud recognizes that I have a CC3220SF connected which at least something. I opened a new project for my MCU. Now when I hit the debug button I get the following message:  "Debug Failed. The project does not have target type." When I click on "Target --> Connect COM port..." I get the same message "no target type".

    3.) I don't have another one, but I could ask for another one if nothing else helps. But I'm pretty certain that my board isn't the problem since I was able to flash a program with Uniflash, I had zero problems doing this. CCSv7 is the problem I think. I installed CCSv6 for checking if my problem still exists with this version. Surprisingly the connection worked (verify succeded when opening a new project), but CCSv6 was no possibility since I couldn't pick CC3220SF when opening a new project (there was only CC3200).

    When I hit the "verify" button when opening a new CCS project I get the following answer from CCSv7:

    (selected CC3220SF_SWD (Wireless Connectivity MCU)

    This error is generated by TI's USCIF driver or utilities.
    
    The value is '-260' (0xfffffefc).
    The title is 'SC_ERR_XDS110_OPEN'.
    
    The explanation is:
    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.

    Thanks for helping me Sarah!

  • Talking about drivers, I forgot. I installed the XDS110 windows drivers, like it is told to in the How to get started guide. I now uninstalled it, tried it again, didn't work. Installed it again, didn't work either. Just so you know.
  • Sorry I don't know how to edit my posts. The error message from above is when I try to verify the debugger a second time, or third and so on. The first time trying to verify I get this error:

    This error is generated by TI's USCIF driver or utilities.
    
    The value is '-265' (0xfffffef7).
    The title is 'SC_ERR_XDS110_AUTO_FAIL'.
    
    The explanation is:
    The firmware updater encountered an error and could not finish. Unplug
    and re-plug the XDS110, and try again. If the problem remains, try
    updating the firmware using the xdsdfu utility found in the
    .../ccs_base/common/uscif/xds110 directory of the CCS installation.
    View the ReadMe.txt file there for instructions.
    
    [End]
    

  • I also tried what it says in the error description. This is the output. Funny thing is, if i put this command in a second time, I get the message that the requested device was not found on the bus.

  • Hi Markus,

    Have you tried debugging your LaunchPad on another PC? This can be done with CCS Cloud.

    If your LaunchPad works with another PC:
    1. Restart the PC that isn't working (Always step #1).
    2. Try another USB cable. Be sure you are NOT using a USB hub.
    3. Uninstall CCS (your workspace will still be saved). Reinstall with the latest CCS 7.3.
    4. Try the Host Connection error troubleshooting steps here: software-dl.ti.com/.../ccsv7_debugging_jtag_connectivity_issues.html
    5. Uninstall and reinstall the XDS drivers from the Device Manager.


    If your LaunchPad does not work with another PC:
    1. Check that you have the TMS and TCK jumpers in place on the LaunchPad.
    2. Try another USB cable. Be sure you are NOT using a USB hub.
    3. Update the XDS firmware and serial number: processors.wiki.ti.com/.../XDS110
    4. Check out the Security error debugging steps provided here: software-dl.ti.com/.../ccsv7_debugging_jtag_connectivity_issues.html
    5. If all else fails, contact the TI store for a replacement. The firmware on the device may have been corrupted somehow.

    Best regards,
    Sarah
  • Hi Sarah,

    thanks for your fast reply. The next opportunity I have checking all your suggestions is next thursday. Next thursday I'll tell you how it all went!

    Thanks!! Enjoy your weekend.

    Best regards,

    Markus

  • Sooo, I am happy and I could freak out at the same time!! We plugged in my board on the other computer. When requesting the debugger to start, the same message came up (make an update for debug probe). On this computer though, the update was made without a mistake and after the update was made the board now works on my computer, too!

    I spent many hours with this problem, but what I now learned is that you always buy 2 boards and install the SDK on 2 laptops.

    Thanks for your help, Sarah!