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 2015 Threads] Best practice to share same resources between tasksPosted by chaabanemalki on March 12, 2015 Hello,
I'm working on a project where I have to write to an SD card from more than one task. For this I use mutex.
I use SPI to communicate with the SD card, plus I have to use an EEPROM that share the same SPI bus witht he SD card. First idea that came in my mind is to use one mutex to share the SPI bus between SD card and EEPROM and also between different tasks that write/read from the SD card.
Is there a better efficient way to manage my case ?
Best practice to share same resources between tasksPosted by davedoors on March 12, 2015 Mutex is a good option for you. It will be obtained by the highest priority thread waiting on it, and has priority inheritance.
Best practice to share same resources between tasksPosted by richard_damon on March 12, 2015 This sounds like the classic use of a mutex.
The minor nit is that it seems you are making public an implementation detail (the SD card and the EEPROM are on the same bus), but the actual mutex access can be put into the device driver APIs.
There could be some argument for having a second mutex outside the SPI bus mutex for just the SD card (or just the EEPROM) if the application layer needs to do multiple transactions that need to stay "atomic" (like reading a sector to update it). With just a single mutex, the task would need to lock out the EEPROM too during the update cycle.
Best practice to share same resources between tasksPosted by chaabanemalki on March 13, 2015
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|