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.

LAUNCHXL-CC1352R1: Debug error - faulty board?

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

Hi

i have 3xlaunchxl-cc1352R1 boards.

With the one board i will be happily debugging for a while when i suddenly get:

Cortex_M4_0: Error: (Error -1170 @ 0x0) 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). (Emulation package 9.4.0.00129)
Cortex_M4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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). (Emulation package 9.4.0.00129)

thereafter the above error happens within a minute of commencing a debug session and i am forced to abandon use of the board for a 'while'. Once the 'while' is up, i am able to debug for a short while before the process repeats itself.

i've tried different usb cables to no avail 

I must stress that the other 2 boards do not exhibit this behaviour despite being subject to the same code & debugging.

can anyone direct me to possible causes...

this is on a win10 pc running ccs10.4

thanks in advance.

  • Hi Moshe,

    This issue is really hard to debug, especially when I am not able to replicate the problem.

    Could you try to do a mass erase of the device in UniFlash under "Settings & Utilities and see if it helps?

    Do you get any errors if you set the device in continues RX in SmartRF Studio or does it only happend when you are running a debug session in CCS?

    Regards,

    HG

  • Hi Halatullah

    Perhaps i should have been a considerate forum user and posted an update...

    it would appear that the problem was due to the usb cable contact with the launchpad...the cable seemed to fit & connect nicely but it was not quite the fit that i thought it was.
    i came to this conclusion because i found a tried a further cable that i found i had which has not caused this problem.

    such is the life in development!

    moshe