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


Which features of the API are supported?

Posted by George Silvis on May 11, 2009

If a feature (eg configUSE_MUTEXES) is not defined in the FreeRTOSconfig.h of a particular port, does this mean that that feature is not supported by that port of the RTOS?

I understand that you can enable/disable features from the config.h. But if an API feature defined in the book is not mentioned in the config.h, does this mean that it is not supported in this particular port.

I'm trying to use a mutex with the LPC2000 port and having some difficulty. I want to know if this is my problem or if its a feature not available with this port.


RE: Which features of the API are supported?

Posted by Richard on May 11, 2009
All features are supported in all ports - other than stack checking which does not work on architectures with segmented memory (PIC18 and x86). Some FreeRTOSConfig.h files do not contain all the available macros simply because they were written prior to the macros being introduced into later versions of FreeRTOS.

What is the problem you are experiencing?


RE: Which features of the API are supported?

Posted by George Silvis on May 11, 2009
Thanks. I'll review FreeRTOS.h for defaulted features. The documentation book does mention that interrupt nesting comes only with some ports that are for architectures that permit the feature. I'll take a closer look for the LPC2000.

My application is on the LPC2148, using the IAR compiler.

The problem I'm having is with my first experiment with a mutex. I have a I2C service that needs to be accessed by 2 tasks. It seems straight forward to have them take turns by using a mutex: All access is always bracketed by I2C_Start() and I2C_Stop(), so I added the semaphoreTake to the Start and the Give to the End. It works a short while then the debugger finds the code hung in the idle state. The tasks have different priorities. If you have any suggestions on how to debug, gratefully received!


RE: Which features of the API are supported?

Posted by George Silvis on May 11, 2009
Never mind. My problem with the mutex wrapped around the I2C service is self inflicted.


[ 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