Compiler/CC3220S-LAUNCHXL: Debug Hanging issue

Hello,

pann said:

"When Deugging Start 'Program gets Hanging and freeze.can't move to next instruction.

Are your referring that when you try to step to the next instruction, it just stays halted on the same instruction? Or do you need to manually halt execution to see that it is on the same instruction? A screenshot of the could IDE with the disassembly view would be helpful.

Thanks

ki

can't get disassembly view??

sorry, I was thinking of the CCS IDE. Please provide a screenshot what source line you are stuck on when halted. Something like:

Thanks

ki

thnks for rply,

there is no Static place it get halting,

code Get halting or freeze place is Dynamically changing after evey New  debug, so we can't predict where it halt.

so reason for code get halt or freeze??

pann said:

code Get halting or freeze

What exactly do you mean by this? How do you determine that the code is handing/freezing? Are you talking about your code hitting an exception or runs off to an invalid address?

Thanks

ki

not invalid address,

if invalid address means i mention you already that "freezing issue is dynamic.

if 1st cycle of Debug it may give success and ''2nd cycle of debugit may get freeze.

so there's no point for invalid address.

my question is why this happns?

Without more details, like a reproducible test case, it is very difficult to diagnose the root cause. Can you at least provide a screenshot of the Cloud IDE the next time it happens?

sure,

i will share you the screenshot of 2 different place of freeze/halting with 2 diff debug session.

#Line 437 the code get freeze and not move to next instruction(it stays forever)

but when 2nd time we debug freeze/halting line will be change to some other #Line in this code.

In the screenshot above, the target is running. I understand that the location the code gets stuck can change. But when you press the suspend/halt button, where are you halted? Does that change also?

i have attached two images which differentiate the when "halt/ freeze" and after "halt/freeze"

image 1 --> here halting/ freeze happns at  #line 176.

image 2 --> when i press suspend button i get file called  ''Hwi.c''

I don't see where the program counter is in the last screenshot. Can you add "PC" to the Variables view so that I can see where the program counter is?

yes..! here you can see where the PC is and ??

Thanks. This not appear to be a tools specific issue. I will have the device experts investigate further.

ki

Are you using the original localTime example? or did you make changes?

The HW exception is typically related to stack overflow.

Does it always happen or only when you are doing step-by-step debugging?

but last two images are other (Reading sensor projects), not Local Time.

and we have to sample the sensor functions at number of times to get accurate result.while using Debug step over method ''our Code gets freeze/Halted.

and this freeze/halted is not Static ,it has changing its freezing position( line) when we do multiple debug.

so it happns  always...i don't have any idea about this. can pls help me out it.

thanks!

Sure Ki,

Looking forward to Your Guidance

thanks..

Are you using the original localTime example? or did you make changes?

The HW exception is typically related to stack overflow.

Does it always happen or only when you are doing step-by-step debugging?

forget about Local Time stamp example,

there's Two images i have updated with sensor reading projects(which shows before hanging and after hanging)..

hanging while debugging always happns, 

any reason..

Hi,

You have a hard fault at your case - it signalise significant bug inside your code (e.g. stack overflow, access to non-initialised peripheral, etc.). This issue you need to solve by yourself. You have source code of your project and nobody else will be able help with this task.

It seems that your project is based on TI-RTOS. Please follow advices at this video. Usage of desktop version of CCS may to be required for some steps.

Jan

you have mentioned.

can you elaborate (stack overflow, access to non-initialised peripheral, etc.) .

as simple as you can(ex: stack overflow= does any issue with stack allocation?). and remaining, can you??

and

thanks,

Hi,

Please follow video above. It will allow to determine what can be reason of your issue. Another option will be decompose your code to find problematic part of your code. At the first step please see that video. At that video is already answer what is a stack overflow.

Jan

sure,

thanks for guidance,

Hello hi,

"How did you determined these (e.g. stack overflow, access to non-initialised peripheral, etc.).  are the need to be modifiy.

can you share your view on??

thanks,

Hi,

At first step you need to found reason of issue and after then you can fix it. There is no "universal" procedure how found reason of your issue.

If you have some older functional version you can start with it. You can slowly add features from current version and identify reason of issue.

Jan