AVR-Chat

Absolutely!   I had a fully implemented interrupt vector table, I had 
miscounted and had some rjmps where there ought to have been some 
reti's, and vice  versa.  my interrupt vector table template will be 
receiving full commentary TODAY to insure that this never happens again!

(and, to complicate things,  the debug routine I had written to show me 
which interrupt was being called didn't work either *doh*).

Micro Brix wrote:
>
> On 1/18/07, Jim Wagner <jim_d_wagner@applelinks.net 
> <mailto:jim_d_wagner%40applelinks.net>> wrote:
> >
> > That is why I have adopted the practice of installing a
> > full vector table, with all the standard labels and filling
> > the unused ones with RETI or jump to an error handler.
>
> The only way to fly! :)
> I've always done this, or a close variant.
>
> In some apps, I've used a jump to a "halt and DONT catch fire" routine,
> where the app controlled things that could easily get nasty if left on too
> long. This routine safeties the outputs, and then sits in a loop.
>
> My templates all have ISRs that turn off that particular int. I start my
> apps with this, and then change the ones I want to use into real ISRs, and
> if I get squeezed for code space then I might change the turnoffs to 
> simpler
> versions, or to RETIs.
>
> I dont' believe in EVER writing without a fully implemented vector table
> though.
>
>