Is there any way to measure the number of clocks taken by a part of my code. I can measure the time taken by the part of my code and divide it sys clk. But I dont want to do it,b'cos using a timer itself consume some clocks in the form of ISR, if it overflows. Any suggestion pls
Find an unused timer, start it at the beginning of the code block you with to profile, stop it after the code block you wish to profile. No ISR is necessary, works for cycle counts up to 65535. For longer pieces of code, you need to count how often the timer overflows, which also gives you the information how often the ISR was called. Since the ISR should be fairly short, it is easy to determine for how many cycles the ISR runs, which you can then subtract from your total. Alternatively, you can of course count the cycles necessary for the instructions, but this is probably only practical for short pieces of code.
No I think you have mis understood. I 'll clear you. if I use the timer, it will include the iterations in the loops. I dont want that. Say, there is a function which contains some code.On compilation,say, the function contains some 25 different opcodes. I want to know the sum of all the 25 opcodes.
You can count it up by hand. Or you could run it in the simuulator and use the Performance Analyser. The Performance Analyser is described in the uVision Manual.