This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Grouping ISRs by priority for overlaying

Just out of curiosity. Is there a way to tell the linker that ISRs have the same priority and thus cannot interrupt each other and can safely be overlayed?

P.S.: And what is the correct passive form of 'to overlay'?

Parents Reply Children
  • I know those and make intense use of them, but aren't interrupts always root nodes?

    Can I create a virtual function that calls them, which really only exists in the call tree and not in the code?

    Should I write a function for each priority level that calls all the ISRs of the same priority? But I'd expect ISRs are subject to a number of special treatments by the compiler and linker. I'm afraid the effects could be quite destructive.