FreeRTOS-Kernel

You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

History

Richard Barry 3788026636 RXv1 tests running before updating to RXv2.		11 years ago
..
Demo	RXv1 tests running before updating to RXv2.	11 years ago
License	Reorder the license text wording so the exception text is at the top rather than the bottom.	11 years ago
Source	Cast away a few unused return types to ensure lint/compilers don't generate warnings when the warning level is high.	11 years ago
readme.txt	Add readme files to the various FreeRTOS+ directories.	13 years ago

readme.txt

Unescape Escape

This file contains invisible Unicode characters that may be processed differently from what appears below. If your use case is intentional and legitimate, you can safely ignore this warning. Use the Escape button to reveal hidden characters.

Directories:

+ The FreeRTOS/Source directory contains the FreeRTOS source code, and contains
  its own readme file.

+ The FreeRTOS/Demo directory contains a demo application for every official
FreeRTOS port, and contains its own readme file.

+ See http://www.freertos.org/a00017.html for full details of the directory 
  structure and information on locating the files you require.

The easiest way to use FreeRTOS is to start with one of the pre-configured demo 
application projects (found in the FreeRTOS/Demo directory).  That way you will
have the correct FreeRTOS source files included, and the correct include paths
configured.  Once a demo application is building and executing you can remove
the demo application file, and start to add in your own application source
files.

See also -
http://www.freertos.org/FreeRTOS-quick-start-guide.html
http://www.freertos.org/FAQHelp.html

readme.txt Unescape Escape

readme.txt

Unescape Escape