SPRUJ79 November 2024 F29H850TU , F29H859TU-Q1
On this device, the CPU1 subsystem acts as a controller, and by default (upon reset), the CPU1 subsystem owns all the configuration and control. Through software running on CPU1, peripherals and I/Os can be configured to be accessible by the other CPU subsystems and the chosen configurations can be locked.
The PLL clock configuration is also owned by the CPU1 subsystem by default and HSM subsystem can also access clock configuration if permissions are enabled (by default enabled).
Each CPU can be independently configured to accept interrupts from different peripherals. The interrupt path is divided into three stages – the peripheral (in some cases ESM also), the PIPE, and the CPU. All stages must be configured and enabled for an interrupt to propagate to the CPU.
Each CPU has their own NMI module to handle different exceptions during run time. If the NMI was on CPU1, any NMI exception that is not handled before the NMI Watchdog (ESM NMIWD) timer expiration resets the entire device using XRSn. If the NMI was on any other CPU subsystem, then the specific CPU subsystem is reset (or the entire device is reset depending on the configuration) and all other CPU subsystems can be informed using ESM that the CPU subsystem was reset because of NMIWD timer expiration.
Each CPU subsystem has their own watchdog timer module for software to use. Watchdog timer expiration on CPU1 resets the entire device and Watchdog timer expiration on other CPU resets that specific CPU subsystem alone when configured to generate a reset.
The register space of the device system control module can be found in Section 3.13.
This chapter explains the system control module on all the CPU subsystems.