PIC interrupt routine help

There are some loose ends here. When you say 'simple pic programming' I assume you think of Assembly programming.

You say pic, but not the type of chip you use.

I'm not sure what you really mean when talking about 'enable an interrupt routine'. Can you expand on this a bit? If you want to enable an interrupt, you need to decide which inbuilt interrupt source you want to use.
If you on the other hand want to call a routine, you really don't need an interrupt, since you are already processing the 'call'.

So, please leave some more info on this.

 

The beauty of interrupts is that the chip will continue to do other tasked full time, it will simply pause and jump to the interrupt when triggered...

Thus if your ADC read, is done via an interrupt say every second or so, you can have the chip do whatever in between those interrupts... Or use it in reverse, have the main program looping on an ADC read, and when it's time use an interrupt to jump to whatever, an then return to the ADC read routine seamless...

As gorgon said you have to decide what interupt to use, an interupt is basically a full proof 'goto' that isn't locking into any location in the program, when triggered it will pause the main program wherever it is and make the interrupt 'goto' jump and return where it left off... Most of the time this is done via a change in an external port or using a timer at preset intervals...

 

nepow,

But what you describe is done just as well by a call. An interrupt has no advantage if it is always triggered from the same spot in the program, which seems to be the end of your ADC read.

If I understand it, your program is something like this:

<initialization>
main_loop:
<do some stuff>
<read the ADC>
<handle the ADC results> // this seems to be what you want to make an interrupt
<do some more stuff>
goto main_loop

What CC is descrbing would be more like:

<initialization>
<set up ADC interrupt>
<start first ADC reading>
main_loop:
<do some stuff>
goto main_loop:

interrupt:
<get the ADC reading>
<do something with the ADC reading>
<start next ADC>
<return from interrrupt>

With this kind of code, the ADC reading happen asychronously with the main program. This is the advantage of interrupts, they can happen at any time, and the main program doesn't even know they are happening (only that it has lost time, like people picked up by aliens)

Bob