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


FreeRTOS + MPU practicality question

Posted by Tamir Michael on June 27, 2012

I've enabled FreeRTOS's support for a MPU (LPC1788). My application, however, needs to _move_ lots of data - log data, screen shots, etc. With a MPU in place, this becomes a difficult or at least - expensive in terms of computation power, as the only way to move data is via kernel provisions (queue...) and signals.
Is there a useful way to share data between tasks? I thought about programming the MPU on the fly so that one of the regions is setup as R/O to allow some access, but what do I do if I need to write (for example, if a task needs to write data to a TX buffer which is located outside of its regions reach...). Having a task per function can cause serious traffic congestion...
Any ideas?

RE: FreeRTOS + MPU practicality question

Posted by Tamir Michael on June 27, 2012
If these issues are not resolved, I am considering leaving the MPU enabled, but only for the kernel.
I would appreciate any input you might have.

RE: FreeRTOS + MPU practicality question

Posted by Richard on June 27, 2012
You can give more than one task access to the same RAM to share data between tasks. For example, if you set up the MPU of two tasks to have both read and write access to a certain area of RAM. Or, depending on the design, you could set up one task to have read only access and another task to have write only access to a region of RAM so one task can produce data and another consume it (without any other tasks being able to write over the data being consumed).

Does that help your design? Maybe you are doing that already?


RE: FreeRTOS + MPU practicality question

Posted by Tamir Michael on June 28, 2012
Thanks for your reply.
I have build a small prototype that allows a task to "R/O - share" its MPU memory (allocated using a LIFO policy but that's off the subject) upon sending a signal to a task that requires access to the memory. That should solve the issue of transferring large blocks of data, but also requires the approval of my colleagues...

[ 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