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.
Tool/software: Code Composer Studio
CCS version info:
Code Composer Studio
Version: 10.2.0.00009
OS: Windows 10, v.10.0, x86_64 / win32
Java version: 1.8.0_144
I am working with Tiva TM4c123 64pin part on custom board. I've been working with the FatFS code trying to port it to a WinBond spi serial flash.
I set a breakpoint (see below) at a line in a file. I then toggled the breakpoint to remove it, and it acts like the breakpoint is still active.
I have closed CCS v10 and re-opened, same problem. I have cleaned the project and rebuilt it, same problem (code halts at the line as if there is a breakpoint.
The menu item Run -> Remove all breakpoints is grey (indicating to me the user, that there are no breakpoints). When the program is loaded for debug, it stops at main() with a 'hidden' breakpoint at main().
Could it be that I somehow inadvertantly added a hidden breakpoint on line shown below. If so, is there a way to remove the hidden breakpoint?
What else could explain this behavior?
Thanks in advance
First break at the hidden breakpoint:
'Step Into' does nothing, no single step, no errors in console.
'Step over' does not single step, but results in: CORTEX_M4_0: Can't Run Target CPU: Timed out while waiting for target powerup/polling a hardware resource.
'Resume (F8) has same/similar results as Step Over
CORTEX_M4_0: GEL Output:
Memory Map Initialization Complete
CORTEX_M4_0: Can't Run Target CPU: Timed out while waiting for target powerup/polling a hardware resource.
a brief video of the 'challenge'. This is an application that uses TivaWare 2.1.4.178
Several attempts at attaching a video have failed. Youtube link will hopefully live thru the e2e filter. https://youtu.be/Ff_Vz21vw34
Hello,
Please open the Scripting Console and type:
js:> eval("DEBUG_DumpBreakpoints()")
and cut and paste the output that appears in the Console view to this thread
Thanks
ki
Update: A fix has have been found.
A complete Power down of the target hardware and JTAG emulator, as well as the laptop, removed the hidden breakpoint.
The target hardware has two supplies, a battery supply for HIB and the board power input. I had been cycling the board power and not the HIB supply. The fix happened when both supplies were disconnected, JTAG disconnected from the laptop, complete power down of laptop with a few minutes of wait before repowering.
The ultra low power hardware may have been hanging onto enough energy and in the thrash to get unstuck, the user was moving too fast.
Case closed.
And thanks so much for the pointer Ki, I will do that if I encounter this problem again. Best regards and thanks.
I should add that my overall experience with Code Composer Studio is quite positive and the move of a decent size codebase (cc13xx, Tiva) from CCS v7.4 to CCS v10 has been very good, great product!