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] [September 2014 Threads] How to determine current context type - interrupt or taskPosted by luhu on September 21, 2014 Hello,
Searched a little but didn't found answer.
Is there some function or other method in FreeRTOS that allows to determine if program is currently in interrupt or process context?
I want to implement a function that will use xQueueSend. But that function might be called both from process or interrupt and I would like to avoid creating another version of that function which will use xQueueSendFromISR.
Best Regards,
Michal
How to determine current context type - interrupt or taskPosted by rtel on September 21, 2014 Which port are you using?
Regards.
How to determine current context type - interrupt or taskPosted by luhu on September 21, 2014 I am using LPC4330 MCU and base on examples from lpcopen.
Best Regards,
Michal
How to determine current context type - interrupt or taskPosted by rtel on September 21, 2014 In which case I think you can ask the hardware for the context as follows:
if( ( portNVICINTCTRLREG & 0x1F ) == 0 )
{
/* Not in an interrupt. /
}
else
{
/ In an interrupt. */
}
(portNVICINTCTRLREG is already defined, assuming you are using GCC as you mention lpcopen).
Regards.
How to determine current context type - interrupt or taskPosted by luhu on September 21, 2014 Thanks for fast reply. Will try this.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|