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] [October 2011 Threads]
Hi there,
I have a small chunk of code below that needs to be atomic and may be called from ISR or task.
Variable bool bFromIsr is true if the section is called from ISR false if from task.
Two questions:
1. Is there any OS variable I can examine to know if I am presently in an ISR? (E.g. is ISR nesting level tracked somewhere, I could not find it.) Or do I have to independently provide a value for bFromIsr?
2. Have I chosen the correct macros to do this? I had thought that I should not have to call directly any functions prefixed by "port...". What is the correct macro for "suspend interrupts from an interrupt"?
Thanks and regards,
Owen
//because this can be called indirectly from multiple tasks or ISRs the action needs to be atomic
if (bFromIsr) {
uxSavedInterruptStatus = portSET_INTERRUPT_MASK_FROM_ISR();
} else {
taskENTER_CRITICAL();
}
// BEGIN section of atomic code ////////////////
//check and update the high water mark
if (i>logPoolHwm)
{
//since we start scanning from zero, i represents the hwm
logPoolHwm = i;
}
//mark it as in use
logPool.inUse = 1;
// END section of atomic code ////////////////
if (bFromIsr) {
portCLEAR_INTERRUPT_MASK_FROM_ISR( uxSavedInterruptStatus );
} else {
taskEXIT_CRITICAL();
}
FreeRTOS doesn't have any flag like that built in. Depending on the hardware architecture, you may be able to check a hardware register to detect this, or you could just make your bFromIsr a global, and require that ISRs begin with a bFromIsr++ and end with a bFromIsr-- (and make it really an int and not a bool like the name implies).
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.