FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [April 2009 Threads] FIQ interrupts on LP23xxPosted by torginus on April 25, 2009 Hi!
I'd like to ask a techincal a question.
I'm using a Philips LPC2378 microcontroller, which has a separate register set for handling FIQ interrupts.
Does it mean, that this makes context saving upon entry unnecessary, so I needn't (and shouldn't) use portSAVE_CONTEXT(), and portRESTORE_CONTEXT() upon entry, and exit from the interrupt handler? Or are there parts of the context that still need to be saved? Is it safe to call FreeRTOS functions from such a 'plain' FIQ interrupt?
Btw, what's the difference between the portSAVE/RESTORE combo and using GCC's builtin __attribute("IRQ"/"FIQ")__ function attributes?
RE: FIQ interrupts on LP23xxPosted by Richard on April 25, 2009 Best not to call API function from the FIQ, and use the standard GCC method of entering the function, not the portSAVE/RESTORE_CONTEXT macros.
You might like to check the implementation of the portENTER_CRITICAL() and portEXIT_CRITICAL() macros to ensure they don't disable and enable FIQ interrupts - unless you want them to.
The __attribute__ method does not save the entire context, often contains bugs (depending on the GCC version) and does not save the context in the form expected by the kernel.
Regards.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|