I am currently building an
application and I am employing CCS Version 2.20 for the same. I am attempting to
profile certain functions in the simulator (C55x Cycle Accurate Simulator) and I
feel the cycle counts aren't accurate.
Has anyone else faced a
similar kind of problem ? If so, are there any known bugs/ shortcomings and
workarounds for the same ?
Am I missing some setup or
initializations ??
Looking forward to your views
in this regard.
Thanks a lot in
advance.
Cheers,
Ganesh
Reply by simha j●September 26, 20042004-09-26
Hi,
From my experience I can say that, Profiling facility
provided in CCS is fairly correct.
As said by Jagadeesh in one of his previous mails, use
device simulator, to get a rough figure, while
profiling.
Another way is to use the STS module in DSP/BIOS, to
get an approximate value about the cycles consumed in
the execution.
and one more simple method which gives accurate
results is to use the GPIOs on your hardware. just
toggle these pins before and after the function call
you want to profile and observe on a scope. This is
the most accurate method to do it.
We have done it for our Audio/Video codecs and have
got satisfactory numbers.
The differnce bwtween this method and the software
method was about 20%.
This overhead is may be due to the software itself.
Regards
Simha
_______________________________
Reply by Bibin Varghese●September 27, 20042004-09-27
What Simha said is exactly correct.
DSP/Bios will give a better result than profiling.And Harware SET/RESET
using CRO (or any analyser) will give the exact result .
By Bibin Varghese
-------Original Message-------
From: simha j
Date: Monday, September 27, 2004 17:21:28
To: c...@yahoogroups.com
Cc: g...@emuzed.com
Subject: [c55x] Re: Reg. Profiling of functions in
Simulator
Hi,
From my experience I can say that,
Profiling facility provided in CCS is fairly correct. As said by
Jagadeesh in one of his previous mails, use device simulator, to get a
rough figure, while profiling.
Another way is to use the STS
module in DSP/BIOS, to get an approximate value about the cycles consumed
in the execution.
and one more simple method which gives
accurate results is to use the GPIOs on your hardware. just toggle
these pins before and after the function call you want to profile and
observe on a scope. This is the most accurate method to do it. We
have done it for our Audio/Video codecs and have got satisfactory
numbers.
The differnce bwtween this method and the software method was about 20%. This overhead is may be due to the software
itself.Regards Simha
_______________________________
_____________________________________ Note: If you
do a simple "reply" with your email client, only the author of this message will
receive your answer. You need to do a "reply all" if you want your answer
to be distributed to the entire group.
_____________________________________ About this discussion group: