ST7MDTU5-EMU2B STMicroelectronics, ST7MDTU5-EMU2B Datasheet - Page 39

• Manufacturer Part Number: ST7MDTU5-EMU2B
• Description: EMULATOR REAL TIME ST7
• Manufacturer: STMicroelectronics
• Series: ST7-EMU2Br
• Type: Microcontrollerr

Specifications of ST7MDTU5-EMU2B

• Contents: Main Emulation Board (MEB), Target Emulation Board (TEB), Cables, Power Supply and Documentation
• For Use With/related Products: ST7265x
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

ST7MDTU5-EMU2B User Manual
Note:
3.12
3.12.1
3.12.2
Using the Configuration Setup dialog box (available from the MCU Configuration dialog
box), you can also control what type of MCU configuration information is restored from a
workspace file (*.wsp).
Debug context and Build context
There are two STVD7 contexts, the build context and the debug context. Until
now, in creating a workspace, and defining your project settings, you have been in
the build context. To proceed step—configuring your MCU—you need to change to
the debug context.
Briefly, the two contexts are different in that:
•
•
Build Context
The build context is the context set when starting STVD7. In this context, it is not
necessary to be connected to an emulator and the debug commands are not
available. You can also edit the source files of an application and perform the use
the Build command to perform compile and link actions in an interactive and
iterative way to re-build the application executable file.
Debug Context
In this context, the following debug actions can be carried out:
•
•
•
•
•
•
•
In the build context, you can open and close workspaces and build or re-build
the application executable file.
In the debug context you set the emulated MCU configuration (this step is
described in
build context.
Loading, running and stopping the application.
Defining the MCU configuration (MCU options and memory mapping).
Viewing source and disassembled code.
Setting instruction breakpoints with a counter and/or condition.
Setting data breakpoints.
Viewing local variables, memory and ST7 registers.
Viewing history of execution from the trace buffer or with the Call Stack feature
analyzing the performance of a piece of code.
Section
3.13) and debug the executable file created while in the
3 - STVD7
39/71