CLK_getltime() always gives 0

Also, CLK_getltime() returns a number whose granularity is given in kernel ticks.  Generally the kernel tick is 1ms unless you have modified it.  So with those tiny delays I would expect to get the same number.  Though as Mariana mentions you cannot call that function from main().

If I can not call CLK_getltime() and other CLK functions from main() how can I measure the execution time of my code. I intend to calculate the MIPS for my code. Can you suggest something regarding this?

I don't have a code snippet (i'll have to dig around to see if I still have one) but here's the pseudo code to do something like this:

configure timer

start timer

immediately stop timer

find difference - start/stop overhead

start timer

run algorithm

stop timer

subtract stop-start-overhead

You can call your function from a TSK, or you can use the profiler.

At Code Composer Studio, go to the top menu, click on Profile-> Clock-> Enable, and also select Profile-> Clock-> View.  You are going to see a little watch symbol close to the right corner (bottom) of your CCS screen:

 You can put a break poing before your code, double click in the watch to reset it, put a break point after your code, and get the clock value.

In the CCs profiler virew:

Cycles:

Incl. Total : Total number of cycles for all executions including function calls.

Here does "total number of cycles" means total number of CPU clock cycles?

Yes, exactly.

Hi,

I am using the same basic clock() function and not the other clk functions. just before the code and the after the code, still I am only getting zero. I am not getting correct no. of cycles using the Profiler clock for dsplib functions. Please help

Don't use clock()...  You can look at the source code as its part of the RTS library.  It works by sending a request for the time over JTAG to the host and then receiving the time over JTAG.  This involves CCS silently halting the target without your knowledge which wreaks havoc on real time.  You are much better using BIOS functions such as CLK_gethtime or CLK_getltime for doing benchmarking.  If you're not using BIOS then you should use the Time Stamp Counter (TSC) as discussed in the 64x+/674x CPU Guide.

Hi,

I have performed the same procedure mentioned above to perform benchmarking. But after running over even DSPlib function, i see the clock window showing around 2,828,452 clock cycles. I do not think it is the correct value. What is the correct method to benchmark a particular function call statement which is just one statement.

I've answered this question and you have not taken my advice...  Use CLK_gethtime...

Actually i have posted this problem in another post also..i am using C6727 and not using DSP/BIOS. I have checked the header files for csl_timer.h and this dsp chip is not included in this. Another member has already informed me that clk_getltime will not work for c6727 chip. I can only use the free running timer of the chip.

I have tried to use the function as u have told.  It is not recognised by the chip.

CLK_gethtime and CLK_getltime are both DSP/BIOS APIs.  Both of them work with c672x.

If you're not using BIOS then you'll need to configure the RTI and use that as your time base, which is what CLK_gethtime is doing.