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] [March 2011 Threads] CoRoutine and Task communication possible?Posted by Akos on March 14, 2011 Hello!
Why isn't it possible to pass data between a coroutine and a task? Perhaps using a queue? Also, even regarding that there is a reason for it that I do not yet understand, why wouldn't we be able to use the ISR routines from the CoRoutines? The only obstacle is that any called function may not block (because of the shared stack), but the ISR funcitons never block, so they could theoretically be used from the coroutine environment.
And my other solution would be to define an svc (on cortex-m3 for example) to do the queueing. SVC 0 is used for task switching, but in my opinion I could use another SVC to do the queue up work. In this case the queueing would happen from isr environment, so the Queue_ISR functions could be used. Some adjustment must be made to the ported code, so that the SVC handler extracts the svc code, and depending on the svc number queues or switches tasks. Do you think this could work?
Regards, Ákos Vandra
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|