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] Mechanism for IP(rocessor)CPosted by Kreyer on August 9, 2012 Hi,
Iam planning to use FreeRTOS in one of our projects. We want to run it on a dual core ARM cortex-a9. As far as Iam aware FreeRTOS does not support SMP, so if we want to utilize both cores we need to run it in AMP mode, i.e. one FreeRTOS instance per core. Surely we will need a mechanism to exchange information between both cores. Is there any support for IPC messages in FreeRTOS? If not, Iam planning to write my own service. Makes it sense to implement such a service within FreeRTOS architecture? (e.g. accessing port interface when it needs target specific services like shared memory allocation or synchronization events between the cores). Otherwise, I simply would implement it as a project specific application utilizing FreeRTOS and target specific APIs.
Thanks for all information you have on this.
Steve
RE: Mechanism for IP(rocessor)CPosted by Richard on August 10, 2012 Have a look here:
http://interactive.freertos.org/entries/21706962-xilinx-freertos-port-for-zynq
I believe this is designed to run FreeRTOS on one A9 core, and Linux on another. A Linux style inter-core communications API is used.
There will be another AMP protocol being published (by a third party) soon too, but I can't say exactly when that will be yet.
Regards.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|