• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 831 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC2640R2F: Unable to flash any code in cc2640R2F launchpad: "debug interface is locked error" tried both ccs and smart flash, how to rectify it asap?

Rohit Sahu
Intellectual 305 points
Part Number: CC2640R2F

Hi All,

I cannot flash any code to the cc2640R2F launchpad I am using. The CCSv9.1 shows the following error:

IcePick_C: Error connecting to the target: (Error -242 @ 0x0) A router subpath could not be accessed. The board configuration file is probably incorrect. (Emulation package 8.3.0.00003) 

I even tried the SmartRF flasher to do a forced erase. It gave me the following error:

>Initiate access to target: XDS-L5000JI7 using 2-pin cJTAG.

>Create XBAL object failed: Debug interface is locked.

>XBAL EB pointer is null.

>Failed to create device object.

Please let me know how do I resolve this issue, I need to get the board up asap for a research project. Any help will be greatly appreciated.

Thanks,

Rohit

  • 0
    TI__Genius 15590 points

    Hi Rohit,

    We have a document that covers debugging JTAG: http://software-dl.ti.com/ccs/esd/documents/ccsv7_debugging_jtag_connectivity_issues.html 

    In it I found the following information: 

    "A Router Subpath Cannot Be Accessed

    This error is caused by the inability of the JTAG debugger to access any of the subpaths of either the ICEPICK or the DAP. This is usually caused by either a hardware failure on the board or invalid code on the subcore that causes it to reset itself continuously. This is very similar in nature to the error Cannot access the DAP above but at a higher level.

    If this error is originated in hardware (custom hardware or faulty board or connections), please check this e2e forum thread. Also, power supply problems can lead to this issue as reported in this e2e forum thread.

    If this error is originated in software, it can be either due to a problem with the configuration file (as mentioned in this e2e forum thread or potentially be recovered by accessing the DAP directly and trying to either reset the offending core, lock it or erase its flash memory via a GEL script (some microcontrollers have pre-loaded routines to allow that).

    • For certain devices such as CC13xx and CC26xx, the GEL script is directly available on the menu Scripts → <device name> → MassErase."

    Thanks,

    Alexis