• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 21 subscribers
  • Views 720 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
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

Interrupt XC2267

MOMO

Hello,

I'm working on the XC164CM. I have a problem concerning the interrupt routine.

To declare an interrupt we have several ways to do it.

void itFunc (void) interrupt vectorNb

or

void itFunc (void) interrupt NONE=CACHED

when I declare my interrupt with the first one "void itFunc (void) interrupt vectorNb" I dont have any problem.

but when using the second declaration "void itFunc (void) interrupt NONE=CACHED" keil generate errors.
to use this declaration is there any directive to use?

can you help me please

Thanks

Parents
  • 0 in reply to Thomas Brandl

    When using the CACHED directive then no entry is placed in the vector table for this vector and it is up to you to define the values in the registers FINTxCSP and FINTxADDR where x can be either 0 or 1. This is explained in the help file when searching on CACHED.

    Thus this gives you the option to define two interrupts that would save you the time from going to the vector table and then jumping again to your interrupt service routine (.i.e directly jumping to your ISR)

Reply
  • 0 in reply to Thomas Brandl

    When using the CACHED directive then no entry is placed in the vector table for this vector and it is up to you to define the values in the registers FINTxCSP and FINTxADDR where x can be either 0 or 1. This is explained in the help file when searching on CACHED.

    Thus this gives you the option to define two interrupts that would save you the time from going to the vector table and then jumping again to your interrupt service routine (.i.e directly jumping to your ISR)

Children
No data