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.

TMS320F28335 Optimization: --Opt_level=2 causes non-enabled interrupt to trigger

Other Parts Discussed in Thread: TMS320F28335

I'm currently working on a "simple" audio echo program with the TMS320F28335, using the explorer's kit and the AIC23 that's on it. I'm using that program to play around with the optimization tools to see how much signal processing I can do with it. I've used the optimization assistant and was able to change the --opt_for_speed parameter without any problem. However, when I change the optimization level from 1 to 2 my program suddenly triggers the interrupt next to the one I want on the PIE interrupt table (so, instead of using MRINTA, like how I want it to, it triggers MXINTB.)This occurs even when I actively turn off the interrupt (by un-setting the enable flag.) 

Since opt level 2 only deals with loops (of which the interrupt set-up is not a part of) and globals (of which the interrupt set-up is also not a part of) I'm not entirely sure what's causing this. If I keep the opt. level to something lower, the program works as intended, so something involving that mode of optimization is bugging it.

Code is attached if it helps. Right now it's just an echo with a 10 sample delay in one ear to emulate a FIR filter.

4174.McBSP_Audio_LeftRight_1int_1phase.zip