SPRUJ79 November 2024 F29H850TU
During development, it is sometimes necessary to reset the CPU and the peripherals without disconnecting the debugger or disrupting the system-level configuration. To facilitate this, each CPU has a subsystem reset, which can be triggered by a debugger using Code Composer Studio IDE. CPU2 subsystem reset (CPU2.SYSRS) resets only CPU2, the peripherals, and the clock gating and LPM configuration. It does not hold CPU2 in reset. CPU3 subsystem reset (CPU3.SYSRS) resets only CPU3, the peripherals, and the clock gating and LPM configuration. CPU1 subsystem reset (CPU1.SYSRS) resets CPU1, the peripherals, many system control registers (including the clock gating and LPM configuration and the peripheral CPU ownership), and all I/O pin configurations. CPU1.SYSRS also produces a CPU2.SYSRS and CPU3.SYSRS (CCS Gel file may have code to release CPU2 and CPU3 out of reset on CPU1 debug reset).
Figure 3-2 explains how the all CPU SYSRS and Software Reset signals are connected to cause particular peripheral to reset in the device.
Neither SYSRS resets the debug module, the device capability registers, the clock source and PLL configurations, the missing clock detection state, the PIPE vector fetch error handler address, the NMI flags, the analog trims, or anything reset only by a POR (see Section 3.3.4).