User`s manual
5-6 Suite56 DSP Tools User’s Manual Motorola
How do I get a listing with cycle counts?
When you assemble your application, use the option -mu to report loadtime memory use,
and use the option
-g to include debugging information in the output of the assembler.
Then load your assembled application into your Suite56 simulator.
After loading the assembled application into the simulator, then from the File menu,
choose Log, and select Profile. A dialogue box appears for you to indicate the location
and name of a log file to save the profile that the simulator will generate for you.
Then execute your application in the usual way. The profile appears in two files: an
ordinary ASCII-file with the extension
.log, and a PostScript file with the extension .ps.
You can view the contents of the .log file through any text editor or the PostScript file
through a PostScript viewer. The same information appears in both files:
• a routine call graph;
• a graph of dependencies between routines in your application;
• a list of which parts of your application executed;
• indications of program flow and control;
• lists of instructions used by instruction type;
• lists of memory locations and the number of reads and writes to those locations.
5.10 How do I get a listing with cycle counts?
When you assemble your application, use the option cc to enable cycle counts in the
listing file produced by the assembler.
5.11 My program runs, but I want it to go faster.
First, consider whether the algorithm you are using can be reduced in any way. You may
need to consult other software engineers or exploit tools such as Matlab to help you with
this part of the problem.
Once you are sure that you are implementing the most efficient algorithms for your
application, then assemble it with the options -mu for a loadtime memory-use report and
-g to retain debugging information in the assembled output.
Next, load your application in the usual way into a Suite56 simulator, and profile it, as we
suggested in Section 5.9 .
We strongly recommend that you analyze the loadtime memory-use report and the profile
of your application before you begin optimizations to be sure that you optimize portions of
your program that actually make a difference in its performance.