CCS/LAUNCHXL-CC1310: Debugger show the actual Line

Hello,

Sinisa Milanovic said:

So is there a way, that the debugger shows me the actual Line, so I can see where the programm is stucked?

For this to happen, the target must be halted in a location where there is actual source code correlation. So if you hit some exception that is not handled and your program ends up in some invalid location ("run into the weeds") where there is no valid code, then there is no source line to display. Look at the program counter of when it is stuck. Is that a valid address for code?

Another consideration is if the target is halted in valid code but that code is from a library where there is no debug symbols.

Another consideration is what level of optimization you built for and if you have full debug symbols for your code:

http://dev.ti.com/tirex/#/?link=Development%20Tools%2FIntegrated%20Development%20Environments%2FCode%20Composer%20Studio%2FDebug%2FDocuments%2FApplication%20Notes%2FDebug%20versus%20Optimization%20Tradeoff

Sinisa Milanovic said:

It's a periodic program, so I am not able to work with Breakpoints, because it happens maybe every 10 000 time.

Note that if it gets stuck at the same address, you can set a program watchpoint for that address and have it halt when that address is first reached.

My explicite problem is, that my Code is very large.
I start the program and it works fine for a long time(for example 8 hours), and then it stopps.
Now im still connected with it, but i don't know, where the programm geht stucked(mybe the program waits for a semaphore post)
Is there a way, if I'am still connected with the CC1310 over CCS, that i can see, in which line my program is now(again as example that he waits at the Semaphore pend, because the semaphore post did not send)

Thank you very much for your help

Best regards

Sinisa Milanovic said:

Now im still connected with it, but i don't know, where the programm geht stucked(mybe the program waits for a semaphore post)

Do you have the option to halt the target? Or are you trying to determine where it is stick without halting? If you can halt the target and did so, you should be able to see where you are halted in the source unless one of the scenarios described in my prior post apply.