CCS/TM4C129XKCZAD: J-link debugger error ""CORTEX_M4_0: Error: Stat [ JLINKARM_IsHalted() call ] failed!""

Hi,

The function you mention is the attempt of the Jlink to verify if the target is halted - this is necessary to access the target for any operation (read memory, a register, set a breakpoint, etc.). In this case, I suspect a view may be triggering this - can you close the views opened (variables, registers, memory Browser, etc.) and see which one may cause this message to disappear.

That is also valid if you are trying to modify something while the target is running - you may get these issues triggered as well.

I couldn't get this issue here - I tested my Jlink (not Ultra+) with both CCSv7.1.0 and Segger support version 6.10.0n/1.0.0.6 and CCSv7.3.0RC1 and Segger support 6.14.0e/1.0.0.6.

Hope this helps,
Rafael

Hi
I tried closing all views .... I still face the issue
I observe the problem occurs when CCS executes the first instruction
ui32SysClock = SysCtlClockFreqSet((SYSCTL_XTAL_25MHZ |
SYSCTL_OSC_MAIN | SYSCTL_USE_PLL |
SYSCTL_CFG_VCO_480), 120000000);

If i step thru this portion then it run it then it seems ok....
Also after building first time if i run the code then too I do not see this issue after closing the view!!

Hi,

Thanks for sending the details; I have seen similar scenarios caused by the change in the PLL that cause an intermediate glitch on the JTAG TCLK frequency - this can trigger the warning message, although I haven't seen this happen with my Jlink yet.

In the case of XDS Debug probes, I have seen warnings be triggered during these transitions but very randomly. In the cases I observed, there was nothing that could be done. 

I will try to reproduce this on my Launchpad with code that performs these PLL transitions. 

Regards,

Rafael