Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Real time embedded FreeRTOS mailing list 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem TCP & FAT Training




Loading

Pic port and interrupts

Posted by Marcel van Lieshout on February 4, 2005
When an interrupt fires, the interrupthandler is called in the context of the currently executing task. Shouldn't the first thing that is done in the interrupthandler be a contextsave?
Now each interrupttype has to determine by itself if a contextsave is needed.
Or am I missing something?

RE: Pic port and interrupts

Posted by Richard on February 4, 2005
The interrupt handler prvLowInterrupt() in port.c first checks to find the source of the interrupt. No context has been saved yet so it is *VERY* important that no code is added to this function that could change the context. If you look at the assembler of the code that already exists you will see that nothing gets modified.

If the interrupt was the RTOS tick then the ISR does first save the context before switching, and restoring the new context.

If the interrupt was not the RTOS then what happens is application dependent. If the interrupt wants to cause a task switch it can do by calling taskYIELD - but this MUST only be done after the interrupt source has been cleared. See vSerialRxISR() for an example. This then saves the context and performs the switch as per required. This means the saved context is as it is within the ISR - the ISR is not completed. When the task runs again it will start from the point it left in the ISR and complete the ISR. The ISR cause was already cleared so this is ok - it is as if the ISR completed in one go.

The save and restore macros handle the interrupt flag settings that make this possible. See the comments above the portSAVE_CONTEXT and portRESTORE_CONTEXT macros.


[ Back to the top ]    [ About FreeRTOS ]    [ Sitemap ]    [ ]




Copyright (C) 2004-2010 Richard Barry. Copyright (C) 2010-2016 Real Time Engineers Ltd.
Any and all data, files, source code, html content and documentation included in the FreeRTOSTM distribution or available on this site are the exclusive property of Real Time Engineers Ltd.. See the files license.txt (included in the distribution) and this copyright notice for more information. FreeRTOSTM and FreeRTOS.orgTM are trade marks of Real Time Engineers Ltd.

Latest News:

FreeRTOS V9.0.0 is now available for download.


Free TCP/IP and file system demos for the RTOS


Sponsored Links

⇓ Now With No Code Size Limit! ⇓
⇑ Free Download Without Registering ⇑


FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

Renesas Electronics Gold Alliance RTOS Partner.jpg

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers

Atmel RTOS partner supporting ARM Cortex-M3 and AVR32 microcontrollers

STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Xilinx Microblaze and Zynq partner

Silicon Labs low power RTOS partner

Altera RTOS partner for Nios II and Cortex-A9 SoC

Freescale Alliance RTOS Member supporting ARM and ColdFire microcontrollers

Infineon ARM Cortex-M microcontrollers

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

Cypress RTOS partner supporting ARM Cortex-M3

Fujitsu RTOS partner supporting ARM Cortex-M3 and FM3

Microsemi (previously Actel) RTOS partner supporting ARM Cortex-M3

Atollic Partner

IAR Partner

Keil ARM Partner

Embedded Artists