Google Git
Sign in
pigweed / third_party / github / FreeRTOS / FreeRTOS-Kernel / 77ad7174005e59321765b1a9ace3f20b5ab029f1
commit77ad7174005e59321765b1a9ace3f20b5ab029f1[log] [tgz]
authorReda Maher <52288047+RedaMaher@users.noreply.github.com>Tue Oct 06 03:06:51 2020 +0200
committerGitHub <noreply@github.com>Mon Oct 05 18:06:51 2020 -0700
treef508aaa6fbe31fe8bce2c302d8f8bf55b4223923
parentfccb97b10b79bce9cdd22a7d6902dd9ece0402ee [diff]
Posix: Fix no task switching issue if a task ended its main function (#184)

* Posix: Fix no task switching issue if a task ended

When the main function of a task exits, no task switching happened.
This is because all the remaining tasks are waiting on the condition
variable. The fix is to trigger a task switch and mark the exiting
task as "Dying" to be suspened and exited properly from the scheduler.

* Posix: Assert and stop if the Task function returned

* Posix: just assert if a task returned from its main function

Co-authored-by: alfred gedeon <alfred2g@hotmail.com>
1 file changed
tree: f508aaa6fbe31fe8bce2c302d8f8bf55b4223923
  1. .github/
  2. include/
  3. portable/
  4. CONTRIBUTING.md
  5. croutine.c
  6. event_groups.c
  7. GitHub-FreeRTOS-Kernel-Home.url
  8. History.txt
  9. lexicon.txt
  10. LICENSE.md
  11. list.c
  12. queue.c
  13. Quick_Start_Guide.url
  14. README.md
  15. SECURITY.md
  16. stream_buffer.c
  17. tasks.c
  18. timers.c
README.md

Getting started

This repository contains FreeRTOS kernel source/header files and kernel ports only. This repository is referenced as a submodule in FreeRTOS/FreeRTOS repository, which contains pre-configured demo application projects under FreeRTOS/Demo directory.

The easiest way to use FreeRTOS is to start with one of the pre-configured demo application projects. 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 files, and start to add in your own application source files. See the FreeRTOS Kernel Quick Start Guide for detailed instructions and other useful links.

Additionally, for FreeRTOS kernel feature information refer to the Developer Documentation, and API Reference.

Getting help

If you have any questions or need assistance troubleshooting your FreeRTOS project, we have an active community that can help on the FreeRTOS Community Support Forum.

Cloning this repository

To clone using HTTPS:

git clone https://github.com/FreeRTOS/FreeRTOS-Kernel.git

Using SSH:

git clone git@github.com:FreeRTOS/FreeRTOS-Kernel.git

Repository structure

  • The root of this repository contains the three files that are common to every port - list.c, queue.c and tasks.c. The kernel is contained within these three files. croutine.c implements the optional co-routine functionality - which is normally only used on very memory limited systems.

  • The ./portable directory contains the files that are specific to a particular microcontroller and/or compiler. See the readme file in the ./portable directory for more information.

  • The ./include directory contains the real time kernel header files.

Code Formatting

FreeRTOS files are formatted using the “uncrustify” tool. The configuration file used by uncrustify can be found in the FreeRTOS/FreeRTOS repository.

Spelling

lexicon.txt contains words that are not traditionally found in an English dictionary. It is used by the spellchecker to verify the various jargon, variable names, and other odd words used in the FreeRTOS code base. If your pull request fails to pass the spelling and you believe this is a mistake, then add the word to lexicon.txt. Note that only the FreeRTOS Kernel source files are checked for proper spelling, the portable section is ignored.