SPRUIZ1B July 2023 – August 2024 TMS320F28P650DH , TMS320F28P650DK , TMS320F28P650SH , TMS320F28P650SK , TMS320F28P659DH-Q1 , TMS320F28P659DK-Q1 , TMS320F28P659SH-Q1
FILE: nmi_ex1_cpu1handling.c
This example demonstrates how to handle an NMI.
The watchdog of CPU2 is configured to reset the core once the watchdog overflows and in the CPU1 the NMI is triggered. The NMI status is read and is verified to be due to CPU2 Watchdog reset. The NMI ISR reboots the CPU2 core and the process is repeated.
NOTE: In the default CPU2 linker cmd file, GS4, FLASH_BANK3 and FLASH_BANK4 are used for allocating various CPU2 sections. The CPU1 application assigns the ownership of these memory regions to CPU2. Please note that CPU2 .out file can be loaded only after CPU1 completes this configuration
The erase setting (CPU1/CPU2 On-Chip Flash -> erase setting) needs to be configured as selected banks only (Choose the corresponding BANKS allocated for CPUs) or necessary sectors only before loading CPU1/CPU2.out file (This is applicable only for FLASH configuration)
Watch Variables