In a message dated 9/13/01 12:08:42 PM Pacific Daylight Time,
olin_piclist@EMBEDINC.COM writes:


> First, you still have to remove the interrupt condition.  Second, if you're
> just going to set a flag in the interrupt routine then check that flag in
> the foreground code, you might as well check the interrupt condition flag in
> the foreground code directly with interrupts off.
>
> Despite these specific points, I agree with the general strategy of doing as
> little as possible in the interrupt routine.
>
>

Olin,

I'm starting to agree with the fact that I should do away with interrupts as
they're causing more problems than anything! I took another look at the code
this morning. The interrupt is neverending because the PC never wants to go
to "intend" no matter what! If I add bcf PORTB,2 after a few instructions in
the ISR and scope it, I'll see the expected waveform. However, if I replace
the bcf instruction with just a plain ole "goto intend" (where I've added the
bcf instruction) it'll never happen, what gives?

Regards,

Tim H.

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu