- IAR Embedded Workbench for Arm 9.70.x
- C-SPY Debugging
- Breakpoints
- Reference information on breakpoints
- Data Log breakpoints dialog box (C-SPY hardware drivers)
Data Log breakpoints dialog box (C-SPY hardware drivers)
The Data Log breakpoints dialog box is available from the context menu in the editor window, Breakpoints window, the Memory window, and in the Disassembly window.

Use the Data Log breakpoints dialog box to set a maximum of four data log breakpoints.
You can set a data log breakpoint on 8, 16, and 32-bit variables.
See also Data Log breakpoints and Getting started using data logging.
Requirements
A device and a debug probe with support for SWO.
Trigger at
Specify the data location of the breakpoint. Alternatively, click the Edit button to open the Enter Location dialog box, see Enter Location dialog box.
Access Type
Selects the type of memory access that triggers the breakpoint:
- Read/Write
Reads from or writes to location.
- Read
Reads from location; except for Cortex-M3, revision 1 devices.
- Write
Writes to location; except for Cortex-M3, revision 1 devices.
Size
Determines whether there should be a size—in practice, a range—of locations where the breakpoint will trigger. Each fetch access to the specified memory range will trigger the breakpoint. Select how to specify the size:
- Auto
The size will automatically be based on the type of expression the breakpoint is set on. For example, if you set the breakpoint on a 12-byte structure, the size of the breakpoint will be 12 bytes.
- Manual
Specify the size of the breakpoint range in the text box.
Trigger range
Shows the requested range and the effective range to be covered by the trace. The range suggested is either within or exactly the area specified by the Trigger at and the Size options.
- Extend to cover requested range
Extends the breakpoint so that a whole data structure is covered. For data structures that do not fit the size of the possible breakpoint ranges supplied by the hardware breakpoint unit, for example three bytes, the breakpoint range will not cover the whole data structure. Note that the breakpoint range will be extended beyond the size of the data structure, which might cause false triggers at adjacent data.