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] [August 2012 Threads] implementation of "yield from ISR...Posted by Dave Nadler on August 21, 2012 When an ISR does something which logically unblocks a new task (giving a binary semaphore, putting something in a queue), we want to yield. Dumb question perhaps: why not just simulate a timer interrupt ? This would get back to the scheduler quickly and cleanly after the ISR returns. This would mess up anything using the timer for stable timing without some addition work (accumulate partial timer values in the timer ISR and adjust the tick count accordingly), but that's not hard. Might make things simpler ? Still doesn't allow an ISR to mess with queues while running at a higher priority than FreeRTOS. Thoughts ?
Thanks, Best Regards, Dave
RE: implementation of "yield from ISR...Posted by Richard on August 22, 2012 Each port does this in a slightly different way. Faking timer interrupts is not possible on all platforms, and would get complex as you would have to know which was a fake interrupt (so only a context switch was performed) and which was a real interrupt requiring the tick to be incremented and a context switch to be performed - the complexity comes when both things happen simultaneously.
Regards.
RE: implementation of "yield from ISR...Posted by Dave Nadler on September 2, 2012 Thanks for the concise explanation. I added a fake interrupt to a distinct (non-timer) ISR at priority 1; high-priority ISR can force reschedule by triggering the fake interrupt. Seems nice and clean, on PIC24F anyway. Thanks again ! Best Regards, Dave
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|