HI,
I have a bizarre issue with CCS running code on the ezDSP C5515 usb stick. I have 2 interrupt sources. Both I believe setup properly . Code takne mostly from CSL and other ezDsp example code. I've setup a simple 1 mSec timer (gpt0) which simply incs. a timer variable, does the proper clearing vie IRQ_clear() and a write of 0x0001 to the agregate reg. I also have a one-shot SAR conversion ISR . A start of convert generates an interrupt when conversion is complete. Within the SAR isr , I change the SAR channel and do another start of convert. The ISR and the conversion process continues in definitely. The timer is setup for autoload so it also runs indefinitely. Both ISR have 'interrupt' keywords and disassembly shows good save and restore. If enable each seperately and run some loop test code both appear to work properly. i do have alot of experience so I'm pretty sure the ssetup, servicing, etc are clean. The weirdness starts when I enable both interrupts and run some test code. In debug, I only get one interrupt consistantly, normally the timer, but it has been opposite of that. Now I may get a few seconds worth of SAR samples then It suddeny freezes up. I can look in the IERx regs to make sure both timer and sar are still enabled (0x2010). I can also look in the IFEx regs and see that there is a pending SAR (or timer) pending but I can never get both 'events' to get sensed and have the DSP vector to the ISR. If can manually go into the IEx reg, disable the timer bit. Then manually go to the SARcontrol and force a adcstart bit hi. Then when I resume the code I suddenly get all the SAR ISR to fire and it inititaites another conversion and goes on forever. If the timer is frozen I can disable the SAR and the timer will start interrupting. HELP... any suggestions. Is this a debug/emulator thing?
Regards,
Steve
