This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DSPLIB cause system reset when interrupt occur

I am using dsplib function on dm6446. The dsplib's version is  c64x+dsplib 2.1.1. I execute DSP_mat_mul() or DSP_mul32() in a infinite loop in my application.
If I don't enable interrupt, the function can work correctly. But, when I enable interrupt of timer, it cause DSP-side reset on CCS3.3 and show below message.
Sometime, it may casuse system crash, so I reset system and re-connect the dm6446.
By the way, I try enable and disable interrupt across dsplib function by RINT and DINT, it is in the same situation.

So, I try another function like DSP_dotprod() and DSP_fir_gen_hM17_rA8X8() in my application. These function could work correctly even if the interrupt happened.
Is there any suggestion?

 

CCS message
-------------------------------------------
Trouble Halting Target CPU: Error 0x00001024/-1137 Error during: Register, Execution, Target,   It appears that the target is being held in reset.  This may be due to Wait-In-Reset (WIR) configuration set by the EMU0=0 and EMU1=1 pin settings.  If this is the case, DISCONNECT all CONNECTED devices including icepick and then select RETRY to clear the WIR configuration.  If this is a multi-core system, the master CPU may not be releasing the DSP/MCU from reset.  Please check your configuration in CC_setup and/or your GEL file to ensure that nothing is blocking the DSP/MCU from being released from reset 
Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint opcodes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging.
Trouble Determining Current Execution Packet(s): Error 0x20010000/-2180 Severe Error during: RTDX,  RTDX_ERR_PORTCFG Error Occured at 0x00000000 
Trouble Determining Current Execution Packet(s): Error 0x20010000/-2180 Severe Error during: RTDX,  RTDX_ERR_PORTCFG Error Occured at 0x00000000 
Trouble Determining Current Execution Packet(s): Error 0x20010000/-2180 Severe Error during: RTDX,  RTDX_ERR_PORTCFG Error Occured at 0x00000000 
Trouble Determining Current Execution Packet(s): Error 0x20010000/-2180 Severe Error during: RTDX,  RTDX_ERR_PORTCFG Error Occured at 0x00000000 
Trouble Determining Current Execution Packet(s): Error 0x20010000/-2180 Severe Error during: RTDX,  RTDX_ERR_PORTCFG Error Occured at 0x00000000 
Trouble Determining Current Execution Packet(s): Error 0x20010000/-2180 Severe Error during: RTDX,  RTDX_ERR_PORTCFG Error Occured at 0x00000000 
Trouble Determining Current Execution Packet(s): Error 0x20010000/-2180 Severe Error during: RTDX,  RTDX_ERR_PORTCFG Error Occured at 0x00000000 
Trouble Determining Current Execution Packet(s): Error 0x20010000/-2180 Severe Error during: RTDX,  RTDX_ERR_PORTCFG Error Occured at 0x00000000 
Trouble Determining Current Execution Packet(s): Error 0x20010000/-2180 Severe Error during: RTDX,  RTDX_ERR_PORTCFG Error Occured at 0x00000000 
Trouble Determining Current Execution Packet(s): Error 0x20010000/-2180 Severe Error during: RTDX,  RTDX_ERR_PORTCFG Error Occured at 0x00000000 
Trouble Determining Current Execution Packet(s): Error 0x20010000/-2180 Severe Error during: RTDX,  RTDX_ERR_PORTCFG Error Occured at 0x00000000 
Trouble Determining Current Execution Packet(s): Error 0x20010000/-2180 Severe Error during: RTDX,  RTDX_ERR_PORTCFG Error Occured at 0x00000000 
Trouble Determining Current Execution Packet(s): Error 0x20010000/-2180 Severe Error during: RTDX,  RTDX_ERR_PORTCFG Error Occured at 0x00000000 
Trouble Determining Current Execution Packet(s): Error 0x20010000/-2180 Severe Error during: RTDX,  RTDX_ERR_PORTCFG Error Occured at 0x00000000 
-------------------------------------------------