User`s guide

CPU32 Emulation 127
Chapter 7: Using the Emulator with a Debugger
Using the Software Development Systems debugger
the SIM registers before issuing these two commands. “control –c” is
used by SingleStep to forward a command to the emulator. For help on
either the “sync sim” or “pp load” command, issue the commands,
control –c “help sync” or control –c “help pp load” into the Command
window. Also, note that the help pp load command will refer to the
analysis probe as a preprocessor. They are one in the same.
If your target is not one that SDS ships a workspace for, add a line to
the bottom of the file “sstep.ini” (which is supplied with the debugger)
that sets up the _config alias to point to a .cfg file to use. This line will
look like:
alias _config 'source ${cmdpath}68336.cfg'
In this case, the name of the config file to use is 68336.cfg. Edit this file
specific for your targets need. Keep in mind, that commands beginning
with “control –c” followed by a string of quoted text are commands that
will be forwarded to the emulator. Commands that do not begin with
“control –c” are SingleStep commands.
Example
Here is a configuration file which contains both emulator built-in
commands and SingleStep commands:
# Config file for 68336 Motorola Modular Board
# First set clock speed to 8 MHz
control -c "cf procck=8"
# Set the processor id to 68336
control -c "cf proc=68336"
set vectbase = 0x000000
set vectaddr = 0x000000
# write -l CPU:0x3FF00 = 0x01000133 # MBAR
# write -l SD:0x01001000 = 0x0001438F # MCR
# write -b SD:0x01001022 = 0x0E # SYPCR
# write -l SD:0x01001040 = 0x17CD23A0 # GIMR
# write -l SD:0x01001050 = 0x00000000 # BR0
# write -l SD:0x01001054 = 0x00000000 # OR0
# write -l SD:0x01001060 = 0xA0000001 # BR1
# write -l SD:0x01001064 = 0x2FE00000 # OR1
# write -l SD:0x01001080 = 0x00000001 # BR3
# write -l SD:0x01001084 = 0x4FE00009 # OR3