ctl_enter/exit_isr on every ISR?

Follow

Trevor O'Grady

• March 04, 2010 16:11

I have been adding ctl_enter_isr and ctl_exit_isr to all ISR handlers. However the following taken from the Rowley on-line documentation suggests that it is only required for ISR that uses CTL services. I assume that refers to an ISR that could call a CTL function (to signal or task switch etc.). Can anyone confirm this?

 

Interrupt handlers

A Cortex-M3 interrupt handler that uses CTL services should have the following code on entry and exit

void
SysTick_ISR()
{
  ctl_enter_isr();
  …
  // handle interrupt
  …
  ctl_exit_isr();
}

1

• 

  Leo Bosnjak

  • April 08, 2010 11:38

  Hi,

  I think, I can confirm that, because on my MSP430 I've only declared the timer tick ISR as __ctl_interrupt (which does the same as your code I think), because I don't want a task switch to happen after other interrupts..

  kr, Leo

  0

  Comment actions Permalink
• 

  Michael Johnson

  • April 08, 2010 14:01

  You can use __interrupt for interrupt handling functions that don't use CTL services.

   

  Regards

  Michael

  0

  Comment actions Permalink
• 

  Bruce Chippindale

  • June 07, 2012 21:07

  If writing in C for the stm32f2xx   ?  

   

  What does __interrupt do?   It is not in the pdf    

  0

  Comment actions Permalink
• 

  Michael Johnson

  • June 07, 2012 21:25

  This is a special in the MSP430 compiler - unlike the Cortex-M3 regular C functions can't be used as interrupt handlers for MSP430.

  0

  Comment actions Permalink

Please sign in to leave a comment.