User`s guide

CPU32 Emulation 121

Chapter 7: Using the Emulator with a Debugger

Using the Green Hills debugger

NOTE: logging commands in this way may result in a VERY large file.

Beware of the disk space it may require.

To reinitialize the system

If you suspect that the emulator is out of sync with the MULTI

debugger, you may want to reinitialize it. Perform the steps below to

accomplish reinitialization:

In the Target window, type:

init -c

Repeat step 5 in the "Getting started" section to configure the

emulator.

To disconnect from the emulator

•

In the Debugger window, select

Remote

➞

Disconnect

The Debugger command pane indicates that the debugger has

disconnected from the emulator.

Error conditions

"!ERROR 800! Invalid command: bcast"

usually means that there is not a target interface module (TIM)

connected to the emulator or the emulator does not have firmware for

the CPU32 family. Verify that the emulator is connected to the target.

Next, go to the system window of the logic analyzer interface and verify

that the Emulation Module icon (stop-light) is described as a Motorola

CPU16/32 BDM Emulator. If it is not, follow the steps on page 150 to

update the firmware in the emulation module.

"command socket connection failed: WSAECONNREFUSED: connection refused"

usually means the emulation module is not at port #6470 on the Logic

Analysis System.