TMS320F28388D: CPU2 watchdog

Hello,
what happens with the CPU2 watchdog if I only program CPU1 project is programmed in flash. CPU2 watchdog is on per default and should generate and CPU1 NMI reset. Right? In our examples this will lead in an endless loop.

The NMI on the CPU1 lead into an endless loop.

static void Interrupt_nmiHandler(void)
{
    //
    // A non-maskable interrupt has occurred, indicating that a hardware error
    // has occurred in the system.  You can use SysCtl_getNMIFlagStatus() to
    // to read the NMIFLG register and determine what caused the NMI.
    //
    ESTOP0;
    for(;;)
    {
        ;
    }
}

This means that you should always program CPU1 project and an CPU2 project which handles the watchdog. Right?

Regards, Holger