HP 16600A Series User Manual page 200

In summary, there are two ways for you to configure the emulation
module and your target. The first method consisted of loading an
existing workspace, using the Debug Dialog to modify any items
needed followed by clicking the OK button and having it create a
corresponding .cfg file. If you have an analysis probe connected to this
target, you need to enter the two additional commands into the
Command window (control –c "sync sim", control –c "pp load"). The
second method consisted of creating a .cfg file and specifying that file
in the _config alias in the sstep.ini file. This file will automatically be
loaded upon clicking OK in the Debug Dialog.
To save time, you may want to do the first method just to generate .cfg
file that you can edit and use in method two. If you had an analysis
probe connected you would add the two commands mentioned
previously to the .cfg file thereby not having to enter them through the
Command window.
The "Debug" dialog method and the sstep.ini method are mutually
exclusive. Use one or the other, but not both.
Initialization of the target (that is, execution of the _config alias) will
not actually occur until the "Debug" dialog is successfully exited.
5 Set up the download and execution options in the Options tab of
the Debug dialog.
6 Download the application and run:
Select the File tab and enter the application file name. Exit the
"Debug" dialog box by clicking OK.
Emulation module initialization and target initialization occur every
time the "Debug" dialog is terminated via the OK button. A summary of
the actions taken by SingleStep is given here:
• Initialize the emulation module with the communication speed specified in
the "Debug" dialog.
• If "reset target" was selected then execute the commands specified by the
_reset alias. The _reset alias should be used to specify commands that are
Solutions for CPU32
Chapter 8: Using the Emulator with a Debugger
Using the Software Development Systems debugger
199