[Please reply to the list] I've used it without much of a problem. The only other item to check is, if you have global interrupts enabled. Just to be sure, set a breakpoint in the vector table instead of your function (in case you have errors in the vector address). Another item to check is, when you write from DSP B to DSP A, watch the VIRPT register in the DSP A window (instead of MMS view) and ensure that it gets written to (perhaps you are making a mistake in the MMS address for DSP A). Note, it's very easy to get the processor IDs and the names (A and B) mixed up. Cheers Bhaskar --- In adsp@y..., "Waldron, Donald M" <donald.m.waldron@b...> wrote: > Greetings, > > We are attempting to cause a vector interrupt from DSP_B to DSP_A. We are > correctly writing the address of the DSP_A' function from DSP_B via DSP_A's > VIRPT register (using multiprocessor addressing). On DSP_A, the IRPTEN is > set, the VIRPT mask bit is set, but no interrupt occurs. > > Manually setting the IRPTL bit on DSP_A does cause a vector interrupt. > > Are there any nuances with the vector interrupts? Anyone have experience > with getting the vector interrupts working? > > Regards, > > Don Waldron |