ST92F150-EMU2 STMicroelectronics, ST92F150-EMU2 Datasheet - Page 5

• Manufacturer Part Number: ST92F150-EMU2
• Description: BOARD EMULATOR FOR ST9 SERIES
• Manufacturer: STMicroelectronics
• Series: ST9-EMU2r
• Type: Microcontrollerr

Specifications of ST92F150-EMU2

• Contents: ST9 Visual Debug IDE, ST9 HDS2V2 Mainboard, Probe, Sockets, Adapters, Power Supply,Cables & Documentation
• For Use With/related Products: ST9 MCUs
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant
• Other names: 497-3101

ST92F150-EMU2 User Manual
1
Note:
INTRODUCTION
Thanks for choosing ST9+! This manual will help you get started with the
ST9 HDS2V2 emulator kit.
The emulator will assist you in debugging your application hardware as well as
your software. The emulator kit comes with ST9+ V6 Toolchain, including
ST9+ Visual Debug—which contains all of the necessary resources to help you
design, develop and debug ST9+ application software running in a real
environment.
This emulator is also supported by the ST9+ V4 Software Toolchain which also includes a
graphical debugger, WGDB9.
Your emulator performs two major functions:
•
•
The emulator is the hardware system that enables you to control and debug your
application program by:
•
•
•
•
•
The emulator takes advantages of an architecture based on two microprocessors.
This enables you to keep control of the emulator, even if the ST9+ application
hangs.
All of the above emulation functions are accessible through ST9+ Visual Debug.
Complete information concerning how to use ST9+ Visual Debug can be found in
its on-line help.
It reproduces the behavior and functionality of the ST9+ microcontroller in real
time, by replacing it on your application board.
By the means of the ST9+ Visual Debug graphical interface, it provides access
to the microcontroller's internal resources (such as registers and memories).
The management of breakpoints and application code trace offers you
powerful capabilities for debugging your application programs.
stopping program execution at particular instructions,
stopping the program after defined events, such as access to specific
addresses, specific registers or a sequence of events,
tracking the execution of the program in a trace memory whose contents you
can filter,
triggering a peripheral such as an oscilloscope after the occurrence of an
event,
analyzing your code performance.
1 - Introduction
5/55