Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Real time embedded FreeRTOS mailing list 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem TCP & FAT Training




Loading

Semaphore

Posted by Nobody/Anonymous on June 7, 2006
Hi!
I have some doubts on semahore use for lock a resource (EEPROM).
I try to define the semaphore, let's say in eeprom.c and initialize it:

static xSemaphoreHandle xSemaphoreEEPROM;

char eepromInit(void)
{
vSemaphoreCreateBinary( xSemaphoreEEPROM );
if( xSemaphoreEEPROM != NULL ) return 0;
return 1;
}

Then, can I have two files, each one with one different task that can test the semaphore xSemaphoreEEPROM before addressing the EEPROM, like:
...
if( xSemaphoreTake( xSemaphoreEEPROM, ( portTickType ) timeout ) )
{
/* Call function to write data on eeprom... */
xSemaphoreGive( xSemaphoreEEPROM );
}
...
This can lock the resource, or the last code must be included in eeprom.c like a driver:
char writeEEPROM (int addr, int n, char *data, int timeout)
{
if( xSemaphoreTake( xSemaphoreEEPROM, ( portTickType ) timeout ) )
{
/* Write data... */
xSemaphoreGive( xSemaphoreEEPROM );
}
}

Please give me some hint about this.

RE: Semaphore

Posted by Nobody/Anonymous on June 9, 2006
What you say seems to be correct. You are using the semaphore to ensure mutual exclusion of the eeprom resource.


RE: Semaphore

Posted by Nobody/Anonymous on June 9, 2006
I don't have experience in these kinf of OS's but there will eventually two task accessing the same function:

char writeEEPROM (int addr, int n, char *data, int timeout)
{
if( xSemaphoreTake( xSemaphoreEEPROM, ( portTickType ) timeout ) )
{
/* Write data... */
xSemaphoreGive( xSemaphoreEEPROM );
}
}

There is any problem when two tasks call the same function with a lock semaphore like the previous one?
Or there is a better way to do this?

RE: Semaphore

Posted by Nobody/Anonymous on June 9, 2006
Nope, this is exactly how semaphores should be used.


[ Back to the top ]    [ About FreeRTOS ]    [ Sitemap ]    [ ]




Copyright (C) 2004-2010 Richard Barry. Copyright (C) 2010-2016 Real Time Engineers Ltd.
Any and all data, files, source code, html content and documentation included in the FreeRTOSTM distribution or available on this site are the exclusive property of Real Time Engineers Ltd.. See the files license.txt (included in the distribution) and this copyright notice for more information. FreeRTOSTM and FreeRTOS.orgTM are trade marks of Real Time Engineers Ltd.

Latest News:

FreeRTOS V9.0.0 is now available for download.


Free TCP/IP and file system demos for the RTOS


Sponsored Links

⇓ Now With No Code Size Limit! ⇓
⇑ Free Download Without Registering ⇑


FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

Renesas Electronics Gold Alliance RTOS Partner.jpg

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers

Atmel RTOS partner supporting ARM Cortex-M3 and AVR32 microcontrollers

STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Xilinx Microblaze and Zynq partner

Silicon Labs low power RTOS partner

Altera RTOS partner for Nios II and Cortex-A9 SoC

Freescale Alliance RTOS Member supporting ARM and ColdFire microcontrollers

Infineon ARM Cortex-M microcontrollers

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

Cypress RTOS partner supporting ARM Cortex-M3

Fujitsu RTOS partner supporting ARM Cortex-M3 and FM3

Microsemi (previously Actel) RTOS partner supporting ARM Cortex-M3

Atollic Partner

IAR Partner

Keil ARM Partner

Embedded Artists