Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem TCP & FAT




Loading

FreeRTOS+IO Configuration Introduction Just l

Posted by lafleur on March 16, 2012
I'm look at the demo code to see if I want to implement a port for my projects using dsPIC and PIC32. In looking at the demo code for the LPC1769 board I see some data structure that do NOT seam to be defined in the demo code.. (did a full file search in the directory tree)..

UART_CFG_Type xUARTConfig;
UART_FIFO_CFG_Type xUARTFIFOConfig;

are they located elsewhere?? did I miss something?

thanks...

RE: FreeRTOS+IO Configuration Introduction Just l

Posted by Richard on March 16, 2012
That project is actually four projects that are linked together in the rather cumbersome way that Eclipse requires, so the file you are looking for is in one of the linked projects - in this case the CMSIS driver project. Take a look at \lpc17xx.cmsis.driver.library\Include\lpc17xx_uart.h.

Regards.

RE: FreeRTOS+IO Configuration Introduction Just l

Posted by lafleur on March 17, 2012
It appear that in the demo code base, in the FreeRTOS folder, where the files headers are marked at 7.1.0, that there are modules like queue.h, semphr.h, task.h and queue.c, that are "updated" from the main line 7.1.0 code base??

what other issues or changes might I find??

thanks



RE: FreeRTOS+IO Configuration Introduction Just l

Posted by Richard on March 17, 2012
You are correct, and maybe the version number should have been updated but that would have meant using a version number that never made it to be an official release. The source files are in between FreeRTOS releases. V7.1.0 was used for development, but the files updated to the SVN head revision from the main line code prior to putting the FreeRTOS+IO demo together.

Regards.

RE: FreeRTOS+IO Configuration Introduction Just l

Posted by lafleur on March 18, 2012
I notices that your I/O stack did not include a close??? why is this??

also, what are the license's cost for using the I/O and CLI stacks

thanks

RE: FreeRTOS+IO Configuration Introduction Just l

Posted by Richard on March 19, 2012
“I notices that your I/O stack did not include a close??? why is this??”


My thinking was that it would rarely be required, and so, to minimise code size (one of the FreeRTOS design goals) it would be omitted. To elaborate - in a multi user general purpose operating system IO devices need to be opened and closed all the time as different users make use of the devices for their own purposes. FreeRTOS is not a multi-user system, and generally, the devices that are opened during initialisation will remain open for the duration of the application - and even if different tasks require access to the same peripheral at different times they can all use a single handle that was opened just once.

I understand that this might not suite every user, and it is the intention to continue to develop the produce ad infinitum depending on user requests. The intention is to open a user voice account so people can vote on features they would like to see, so when I get around to that this can be one such option.

“also, what are the license's cost for using the I/O and CLI stacks”


These have been belatedly added to the FreeRTOS shop now http://shop.freertos.org/Add_on_components_for_FreeRTOS_s/1833.htm although I would suggest waiting until the other side of the ESC conference at the end of this month before purchasing the IO compnent.

Regards.


[ Back to the top ]    [ About FreeRTOS ]    [ Sitemap ]    [ ]




Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.

Latest News

FreeRTOS kernel V10 is available for immediate download. Now MIT licensed.


FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

IAR Partner

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers

STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

OpenRTOS and SafeRTOS