NXP Semiconductors K32 L2A Series, Reference Manual, Page: 127 / 1379

6.2.2.7 Stop mode acknowledge error (SACKERR)
This reset is generated if the core attempts to enter Stop mode or Compute Operation, but
not all modules acknowledge Stop mode within 1025 cycles of the 1 kHz LPO clock.
A module might not acknowledge the entry to Stop mode if an error condition occurs.
The error can be caused by a failure of an external clock input to a module.
6.2.2.8 Software reset (SW)
The SYSRESETREQ field in the NVIC Application Interrupt and Reset Control register
can be set to force a software reset on the device. (See Arm's NVIC documentation for
the full description of the register fields, especially the VECTKEY field requirements.)
Setting SYSRESETREQ generates a software reset request. This reset forces a system
reset of all major components except for the debug module. A software reset causes
RCM_SRS[SW] to set.
6.2.2.9 Lockup reset (LOCKUP)
The LOCKUP gives immediate indication of a seriously errant kernel software. This is
the result of the core being locked, because of an unrecoverable exception following the
activation of the processor’s built-in system state protection hardware.
The LOCKUP condition causes a system reset and also causes RCM_SRS[LOCKUP] to
set.
6.2.2.10 MDM-AP system reset request
To initiate a system reset, set the System Reset Request field in the MDM-AP control
register. This is the primary method for resets via the SWD interface. The system reset is
held until this field is cleared.
To hold the core in reset as the rest of the chip comes out of system reset, set the Core
Hold Reset field in the MDM-AP control register.
Chapter 6 Reset and Boot
K32 L2A Reference Manual, Rev. 2, 01/2020
NXP Semiconductors 127