User manual

UM0036 Simulator features
Doc ID 7705 Rev 11 221/385
Figure 161. Memory and Watch windows with Read/Write on the fly
Note that when you scroll in the Memory Window, the newly visible memory entries turn
bold, to show that they are being updated, then change back to normal, indicating that they
are current and valid.
When the Read/Write on the Fly option is active, the only time that the values shown in the
Memory window may not be valid is during the direct editing of a memory value during the
running of a program. In this event, the edited value appears in red, indicating that it has not
yet been taken into account by the program, it then turns to bold black, to indicate that the
program is adjusting accordingly, and then finally, all entries are in normal weight black,
indicating that the window is valid and updated.
6.5 Forcing interrupts
In the Simulator, you can generate interrupt requests using pseudo pins named IRQx,
where x is the interrupt number. This is done by changing the value of the IRQx pseudo pin,
either from the from the I/O Stimulation window or in the stimuli file.
This feature is useful because it allows you to debug code for peripherals that are not
supported by the Simulator. And in the case of supported peripherals, it allows you to trigger
an interrupt whenever you want, without waiting for the interrupt conditions to be met.
The prerequisites for using this feature are:
● Interrupts must be globally enabled in the condition code register.
● The interrupt handler corresponding to the IRQ number must be defined, and its
address correctly set in the interrupt vector.
Note that if there is no interrupt handler at the address pointed by the interupt vector
corresponding to the interrupt request number, the program will crash.
You can use any kind of signal (digital, analog or periodic), with a delay if you want, to
generate an interrupt. Refer to Section 6.2: Using the input pin stimulator on page 203 or