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-CC2650: CC 2650 A router subpath could not be accessed. The board configuration file is probably incorrect.

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

Tool/software: Code Composer Studio

I have this exact same problem on a cc1352 launchpad. I've tried uniflash. I keep getting cannot connect to icepick messages.

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 8.0.27.9)

I've tried smartrf flash programmer 2, but just get "Enumeration failed"

  • Hi,

    Your post does not make clear that you tried the debugging suggestions mentioned In the attached thread. Did you try those?

    Especially the option to start a "project less" connection and use the ICEPICK to inspect the status of the M4 core.

    processors.wiki.ti.com/.../GSG:Connecting_to_slave_cores_in_SoC_devices_v5

    If that still does not work for you, there is a strong chance that a previously running software locked your JTAG connection. In this case, the experts in the device forum would be able to help you further.

    Hope this helps,
    Rafael
  • I could not figure out the projectless connection based on the previous thread. I didnt find that option in CCS, uniflash, or smartrf. Based on the link, it looks like that is somewhere in CCS, although I dont see that option in the link.

    I'll try figuring that later today. Are there any more concise references to where that projectless option is found?

  • Hi,

    I see then. It is not an option but a sequence of actions that launch a projectless debug session.

    Section 2 steps 1 through 3 of the page I sent above also talks about how to launch the debugger without a project.

    Once you completed the steps above, section 3 talks about how to inspect the status of the cores.

    Regards,
    Rafael

  • I made it up to step 2 in "Core Status" from that page. When I try to connect to the icepick, I get the same -241 error.

  • Still having the issue and no resolution. Any thoughts?
  • Hi,

    Please apologize for the delay. If you are getting this error trying to connect to the ICEPICK, then there is a severe problem that is preventing communications between the Debug Probe and the device.

    First thing to check is if you have all the JTAG jumpers in place in your launchpad.

    If everything is correct, the major issue in this case is that, by being blocked from connecting to the ICEPICK, it also prevents you from trying to mass erase the device. Something similar to what is reported in the thread below:
    e2e.ti.com/.../659865

    Given this scenario, the best alternative is try to isolate and test each component by comparison with another launchpad or an external debug probe.

    Hope this helps,
    Rafael
  • So basically what I get out of that other thread is I'm SOL. That's really disconcerting since this happened during an innocuous debug session in CCS. I could see if I were monkeying with pins and fried the board, but that is definitely not the case here. This happened purely as a result of software.

    I have tried running a cable from one launchpad's XDS connector to this one's target connector (and removed all jumpers), but I am getting the same results.

    in flashprogrammer2, I keep getting "An XDS emulator may have incompatible firmware. See Help document for troubleshooting" or "a valid device must be selected" even on a known good launchpad. This is a 1352... is that maybe incompatible with flashprogrammer2?
  • Hi,

    In certain devices there is a condition that locks you out of JTAG, and I suspect that in your device this is a possibility - but that is entirely dependent on the code itself, not something the debugger or the CCS could explicitly cause. Obviously that does not rule out the unfortunate possibility the HW itself simply ceased to work inadvertently.

    I think the SmartRF flash programmer 2 does not support the CC1352 devices, but I asked for the help of a device expert to chime in with his inputs.

    Regards,
    Rafael
  • Hello,

    I can confirm that the CC1352 devices are not supported by SmartRF flash programmer 2, therefore you will have to use Uniflash.

    Best regards,

    David
  • Is there any technical difference between uniflash and smartrf programmer2 with regardes to this issue? I am unable to use uniflash because of the following error (it works fine with another launchpad and other devices):

    [9/4/2018, 12:59:15 PM] [ERROR] IcePick_C: 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 8.0.27.9)

    How do I unlock the device?

  • Hello,

    Please get in touch with us offline and we can point you in the right direction (you can click on my profile and send me a private message that way).

    Thanks,

    David
  • It isn't abundantly clear how to do that on your profile page
  • Hi spanky,

    I can see where this is not very obvious.

    Here's how to do it: click on DavidL's name on his post above - this will take you to his profile page. Then, there is a "+Connect" teal colored button in the upper right - click this and then select "request friendship". You can include your message in the friend request, or wait til it gets accepted to then start sending PM's.

    Alternately, I think that my own profile is set such that you can send me a message without requesting friendship first, so you could try on my profile if that's easier. Thanks for your patience here - I know the private messaging setup is not super straightforward the first time.

    Regards,
    Katie
  • I did that a while back, but no response. At first I mistakenly clicked the first option "Email -------" but I was too lazy to read the rest "Email unsubscribe to user", which in itself is not overly obvious. Did clicking that first prevent the request from going through?

    The 2nd option currently says "Cancel Friendship Request"
  • Closing this thread because this is being handled offline.