User`s guide

128 CPU32 Emulation
Chapter 7: Using the Emulator with a Debugger
Using the Software Development Systems debugger
Given that you added a line to the sstep.ini file that points to this
configuration file, all you need to do now is to bring up the Debug
Dialog and enter the file to download (if desired), and the connection
port to use. Click OK when finished. This config file (the one pointed to
by the added line in sstep.ini) will get executed if and only if you have
not unchecked the “Reset Target” option on the Debug Dialog’s
“Options” tab. This is selected by default. Deselecting this option will
prevent the config file you specified in the sstep.ini file from being
executed. Also, keep in mind that this file will be executed every time
the Debug Dialog is terminated via the OK button when “Reset Target”
is selected.
# write -b SD:0x0100100C = 0x8C # CLKOCR
# write -w SD:0x01001010 = 0x8000 # PLLCR
# write -w SD:0x01001014 = 0x0000 # CDVCR
# write -w SD:0x01001016 = 0x00A0 # PEPAR
# write -w SD:0x01001026 = 0x070F # PICR
# write -b SD:0x01001008 = 0x84 # AVR
# Reset, run, break in order to set up chip selects
# We can issue these commands since the target has boot
# code in ROM that sets up the chip select registers
control -c "rst"
control -c "r"
control -c "b"
# Issue the next two commands since there is an
# analysis probe connected to the target
# Copy the sim values to the emsim set
control -c "sync sim"
# Copy the emsim values to the analysis probe
control -c "pp load"
The config file shown in this example did not need to set up chip
select registers because the target has boot code in ROM that will
accomplish this. Therefore, just issuing a “reset, run, break” will
execute the boot code in ROM. If your ROM does not contain boot
code to set up these registers, add write commands to the .cfg file
(similar to what is shown here for the 68360) to set up these values.
Reset, run, break would not be used to set up a target that does not
contain boot code.