SPRUII0F May 2019 – June 2024 TMS320F28384D , TMS320F28384D-Q1 , TMS320F28384S , TMS320F28384S-Q1 , TMS320F28386D , TMS320F28386D-Q1 , TMS320F28386S , TMS320F28386S-Q1 , TMS320F28388D , TMS320F28388S
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 owned by it, clock gating and LPM configuration. It does not hold CPU2 in reset. CPU1 subsystem reset (CPU1.SYSRS) resets CPU1, the peripherals owned by it, many system control registers (including its clock gating and LPM configuration and the peripherals' CPU ownership), and all I/O pin configurations. It also produces a CPU2.SYSRS and CM.RESETn and holds both, CPU2 and CM, in reset (CCS Gel file has code to release CPU2 and CM out of reset on CPU1 debug reset).
Neither SYSRS resets the ICEPick debug module, the device capability registers, the clock source and PLL configurations, the missing clock detection state, the PIE vector fetch error handler address, the NMI flags, the analog trims, or anything reset only by a POR (see Section 3.3.4).