3.
Set the breakpoint with
‘Debug
è
Set Breakpoint’
.
ð
The according command line is marked with a circle.
4.
To activate the breakpoint click on
‘Debug
è
Breakpoints Active’
.
ð
The circle is changed to a filled circle.
5.
Bring your CPU into RUN.
ð
When the program reaches the breakpoint, your CPU switches to the state
HOLD, the breakpoint is marked with an arrow and the register contents are
monitored.
6.
Now you may execute the program code step by step via
‘Debug
è
Execute Next Statement’
or run the program until the next breakpoint via
‘Debug
è
Resume’
.
7.
Delete (all) breakpoints with the option
‘Debug
è
Delete All Breakpoints’
.
n
The RUN-LED blinks and the STOP-LED is on.
n
The execution of the code is stopped. No level is further executed.
n
All times are frozen.
n
The real-time clock runs is just running.
n
The outputs were disabled (BASP is activated).
n
Configured CP connections remain exist.
The usage of breakpoints is always possible. Switching to the operating
mode test operation is not necessary.
With more than 2 breakpoints, a single step execution is not possible.
Behavior in operating
state HOLD
System 300S
+
Deployment CPU 315-4PN23
Operating modes > Overview
HB140 | CPU | 315-4PN23 | en | 18-02
62
