Path / History

Clyde - are you looking for a call stack? Or something more detailed like trace-type capability?

Thanks

ki

There is a thread that shows the functions called to get to the break point.  But I'd like to know the previous functions called ... and the sequence of these calls.

Sounds like you are looking for the call stack. You can see that information from the debug view:

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_ccstudio/workshops/CCSv5/CCSv5_OverviewWorkshop.pdf (see slide 41)

It would be good to try things before making a suggestion.  The call stack does not provide anything beyond the thread mentioned in the previous response.

Clyde - it would be helpful if you reference the thread you are talking about. Otherwise I can only make guesses as to what you are mentioning.

As mentioned in the first query, I would like the history of all functions called, not just the thread.  All functions includes those that were called and then returned to main() before the thread that lead to the break point.

Still waiting for a response.

Can I get a response from TI for the question posted on Apr 24, 2012 11:37 AM?

Clyde,

Sorry for dropping the ball on this thread. I also got confused when you were mentioning threads. I was thinking of a forum 'thread'. Unfortunately the tracing type debug functionality is quite limited on MSP430. One option that may work is use function hooks to log the function name or function address that calls the hook. Basically you are doing your own little trace where you are logging every function call. This option will add overhead in terms of both space (hook functions and a circular buffer to store the name/addresses) and performance. Knowing how code size is a big concern on MSP430, this may add too much overhead in the space department. But if you still want to explore this, function hooks are covered in section 2.13 of the Compiler User's Guide:

http://www.ti.com/lit/ug/slau132e/slau132e.pdf

There is also a wiki topic that covers how function hooks are used for profiling. The examples are for C6000 but it gives you an idea of how function hooks can be used. Might be useful to take a peek.

http://processors.wiki.ti.com/index.php/Profiling_on_the_C6000_using_Function_Hooks

Sorry, I can't think of a better option. Hopefully some others in the forum can provide some insight.

Thanks

ki

I find info on hooks in 2.14.  It's not clear how to implement or retrieve info. 

1) Do I simply put:

   extern "C"
   {
     --entry_hook;
   }

in main.h?

Where do I find the results?

Clyde,

--entry_hook is a compiler option. You enable function hooks in the build options and specify if you wish to pass the address or function name to the hook function. You can also specify the name of your hook function. In the example below, I am passing in the name of the function that is calling the hook function to the hook function so I can log it. I have specified the name of my hook function as 'logFxnName'.

The next step would be to create a function called logFxnName that has the caller function name as a parameter. Then this function would write the caller function name to a buffer (or where ever you wish).

Did you check out that wiki topic? Even though it is for C6000, many of the concepts regarding function hooks is generic enough that it applies to all devices using function hooks. It shows code examples of hook functions and some cool things you can do in there. It also has an example of the BIOS task switch hook feature to be able to identify via task if you are using BIOS.

http://processors.wiki.ti.com/index.php/Profiling_on_the_C6000_using_Function_Hooks

Note that the screenshot for the build options is outdated.

Thanks

ki

missing screenshot added.

Where do I find "Properties for msp430ex"? ... I'm guessing at the words on the screenshot as the font is very small.  I'm using Code Composer 4.

'msp430ex' is simply the name of my project. Basically I am in the project build properties. 

Sorry I keep forgetting you are still on v4. The properties page looks a bit different in v4.

Clyde Eisenbeis said:

I'm guessing at the words on the screenshot as the font is very small

also, if you click on the picture, you can see a bigger size image of it.

fixed incorrect screenshot for CCSV4

I entered

the result is

Didn't take my images ... although they looked fine before I hit "Post".  How does one insert images?

Yeah the insert image thing is confusing. When I select an image, I have to wait until I get the little green 'uploaded' message and then I have to make sure I hit the 'insert' button. Then when I post my image, it will appear.

I entered

the result is

Delete.

Clyde -

Clyde Eisenbeis said:

I entered

the result is

You are getting an linker error saying that it could not find the entry/exit hook functions you specified in the compiler options. Did you actually create the 'LogEntryHooks' and 'LogExitHook' functions and add them to your project?

I also see you that you are passing in anything to your hook functions (2nd and 4th options are blank). If you want to log the function name, you'll have to pass in the name or address of the function (use the drop down menu to select name or address)

This sounds like a lot of work.  What are the contents of the functions? 

I need to add the name of every function? 

Do you have example code? 

It seems that Code Composer should be able to log every function called ... similar to the Debug Thread ... without any modifications to the code.

Clyde Eisenbeis said:

This sounds like a lot of work.  What are the contents of the functions? 

It can be anything you want. It is completely up to you. In your case you want it to log the function name to a buffer (or cio thought that may be too heavy)

Clyde Eisenbeis said:

I need to add the name of every function? 

Do you have example code? 

Please check out:

http://www.ti.com/lit/ug/slau132e/slau132e.pdf (section 2.13)

http://processors.wiki.ti.com/index.php/Profiling_on_the_C6000_using_Function_Hooks

The first link details how to pass the function name of the calling function to the hook function. The second link shows an actual code example using the function address. There is also example code of a hook function.

Clyde Eisenbeis said:

It seems that Code Composer should be able to log every function called ... similar to the Debug Thread ... without any modifications to the code.

It depends on the device. Some devices support the advanced tracing capabilities provided by CCS. Other devices (like MSP430) do not.

ki

It would be good if Code Composer automatically inserted the appropriate code with the click of a button ... and removed it likewise. 

Yes, that would be pretty cool. I will make a request on your behalf.

ki