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

SAM4 ASF freeRTOS peripheral control vs PDC vs standard driver

Posted by cpasset3 on May 22, 2014

Hi,

I am developing a firmware for a product which have a SAM4 inside (L or N family, not decided yet). We are going with FreeRTOS as OS. I am having some trouble using the freeRTOSperipheralcontrol on the SAM4N (and it is not implemented for the SAM4L).

In our application only one task will be able to access a given peripheral (SPI/TWI and UART), for this case do we need to use the ASF freeRTOS_peripheral control or can we go only with the standard driver (on which we can add the PDC feature if we want to loose less CPU time ?)

Furthermore if we want some access control (in cause of two tasks need to send data to the task control the peripheral), instead of using the ASF freeRTOSperipheralcontrol could we just use a mutex which will be taken when the task will use the peripheral and release afterward ?

Thank you,

Charles


SAM4 ASF freeRTOS peripheral control vs PDC vs standard driver

Posted by rtel on May 22, 2014

There is absolutely nothing to prevent you using the standard ASF drivers, as long you are are aware that they are not written for use in a multi tasking environment so use them appropriately, with things like mutexes as you suggest. The FreeRTOS Peripheral Control drivers take care of that for you.

Also some of the older ASF drivers for the older parts also used a lot of polling, which is extremely inefficient, although a lot of the newer ASF drivers do allow more event driven use. The FreeRTOS Peripheral Control drivers are written to be as efficient as they can eb from the outset, but do have a dependency on the PDC being available.

Regards.


[ 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