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/CC1310: Error -242 @ 0x0 : A router subpath could not be accessed.

Part Number: CC1310

Tool/software: Code Composer Studio

Hi,

I have built a custom board based on the cc1310 reference design. I'm using the CC1310 launchpad to program and debug my board. Whenever I launch a debug session I get this 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.0.903.2)

I found this page http://software-dl.ti.com/ccs/esd/documents/ccsv7_debugging_jtag_connectivity_issues.html#a-router-subpath-cannot-be-accessed which talks about the issue. But following the instructions I was able to work around the problem by directly connecting to the DAP (as shown in https://www.youtube.com/watch?v=-yGmq_VKvTQ&feature=youtu.be. But I have to perform a physical reset using the reset button on the launchpad before connecting to the DAP. If I don't perform the physical reset I get the same error.

I was wondering why the reset is required. I never needed to manually reset the CC1310 chip onboard the launchpad. But my custom board doesn't work without the physical reset. Could you please help?

  • Hello

    Hrunker Unnerby said:
    I have built a custom board based on the cc1310 reference design. I'm using the CC1310 launchpad to program and debug my board.

    Just so I understand correctly, you are using the XDS110 on your CC1310 launchpad to debug your custom CC1310 board?

    Thanks

    ki

  • Yes, I'm using the XDS110 on the CC1310 launchpad.
  • I realized that the post composer ate some of my text when I posted the question. I've updated the post with the missing information. Thanks for looking into this.
  • Thanks for the clarification. I will bring this to the attention of my colleague, who is more knowledgeable regarding these types of emulation issues.
  • Hi,

    The fact the Debug Probe is not reseting the device may be due to either a build (PCB routing) or a connection issue (the reset line is failing or not connected). Can you double-check the connections and the directives shown at the section "Target Connection Design" --> "Single device non-buffered configuration" of the reference below?

    dev.ti.com/.../

    Also, a few other posts cover some troubleshooting details that may be useful for your scenario as well.
    e2e.ti.com/.../712032
    e2e.ti.com/.../718809

    At last, if you have a photograph of your setup with the connections, that could help get to the bottom of this.

    Hope this helps,
    Rafael