User manual

UM0036 EMU3 emulator features
Doc ID 7705 Rev 11 295/385
Figure 226. Defining Level 1, Event 1
An event may incorporate any of the following:
–A Memory Event. You may set an event on any of the following memory events:
Any Memory Access, Memory Access with Data, Opcode Fetch, Opcode
Fetch with Data, Stack Memory Access, DMA Memory access, IT Memory
Access. A Memory Access event would be, for example, a read access of
memory address 0xfd00.
– One or more Other events. Events can be set on the detection of specific values
of signals or other parameter. You can choose one or any combination of the
following: trace buffer (full or not full), input trigger signal value (0 or 1), and
Analyzer probe (enter a specific value or range of values).
– A combination of a memory event and signal events.
Note: All values can be entered either in unsigned integer format, or in hexadecimal format. All
entries in unsigned integer format will be automatically converted into hexadecimal format.
8. Once you have defined event1 and event2 (if present), the next step is to click THEN to
define the actions to take if the defined conditions occur during the running of your
program.
The THEN window allows you to define an action as any of the following:
– Program Execution Break: Stops the execution of the program.
– Trace: Start or stop trace recording, or take a snapshot of the trace (a trace
snapshot is a trace recording of one full program loop). You may opt to start
running your program with the trace ON using the Start with Trace ON option.
Examples of how to control the trace recording using Advanced Breakpoints are
given in Section 10.3 on page 309.
– External Trigger 1 and External Trigger 2: Send a signal to one or both of the
two external triggers (OUT1 and OUT2). Examples of how to control the trigger
output using Advanced Breakpoints are given in Trigger programming examples.
– Goto Level: Jump to another Level of event/action definitions.