SPRUHM8K December 2013 – May 2024 TMS320F28374D , TMS320F28375D , TMS320F28376D , TMS320F28377D , TMS320F28377D-EP , TMS320F28377D-Q1 , TMS320F28378D , TMS320F28379D , TMS320F28379D-Q1
On this device, the CPU1 subsystem acts as a master, and by default (upon reset) owns all the configuration and control. Through software running on CPU1, peripherals and I/Os can be configured to be accessible by the CPU2 subsystem and the configuration chosen can be locked. All peripherals are available on CPU1, but not all peripherals are available on CPU2. To see what peripherals can be configured for CPU2, consult the CPUSELn registers in the DEV_CFG_REGS section.
The PLL clock configuration is also owned by the CPU1 subsystem by default, but a clock control semaphore is provided by which CPU2 can grab access to the clock configuration registers.
Each CPU has an NMI module to handle different exceptions during run time. If the NMI was on CPU1, any NMI exception that is unhandled before the NMI Watchdog (NMIWD) timer expiration resets the entire device. If the NMI was on the CPU2 subsystem, then the CPU2 subsystem alone is reset, in which case the CPU1 subsystem is informed by another NMI that the CPU2 subsystem was reset because of NMIWD timer expiration.
Each CPU subsystem a watchdog timer module for software to use. Watchdog timer expiration on CPU2 resets the CPU2 subsystem alone when configured to generate a reset, but watchdog timer expiration on CPU1 resets the entire device.
Except for a CPU2 standalone internal reset such as CPU2.NMIWD or CPU2.WD each time the device is reset, the CPU2 subsystem is held under reset until the CPU1 subsystem brings the CPU2 subsystem out of reset. This is done by the boot ROM software running on the CPU1 core.
This chapter explains the register space of the device system control module that is divided into three categories:
This chapter explains the system control module on both the CPU subsystems.