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.

Unable to connect an external board to CC2650 made Custom Board

Other Parts Discussed in Thread: CC2650

Hello,

I have already posted this quote before, but i am continuously facing this error again and again.

I am programming my CC2650 custom made board. I have a connector to connect the other custom board to my main CC2650 board. I am able to debug and test the code on my custom board successfully if i am not connecting anything via connector, but if the other board is connected then CCS throws some error as follows,

"Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). "

I have checked my hardware and even lowered my TCLK, but i don't think this is why the error is popping up. Please let me know why this error is popping out and any solutions to solve it.  I am really stuck with this problem and left out with no solution.

I am using WINDOWS 10 os, CCSv6.1 and XDS100v3 debug probe. Also i am trying to debug the codes to my CC2650 custom board via JTAG in SmartRF06.

Thanks in advance.

Regards,

Nitin

  • Nitin,

    Nithin Nagaraj said:
    I am programming my CC2650 custom made board. I have a connector to connect the other custom board to my main CC2650 board. I am able to debug and test the code on my custom board successfully if i am not connecting anything via connector, but if the other board is connected then CCS throws some error as follows,

    I can't make any accurate assessment given I don't have the custom boards, but the error you mentioned can be found in section 5.20 of the page below:

    http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems

    Given you have a working connection without the add-on board attached, we can rule out any software issues and place our suspicion at something on the add-on board that is causing the CC2650 to be held in reset or powered down. This can be caused by many reasons, ranging from ground loops to short circuits.

    Unfortunately from the CCS/JTAG debugger standpoint there is not much these tools can help in this scenario. The device itself is inaccessible and therefore it prevents any further debugging. In this case, a closer scrutiny from a HW perspective with the possible help from the experts at the Wireless Connectivity forum may be a better way to solve this issue.

    Hope this helps,

    Rafael