2/4
ST7MDTx-EMU2B
OVERVIEW
The ST7 real-time development tools consist of
various hardware and software components,
which together form a flexible and sophisticated
system designed to provide comprehensive development support for the ST7 family of MCUs.
The Hardware Development System (HDS) mainframe is common to all ST7 devices and, in conjunction with various active probes, allows em ulation and development of specific devices. Only the
probe needs to be changed to emulate a new ST7
family device.
The development system is controlled by a Host
PC on which a choice of Windows-based software
may be run. The Host PC is simply c onnected to
the Emulator Mainframe by means of a parallel
port. The STVD7 Windows Debugger software
suite is supplied as standard issue with the Emulator hardware, in addition to the conventional
DOS ST7 Software suite, which includes a macroassembler, a linker/loader. Third party C Toolchain and Debugger software is also available.
The Windows-based debugger provides a user
friendly and highly flexible interface which may be
configured to precisely match the u ser’s requirements. All emulator settings are accessible via the
control software.
Once assembled, and/or compiled and li nked, the
application software may be downloaded to the
real-time emulation memory, which can be configured, mapped and modified as required by the user. The device probe is then connected to the application target hardware in place of the MCU and
real-time emulation of the target application can
begin, thus allowing sophisticated testing and debugging of both application hardware and software.
User definable breakpoints allow t he MCU to be
halted when the application software accesses
specific addresses, and/or addresses within a selected range, and/or on data fetch cycles. The
user may then read and modify any register and
memory location. An on line assembler/disassembler is also available to ease debugging.
An important fe ature of the ST7 d e ve l opment system is that true source level debugging is possible,
meaning code may be v ie wed at sourc e level an d
breakpoints may be s et on high level c ode, rather
than on disasse mbled target code. This is muc h
more meaningful to the user and ensures a more
convivial and productive development environment.
A separate and concurrent Logic Analyzer function is available. This hardware implemented function features 1KByte of 32-bit wide trace memory
which allows events to be defined f or any combination of address (16 bits) and data (8 bits), as
well as according to the state of 3 internal and 5
external logic signals. Complex and sequential
conditions may be defined, and all bits are maskable. The external sig nals are input from 5 probes
which can be connected to the target hardware.
Trace memory events may be used as breakpoints or simply to trigger data acquisition according to user specified param eters, without halting
the target system. Such a powerfu l tool enables
the user to detect an d trap virtually any pattern,
and thus rapidly debug the target application.
Log files offer the ability to send any screen display to a text file. In pa rticular, log files are very
useful to save t he contents of the logic analyzer
and/or the contents of data registers to be subsequently analysed or printed.
Command files can be used to execute a set of
debugger commands in batch mode, to simplify
and speed up the emulation session.
The SFR window offers symbolic display of the
SFRs, showing the peripherals, sym bolic display
of the registers.
Finally, when the target program is fully debugged, the appropriate ST7 EPROM/OTP/
FLASH prog ramming board can be us ed to program the EPROM /OTP/FLAS H version of the target device to allow stand-alone testing and evaluation.
123