Changing IPC's Interrupt Number

Depending on what platform you are on (assuming c6000), You can modify it in you *.cfg file by doing something like the following:

var NotifySetup = xdc.useModule('ti.sdo.ipc.family.c647x.NotifySetup');

NotifySetup.dspIntVectId = x;    // x must be an interrupt vector between 4-15

Judah

That did it!  Many thanks Judah!

Looking forward though we plan to have separate applications running on separate cores and for proprietary reasons we plan to use different IPC interrupts on each IPC using core.

Would this mean that we'll need a different IPC/Notify build for each core?  Or is there a way to use a single shared binary and at run time inform the IPC/Notify module which interrupt to use?

As Judah implied, please tell us which device you are using and which type of core you are specifically asking about. Also, the SYS/BIOS version may be helpful and whether you are using the MCSDK.

The Wiki app note Using DSP/BIOS on Multi-Core DSP Devices may not directly apply to IPC and your device, but it discusses some of the issues and tradeoffs with using a shared binary image.

Regards,
RandyP

Currently working with evm TMS320C6678, and Core 0 and Core 1 will use IPC communications but will need to use different interrupt vectors for notification.  

I'll in the mean time look at your link.

It is common to use the same interrupt vector. After the HWI_dispatcher is commonly an IPC dispatcher that routes each IPC code to a different function. The IPC dispatcher could also check the register DNUM to determine if the code is running on Core0 or Core1, and then it can call from a different set of function pointers depending on which core is running. The MCSDK / IPC may already contain this functionality, but I do not know.

Regards,
RandyP