The call stack was unable to find Frame Pointer register information

Hi Shuyan,

I would like to see if I can reproduce the same problem you are seeing.

Could you please send more details regarding your settings and code.  What EVM/Setup do you use?  Are you running an example?  If so which one?   What CCS Settings and setup do you use?

Best Regards,

Lisa

Hi,

I imagine that something is corrupting the register B15 that holds the stack pointer or the stack region itself. Can you increase the stack and see if this issue goes away? If not, can you verify if other cores are overwriting the same memory regions?

You can inspect the stack by checking its contents given by the symbols mentioned in section 7.5.8.4 of the C6000 Compiler v7.0 User's Guide (link here)

The error comes from the factor that the debugger requires the frame pointer information to properly display the call stack in the debug view.

Hope this helps,

Rafael

Hi Lisa,

I just created a new project which is provided by CCSV5.0.2. The example is included in IPC and I/O Examples , it’s  name is “C6678:MessagesQ(single image in all cores)”. when  I debug  it  using   Texas Instruments simulator, I can see the right result. But when I debug the example using TMDXEVM6678L ,at the beginning ,

“C66xx_0: The callstack was unable to find Frame Pointer register information
     C66xx_1: The callstack was unable to find Frame Pointer register information
     C66xx_2: The callstack was unable to find Frame Pointer register information
     C66xx_3: The callstack was unable to find Frame Pointer register information
     C66xx_4: The callstack was unable to find Frame Pointer register information
     C66xx_5: The callstack was unable to find Frame Pointer register information
     C66xx_6: The callstack was unable to find Frame Pointer register information
     C66xx_7: The callstack was unable to find Frame Pointer register information”

is always showed  in console, without the right results.

When I ignore this, and continue to debug  ,the eight cores is always in the state “running” .

I hope you can help me . Thank you very much!

Best Regards,

shuyan

Hi  Rafael,

      Thank  you  for your answer. But I'm a jackaroo, I haven't understand your  advice.Thank you all the same !

     Best wishes,

     shuyan

Hi Shuyan,

First of all sorry for the delay but we are still trying to determine what might be going on here.   I have now tried a simulator and board with no success trying to reproduce what you see.

What setting do you have in your ccxml file?  You should have had to create one.

What do you have set under the following properties? ... see screen shot

What exact hardware are you using?

Thanks!

Lisa

Screenshot ...

Hi Lisa,

Thank you for your reply. I have retried many times, but the same phenomena just as I have described it to you always appeared. Yes, I have created a .ccxml file, and I think it is right, now I will sent my project to you, and hope you can help me. In addition, the hardware I used is 6678, the development environment is CCSv5.0.2, and the emulator is BlackHawk.

Thank you very much. I’m looking forward to your reply.

Best wishes!

Shuyan8308.6678 MessageQ.rar

Hi Shuyan,

I am still trying to work on reproducing this so thank you for the file.  

First of all, may I ask what message_multicore.k is?  Have you tried the example as is?  Have you tried CCS v5.1?

I get errors before the point you show in your original problem post.

Cheers,
LIsa 

Hi Lisa,

Thank you for your great suggestion. I think it is a good idea to install CCSv5.1, so I will install CCSv5.1 to have a try ,and maybe my problem can be solved.

Thank you for your help these days.

Best regards,

shuyan

Hi Shuyan,

just thought I would check whether there are any updates here.

Best Regards,
Lisa

we are also facing the same problem in CCS5.2 with DM6446 EVM on ARM side. earlier this problem is not there but after some time of uses it start coming.