CCS/CC1352P: XDS110 errors and breakpoints (Ubuntu 19, ccs v9.3)

Yvan Pearson

Part Number: CC1352P

Tool/software: Code Composer Studio

I can't seem to get breakpoints to activate especially if its somewhere else outside of main.c where it initially stopped when you start a debug session. Also sometimes I get this error

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 8.4.0.00006)
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 8.4.0.00006)
Cortex_M4_0: JTAG Communication 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 8.4.0.00006)

Also, I'm using the zr_light CC1352P tirtos example if that matters. I'm using cJTAG, target powered at 500kHz with a custom PCB

over 5 years ago

0 Yvan Pearson over 5 years ago

Intellectual 850 points

More info:

When I do get the debugger to stop on a breakpoint and I use Step Over one line at a time, at times it seems to be unreliable and jumps to some other line in another other function. I'm guessing it blows over tons of line of code before eventually stopping. At other times it just doesn't stop even if I use Step Over

0 Yvan Pearson over 5 years ago in reply to Yvan Pearson

Intellectual 850 points

Should I be using Windows?

0 Yvan Pearson over 5 years ago in reply to Yvan Pearson

Intellectual 850 points

I also get a similar result in windows. I'm guessing since the device has 2 cores you may not be able to debug normally. Correct me if I'm wrong!

0 desouza over 5 years ago in reply to Yvan Pearson

TI__Guru**** 171309 points

Hi,

There may be a chance that you are running optimized code. The article below explains the details about this scenario:

https://software-dl.ti.com/ccs/esd/documents/sdto_cgt_debug_versus_optimization_tradeoff.html

The infrequent error may be rooted in the application itself that can either cut the Debug Probe connection with the device or make it lose control over it, thus throwing access errors such as the ones shown. This is particularly true when code sets the core to a low power mode or it may change the pin mux settings.

Another aspect is that certain APIs in fact call functions in another core and may jump over specific system calls. Despite this may cause a sizeable code to run, I wouldn't necessarily expect it to jump to apparent random locations.

As soon as I get my Ubuntu 19.10 running, I will be able to test this specific project and will report back to this thread if I find any additional relevant information.

Regards,

Rafael

0 Yvan Pearson over 5 years ago in reply to desouza

Intellectual 850 points

To be confirmed, but this might be the issue:

Sorry, I'm using Ubuntu 18 LTS (not 19)

Code Composer Studio™︎

Code Composer Studio forum

CCS/CC1352P: XDS110 errors and breakpoints (Ubuntu 19, ccs v9.3)