User manual

In-circuit debugging UM0036
234/385 Doc ID 7705 Rev 11
1. Power up the STice box/RLink/STLink, depending on the hardware that you are using.
2. Connect the SWIM cable between the STice box (or RLink or STLink) and the SWIM
connector on your application board.
3. Select Debug Instrument>Target Settings from the main menu bar.
The Debug Instrument Settings window is displayed.
4. From the Debug Instrument Selection list box select SWIM RLink, SWIM STLink or
SWIM STice depending on your hardware.
5. Enable the Hot Plug Start Debug checkbox.
6. Select the communication port (parallel, USB or Ethernet) that your hardware is
connected to.
7. Click on OK to dismiss the Debug Instrument Settings window.
8. Check your MCU selection.
See Section 7.1.2: Selecting your MCU on page 225.
9. From the Debug menu, select Start Debugging to start a debugging session.
STVD starts running the application, without debugging information, while offering the
following debugging features: abort, step, advanced breakpoints, memory dump, register
window, read/write on-the-fly on RAM and peripherals.
In hot plug mode, you cannot set software breaks, flash program your microcontroller or
perform symbolic debugging.
The constraints on the application are:
● The SWIM_DBG pin must be reserved for debugging (it cannot be used for I/O)
● On the STice, there is no pull-up on the reset pin, therefore you must ensure that there
is a pull-up on reset in the application. Pull-up on the reset pin is provided in the
RLink/STLink hardware.
If your application includes a number of periodic resets (such as watchdog timers), you
might note a difficulty in establishing the connection to the microcontroller. Standard
debugging mode is more appropriate for this kind of application.
7.5 In-circuit debugging limitations
In-circuit debugging limitations that are specific to a microcontroller are listed in the
Discrepancies window. You can access it by selecting Debug Instrument>Emulation
Discrepancies.
The general limitations described in this section apply to all target microcontrollers when in-
circuit debugging.
Stack limitation (ICC only)
For in-circuit debugging, bytes must be reserved on the stack in addition to the memory
reserved for the application. When evaluating the stack size required for your application,
add 5 bytes. Add 5 more bytes (total of 10 bytes) for target MCUs that support software
breakpoints.