Call stack in Code Composer studio

Bojun Pan

Hi,

We are currently using the CCS V6.1.

We are looking for a way to extend the callback stack display in CCS to show where the exception came from.

We are sometimes getting aborts in like interrupts so the return address should be on the stack or in a register. But we always find it's hard to tell where it exactly gets stuck.

Is there any better way in CCS?

Best Regards,

Boju

over 9 years ago

0 stevenh over 9 years ago

Guru 20045 points

Hello Boju,

If you are using the C2000 compiler, you can use an entry & exit hook function to show you which function the exception originated from. Other compilers may also have this functionality.

The compiler puts the entry function at the entry of every function in your code, and it puts the exit function at the exit of every function in your code. The compiler gives you the option to pass the caller name or address, which can then be stored in another global variable that can be read after the exception occurs.

Stephen

0 Bojun Pan over 9 years ago in reply to stevenh

Prodigy 130 points

Thanks for your reply.

But, is there a way to extend callback stacks in CCS?

0 stevenh over 9 years ago in reply to Bojun Pan

Guru 20045 points

Hello Boju,

I don't have an answer for that, so hopefully someone from TI will be able to answer your question.

Your compiler may have a -finstrument-functions option, which seems very similar to the C2000 entry/exit function. See stackoverflow.com/.../automatically-adding-enter-exit-function-logs-to-a-project.

Stephen

0 Bojun Pan over 9 years ago in reply to stevenh

Prodigy 130 points

Thank you!

Code Composer Studio™︎

Code Composer Studio forum

Call stack in Code Composer studio