Hi,
We have some code which (for efficiency reasons, every cycle counts for this application) uses the IPC peripheral by directly accessing the peripheral's registers. However, we now have to integrate a library which uses ti.sdo.ipc.SharedRegion, therefore IPC_start() has to be called - which in our cases uses ti.sdo.ipc.family.c647x.NotifyCircSetup.
1. What I wonder : Is it save to remove that interrupt handler later on, when SharedRegion is the only thing provided by IPC we use?
2. The handler is registered at an interrupt specified in a variable called "NotifyCircSetup_dspIntVectId". Looking at the header, the only thing I see is:
/* dspIntVectId */
#ifdef ti_sdo_ipc_family_c647x_NotifyCircSetup_dspIntVectId__D
#define ti_sdo_ipc_family_c647x_NotifyCircSetup_dspIntVectId (ti_sdo_ipc_family_c647x_NotifyCircSetup_dspIntVectId__D)
#else
#define ti_sdo_ipc_family_c647x_NotifyCircSetup_dspIntVectId (ti_sdo_ipc_family_c647x_NotifyCircSetup_dspIntVectId__C)
typedef xdc_UInt CT__ti_sdo_ipc_family_c647x_NotifyCircSetup_dspIntVectId;
__extern __FAR__ const CT__ti_sdo_ipc_family_c647x_NotifyCircSetup_dspIntVectId ti_sdo_ipc_family_c647x_NotifyCircSetup_dspIntVectId__C;
#endif
Any idea where this value is defined?
Thank you in advance, Clemens
