github-forks
/
FreeRTOS-Kernel
mirror of https://github.com/FreeRTOS/FreeRTOS-Kernel.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
1,423 Commits
2 Branches
99 Tags
129 MiB
C 90.4%
Assembly 9%
CMake 0.5%
 
 
 
Go to file
Richard Barry 8b0ccf1444 New MicroBlaze port: Added a FreeRTOS exception handler, and installed it in each position in the exception table. The handler itself does not do much yet.
Demo New MicroBlaze port: Added a FreeRTOS exception handler, and installed it in each position in the exception table. The handler itself does not do much yet.
License Correct unintended duplication and slight wording change.
Source Change some (xTIMER *) references in the documentation for the timer module to be instead xTimerHandle references (the two are in effect equivalent, but xTIMER is private to the timers source file).
TraceCon First version under SVN is V4.0.1
readme.txt First version under SVN is V4.0.1

readme.txt
Unescape Escape

This file contains invisible Unicode characters!

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.

The download includes the kernel source code, and a demo application for EVERY

RTOS port.  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 start start with one of the demo application 

projects.  Once this is running the project can be modified to include your own

source files.  This way the correct files and compiler options will be 

automatically included in your application.



+ The Source directory contains the real time kernel source files for every 

port.  The kernel itself is only 3 files.



+ The Demo directory contains the demo application source files for every 

port.



+ The TraceCon directory contains the trace visualisation exe file.



See the readme files in the respective directories for further information.