User`s guide

124 CPU32 Emulation
Chapter 7: Using the Emulator with a Debugger
Using the Software Development Systems debugger
Getting started
1
Check that your emulator is programmed with firmware for a
CPU32 processor:
For an emulation module, go to the system window of the logic analyzer
interface and verify that the Emulation Module icon is described as a
"Motorola CPU16/32 BDM Emulator". If it is not, follow the instructions
on page 147 to update the firmware.
2
Connect to the emulator:
a
Start SingleStep running on your PC or workstation.
b
When the small Debug dialog box appears in the middle of the
screen, click the Connection tab and then enter the IP
address of the HP logic analysis system which contains the
emulation module.
If the Debug dialog box is not visible, select
File
➞
Debug
.
Note: SingleStep is hard-coded to connect to the emulation module at port
6470 of the logic analysis system frame. See page 110 for more information
on port numbers.
3
Configure the emulator with the processor clock speed.
In the Debug dialog box, click the Connection tab and then enter a
Processor Clock speed which is less than or equal to the speed at which
the processor will run out of reset.
The emulator must know the target clock speed before it can
communicate with the target. This value depends on the oscillator or
crystal used on your target system and the multipliers applicable at
reset. The communications speed can be changed (see “Download
performance” on page 131) but will be reset to this value each time
SingleStep resets the processor.
4
Initialize the target system.
The target system must have various registers and memory locations
initialized before it can access RAM and before SingleStep can
download an application. Normally, code in the target’s boot ROM