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] [April 2006 Threads] Synchronization objectsPosted by Nobody/Anonymous on April 4, 2006 hello on 32bit cpu semaphore takes 100 bytes in ram! it very expansive. it would very good if freertos would have like window's Event and Semaphore objects.
RE: Synchronization objectsPosted by Richard on April 4, 2006 The semaphore uses exactly the same code as the queue mechanism - it is just a macro wrapper around the queue code. This is done to minimise the ROM usage, rather than the RAM.
While the RAM usage may seem high for a semaphore the data structures within that 100 bytes contains all the event management data in addition to the semaphore data. There are no extra event control blocks required, and event data structures are not required to be allocated separately as in some other RTOS's. This (hopefully) is more efficient when looking at the system as a whole, rather than individual components. At least this is the intention :-)
Regards.
RE: Synchronization objectsPosted by Jeff Smith on April 4, 2006 The preference seems questionable to me... I've always seen that ROM was much more plentiful than RAM inside the MCU families I'm using (8 and 16-bit Freescale).
But then, I've been impressed by the overall system, so Richard makes a good point.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|