set. To release the CPU, write a '1' to STATUSA.CRSTEXT. STATUSA.CRSTEXT will then be set to zero.
Writing a '0' to STATUSA.CRSTEXT has no effect. For security reasons, it is not possible to release the
CPU reset extension when the device is protected by the NVMCTRL security bit. Trying to do so sets the
Protection Error bit (PERR) of the Status A register (STATUSA.PERR).
Figure 14-2. Typical CPU Reset Extension Set and Clear Timing Diagram
DSU CRSTEXT
Clear
SWCLK
CPU reset
extension
CPU_STATE
reset
running
RESET
Related Links
NVMCTRL – Non-Volatile Memory Controller
on page 515
on page 523
14.6.3. Debugger Probe Detection
14.6.3.1. Cold Plugging
Cold-Plugging is the detection of a debugger when the system is in reset. Cold-Plugging is detected when
the CPU reset extension is requested, as described above.
14.6.3.2. Hot Plugging
Hot-Plugging is the detection of a debugger probe when the system is not in reset. Hot-Plugging is not
possible under reset because the detector is reset when POR or RESET are asserted. Hot-Plugging is
active when a SWCLK falling edge is detected. The SWCLK pad is multiplexed with other functions and
the user must ensure that its default function is assigned to the debug system. If the SWCLK function is
changed, the Hot-Plugging feature is disabled until a power-reset or external reset occurs. Availability of
the Hot-Plugging feature can be read from the Hot-Plugging Enable bit of the Status B register
(STATUSB.HPE).
Figure 14-3. Hot-Plugging Detection Timing Diagram
SWCLK
Hot-Plugging
CPU_STATE
reset
running
RESET
The presence of a debugger probe is detected when either Hot-Plugging or Cold-Plugging is detected.
Once detected, the Debugger Present bit of the Status B register (STATUSB.DBGPRES) is set. For
Atmel SAM L22G / L22J / L22N [DATASHEET]
Atmel-42402E-SAM L22G / L22J / L22N_Datasheet_Complete-07/2016
79