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


Hardware usage how is it possible?

Posted by Nobody/Anonymous on January 10, 2007

I have been reading the site and RTOS core.
Untill now i wasn´t able to find (for the PICs) any tip or comment on how to use the pheripherals like SPI, UART, PORTS, PP, ADCs.

How is it possible to interact with the peripherals when using FreeRTOS??

Thank you for the help

RE: Hardware usage how is it possible?

Posted by Nobody/Anonymous on January 10, 2007
Does the PIC port not have a uart driver as an example? I think they all do.

Look in the source code in the demo/[port]/serial directory (where [port] is the port you are interested in).

RE: Hardware usage how is it possible?

Posted by Westmoreland Engineering on January 10, 2007

FreeRTOS is a kernel - peripheral drivers are part of the ports (example code). Some of the example code is very simple - but it's meant to demonstrate the features of FreeRTOS. You can find UART drivers as mentioned above - but it's unlikely you'll find, for instance, a fully-functional full-duplex DMA driven UART for every port - that's up to you to develop or perhaps find the source code for that someplace else and adapt it for FreeRTOS. Most ports have a simple interrupt driven example for UART's - but it'll take some work if you want to use those in the real world - some ports are better than others as well.

John W.

RE: Hardware usage how is it possible?

Posted by Richard on January 10, 2007
Just to go a little further to what John has already stated.

[As I think I state in numerous places on the WEB site and in the code) The sample UART drivers provide an example of interaction between the kernel and an interrupt which is useful for users to copy. However the actual implementation of the driver is often deliberately inefficient, for example it might not use the DMA or even the buffers on the peripheral. This is because the provision of the driver is also for the purpose of testing the port. The more interrupts the peripheral can generate the higher the loading and statistical change of finding an error. If you have a 16 byte buffer and generate an interrupt every 16 characters then you are generating 16 times less interrupts than if you turn the buffering off.


[ 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