Zilog

Z8® CCP™ In-Circuit Emulator

CP97Z8X5301

5

1

LIMITATIONS

1.

Typing into the File Name box in order to change the

drive in the file download and load symbol dialog

boxes is not anticipated by the GUI. Instead, use the

mouse in the Directories box as the workaround.

2.

Switching ICEBOX™ emulators without quitting the

GUI is not supported and may cause unexpected

results.

3.

The maximum loadable symbols is 32,768, provided

there is enough system resource (memory).

4.

The keyboard and mouse will lock up if the screen

saver supplied by Windows 3.1 times out while the

GUI software is waiting for the user to complete

entering a line of assembly code in the Debug window.

To recover, the user must reset the computer. The

workaround is to turn off the screen saver, set the

screen saver to a much longer time out value, finish

the line of code before the time-out occurs (press

ENTER), or use a different screen saver such as “After

Dark.” This problem may also exist at other points in

the GUI that request input from the user.

5.

Although GUI 3.00 and later support baud rates up to

57.6K baud, the actual maximum usable rate may be

less due to limitations of the user’s hardware or

system software setup. The maximum usable rate is

determined by the user’s tolerance of the frequency of

communication errors.

6.

The initial blue Zilog screen can be distorted by other

active windows. This only affects the appearance, not

the functionality, of the GUI.

7.

Do not put a breakpoint at addresses after STOP

instruction. This will cause the program counter to

continue at that location after a Stop-Mode Recovery.

8.

Single-stepping into the Halt instruction will cause an

ICEBOX “Fatal Error” message to be displayed on the

screen. The ICE chip must be reset, either by /Reset

pin on the target board or by resetting the whole

ICEBOX by pressing the emulator MASTER RESET

button at the back of the emulator.

9.

Clicking on the HALT button does not always halt the

ICEBOX execution. If the application goes into Stop

Mode or Halt Mode, the only way to halt the emulator

execution is by doing a Stop-Mode Recovery (as

defined by the user program). You may also reset the

application using the emulator MASTER RESET

button; however, this will reset the whole ICEBOX.

10. RC oscillator emulation is not supported.

11. Since the emulator uses the Z86C50 ICE chip, Port 1

cannot be configured to Low EMI mode. Bit 4 in PCON

registers must be set to logic “1”.

Note: This is not a problem with the actual emulated

device.

12. When the software enters a STOP mode and the

HALT control button in the GUI software is pressed,

any SMR source on the application board is activated.

The emulator will then jump back to address 000C,

which is normal. But when continuing the program with

a GO command from 000C, a POR reset is performed,

resetting all control registers.

A workaround is to do a JUMP 000D and execute with

GO. This will not issue a POR reset.

13. Although the GUI displays two timers (T0,T1) for

Z86C02/E02, only Timer1 is valid for these devices.

14. Multiple emulators instances cannot be used when the

OTP Programming Window is open.

PRECAUTIONS

ALL Devices

1.

GUI software versions prior to 3.00 are incompatible

with hardware containing BOOTROM 3.00. The GUI

software may still boot, but will fail at some later point.

2.

For some 386 PCs, a baud rate of 19.2K or less is

necessary because the Windows' communication

driver does not guarantee “reliable” operation above

9600 baud. On some slower 386 machines, selecting

a

high

baud

rate

might

crash

the

Windows'

environment or result in excessive communication

errors.

3.

When simultaneously running two different GUI

versions on two different Communication Ports, the

former executed version is used for both emulators.

This is a Windows Operating System bug.

4.

The emulator cannot be operated while performing

ESD/EMI testing on the target board.

5.

Executing GUI. The GUI will occasionally continue to

indicate “Executing” after a Halt instruction. Pushing

the GO button will then result in Executing. (Executing

showing at the top of the screen.)