TMS320F28032: When the MCU is connected to the emulator and runs together, what conditions will cause them to be disconnected?

Shaoxing,

Executing an illegal ISR should not cause an emulator disconnect.  This should branch to the Illegal ISR and proceed from there. 

Oftentimes, since this is not an ISR that the customer expects to happen, they use our default ISR file that we ship with the example files.  The default code is an ESTOP0(which only breaks when the emulator is connected) and an infinite "for" loop.

If customer does not change the default ISR that we include, what will typically happen is eventually the watchdog will time out and issue a XRSn.  This can cause the emulation connection some issues, and may disconnect due to the action of the C2000 after it sees a XRSn active signal.

If the customer is debugging an Illegal ISR, then I would suggest they disable the internal WD in that ISR so this no longer happens.

Best,

Matthew

Shaoxing,

The below code should be in F2803x_SysCtrl.c but customer can use as is

void
DisableDog(void)
{
    EALLOW;
    SysCtrlRegs.WDCR= 0x0068;
    EDIS;
}

Best,

Matthew