Matt Rhys-Roberts wrote:
> In other words, do I have to name or move this ISR temporary area
> somehow to enable 'normal' execution of arbitrary functions?

The part of the manual you quoted gives no hint this is even a issue.
Manually placing a relocatable section is usually a bad idea, and giving it
a name only means it won't have its default name.  But in any case, I can't
see any reason you should think the name or placement of the section will
matter to runtime operation.

Step back and think about what is going on.  The location and name of the
temporary data used by the interrupt routine doesn't matter from that point
of view either.  The compiler is merely making sure that temporary RAM
locations used during interrupt are not reused anywhere else, since it has
to assume a interrupt could happen when in any of the other routines.  This
also means you can't call any of these other routines from the interrupt
routine unless those other routines are compiled in such a way as to not us=
e
static temporary variables.  In other words, any routine called during
interrupt must be reenterable.  That means static temporary variables are
out.  All temporary variables need to be dynamically allocated, probably by
using the stack (although there are other ways).  Most likely your compiler
defines a particular way of waving a dead fish over a routine (often called
a pragma) to indicate it must be reenterable, or maybe that's the default
when no dead fish is waved.


********************************************************************
Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
(978) 742-9014.  Gold level PIC consultants since 2000.
--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.