If you have not exited and reentered emulation, you can add traces
to a performance measurement simply by entering another
"performance_measurement_run" command. However, if you exit
and reenter the emulation system, you must enter the
"performance_measurement_initialize restore" command before
you can add traces to a performance measurement. When you
restore a performance measurement, make sure your current trace
command is identical to the command used with the restored
measurement.
The "restore" option checks the emulator software version and will
only work if the perf.out files you are restoring were made with the
same software version as is presently running in the emulator. If
you ran tests using a former software version and saved perf.out
files, then updated your software to a new version number, you will
not be able to restore old perf.out measurement files.
Running the
Performance
Measurement
The "performance_measurement_run" command processes
analyzer trace data. When you end the performance measurement,
this processed data is dumped to the binary "perf.out" file in the
current directory. The perf32 report generator utility is used to
read the binary information in the "perf.out" file.
If the "performance_measurement_run" command is entered
without a count, the current trace data is processed. If a count is
specified, the current trace command is executed consecutively the
number of times specified. The data that results from each trace
command is processed and combined with the existing processed
data. The STATUS line will say "Processing trace < NO.> " during
the run so you will know how your measurement is progressing.
The only way to stop this series of traces is by using < CTRL> -C
(sig INT).
The more traces you include in your sample, the more accurate will
be your results. At least four consecutive traces are required to
obtain statistical interpretation of activity measurement results.
Ending the
Performance
Measurement
The "performance_measurement_end" command takes the data
generated by the "performance_measurement_run" command and
places it in a file named perf.out in the current directory. If a file
named "perf.out" already exists in the current directory, it will be
overwritten. Therefore, if you wish to save a performance
4-10 Performance Measurements
Summary of Contents for 64700 series
Page 2: ......
Page 19: ...Tables Table 9 1 Summary of Commands 9 4 Table 9 2 Command Assignments 9 5 Contents 11 ...
Page 20: ...1 Notes 12 Contents ...
Page 24: ...1 Notes 1 4 Introduction ...
Page 106: ...1 Notes 4 36 Performance Measurements ...
Page 118: ...Figure 5 8 True Demultiplexing 5 12 Using the External Analyzer ...
Page 128: ...1 Notes 6 6 Timing Introduction ...
Page 134: ...1 Notes 7 6 Timing Getting Started ...
Page 168: ...1 Notes 8 34 Timing Using the Analyzer ...
Page 201: ...1 find This command finds a trigger like event in trace memory Syntax Timing Commands 9 33 ...
Page 219: ...1 mark This command marks specified conditions in trace memory Syntax Timing Commands 9 51 ...
Page 254: ...1 trigger This command specifies trigger conditions Syntax 9 86 Timing Commands ...
Page 262: ...1 Notes 9 94 Timing Commands ...
Page 280: ...1 Notes B 16 Timing Diagrams and Outputs ...
Page 292: ...1 Notes C 12 Timing Messages ...