Motorola M68LC302CAF20VCT User Manual page 57

NOTE:
NOTE:
M68ICS08RK In-Circuit Simulator — Rev. 1
MOTOROLA
When the MCU resides on a target system, the RKICS board can communicate
with the MCU over a 16-pin MON08 cable (Motorola part number
01-RE91008W01). The MON08 cable supports the MCU installed in either the
target system or the RKICS.
When using the ICS08RKZ simulation software, the MCU provides the
required input/output information that lets the host computer simulate code,
performing all functions except for maintaining port values. The internal
FLASH memory on the device is downloaded with a program that generates the
appropriate port values. The ICS08RKZ software on the host computer lets the
host computer become a simulator. When the ICS requires port data, the
computer requests the data through the host's serial connection to the core
MCU. The core MCU responds by sending the data to the host via the serial
connection. It is this arrangement that allows a real-world interface for the
in-circuit simulator. The clock runs the MCU at a 4.9512-MHz external clock
rate.
When using the PROG08SZ programming software, the MCU's FLASH
memory can be programmed. Socket XU1 supports the 20-pin SSOP version of
the part, socket XU2 supports the 20-pin SIOC version, and socket XU3
supports the 32-pin QFP version. Only one part may be programmed at a time.
The M68ICS08RK also supports in-circuit programming of either version of the
part through the MON08 cable.
The RKICS board also provides +5 Vdc power, +7.5 Vdc power for the V
voltage required to enter monitor mode, a 4.9152-MHz clock signal, and host
PC RS-232 level translation.
When using the ICD08SZ debugging software, code can be run directly out of
the MCU's internal FLASH at real-time speeds.
The simulation speed will be slower than this rate because the host computer is
the simulator.
The M68ICS08RK's emulation of the MC68HC908RK2 is limited. Port A bit 0
(PTA0) is used for host-to-MCU communication. The port bit is not available
for connection to a target system. Setting DDRA bits 0 to 1 will stop
communications with the simulation or debugger software and will require a
system reset to regain communication with the MCU. Port bits PTB0, PTB2,
and PTB3 are temporarily disconnected from the target system during reset.
Technical Reference and Troubleshooting
Technical Reference and Troubleshooting
RKICS Board
TST
User's Manual
57