len0rd/FreeRTOS-Kernel
1
0
Fork 0
mirror of https://github.com/FreeRTOS/FreeRTOS-Kernel.git synced 2025-04-19 21:11:57 -04:00
Code Issues Packages Projects Releases Wiki Activity
Mirror/fork of freertos kernel
1759 commits 2 branches 99 tags 168 MiB
C 90.4%
Assembly 9%
CMake 0.5%
Find a file
Richard Barry 4e7b460eaf Replace the CLZ function with a CLZ intrinsic in the Cortex-R4 port layer. 
Add EDS support in the PIC24 port layer.
Remove unnecessary EHB instructions from PIC32 port.
In the PIC32 port assembly code, replace the &= code with a single ins instruction.
2013-01-23 16:06:45 +00:00
FreeRTOS Replace the CLZ function with a CLZ intrinsic in the Cortex-R4 port layer. 2013-01-23 16:06:45 +00:00
FreeRTOS-Plus Allow mutex type semaphores to be given from an interrupt (not a normal thing to do - use a binary semaphore!). 2012-09-05 14:02:16 +00:00
readme.txt Add readme files to the various FreeRTOS+ directories. 2012-08-11 22:57:53 +00:00

readme.txt 

Directories:

+ FreeRTOS/source contains the FreeRTOS real time kernel source code.

+ FreeRTOS/demo contains a pre-configured demo project for every official 
  FreeRTOS port.
  
+ FreeRTOS-Plus contains additional FreeRTOS components and third party 
  complementary products.  THESE ARE LICENSED SEPARATELY FROM FreeRTOS although
  all contain open source options.  See the license files in each respective
  directory for information.
  
+ FreeRTOS-Plus/Demo_Projects_Using_FreeRTOS_Simulator contains pre-configured
  demo projects for the FreeRTOS-Plus components.  The demo projects run in
  a Windows environment using the FreeRTOS windows simulator.  These are 
  documented on the FreeRTOS web site http://www.FreeRTOS.org/plus

+ See http://www.freertos.org/a00017.html for full details of the directory 
  structure and information on locating the files you require.

Further readme files are contains in sub-directories as appropriate.
  
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