Streamline - Bare Metal - Function/Call Paths view not showing function names

Hi Stephen,

Thank you for your response. I figured out what I was doing wrong and I could now see some profiling data visible in the code view and Function view with function names but it still does not list the data of all the functions.

I still have few questions based on my implementation:

For generating barman files, I have followed the same steps as shown in the video you mentioned. Linear RAM Buffer with Number of tasks as 258-> Cortex R7 -> Selected 7 PMU counters -> NO Custom Counters -> Generated.

For instrumentation, I have created a new implementation file, where I am calling the initialize function and passing the buffer, buffer length (2MB), Clock Info, and Task Info. 

For interrupts, I have created a periodic timer of 200 micro seconds and in the timer handler I am calling the API - barman_sample_counters_with_program_counter with link register as the argument. 

yes my .axf have symbols. 

No my question is: I am not getting the data for all the functions that were hit during the start of execution till the copying of buffer data into a raw file. Instead I am only getting the profiling data of functions at which the timer expiry happened. 

Does Streamline only captures the functions at which timer expired? If not, is there anything else specific to be taken care of to have the data of all the functions

Hi Stephen,

Thank you for your response. I figured out what I was doing wrong and I could now see some profiling data visible in the code view and Function view with function names but it still does not list the data of all the functions.

I still have few questions based on my implementation:

For generating barman files, I have followed the same steps as shown in the video you mentioned. Linear RAM Buffer with Number of tasks as 258-> Cortex R7 -> Selected 7 PMU counters -> NO Custom Counters -> Generated.

For instrumentation, I have created a new implementation file, where I am calling the initialize function and passing the buffer, buffer length (2MB), Clock Info, and Task Info. 

For interrupts, I have created a periodic timer of 200 micro seconds and in the timer handler I am calling the API - barman_sample_counters_with_program_counter with link register as the argument. 

yes my .axf have symbols. 

No my question is: I am not getting the data for all the functions that were hit during the start of execution till the copying of buffer data into a raw file. Instead I am only getting the profiling data of functions at which the timer expiry happened. 

Does Streamline only captures the functions at which timer expired? If not, is there anything else specific to be taken care of to have the data of all the functions

Hi Anudhi,

Getting function information only when the timer has expired is expected. This is because this is the only place you are calling barman_sample_counters_with_program_counter. If you want to get sampling data for more of your application you have two options:

1) Increase the frequency of your timer so that more of your code is sampled

2) If you have any specific functions that you want to sample you can call the barman_sample_counters_with_program_counter manually on these functions meaning you will get a sample everytime the function is hit.

Unless you mean that you are only getting samples inside the sampling function itself. Then this usually points to the value of LR that you are passing into the function being corrupted somehow.

Cheers,
Stephen

Thank you Stephen