* Adding in ability to support a library for freertos_config and a custom freertos_kernel_port (#558) * Using single name definition for libraries everywhere. (#558) * Supporting backwards compatibility with FREERTOS_CONFIG_FILE_DIRECTORY (#571) * Removing compiler warnings for GNU and Clang. (#571) * Added in documentation on how to consume from a main project. Added default PORT selection for native POSIX and MINGW platforms. * Only adding freertos_config if it exists. Removing auto generation of it from a FREERTOS_CONFIG_FILE_DIRECTORY. * Fixing clang and gnu compiler warnings. * Adding in project information and how to compile for GNU/clang * Fixing compiler issue with unused variable - no need to declare variable. * Adding in compile warnings for linux builds that kernel is okay with using. * Fixing more extra-semi-stmt clang warnings. * Moving definition of hooks into header files if features are enabled. * Fixing formatting with uncrustify. * Fixing merge conflicts with main merge. * Fixing compiler errors due to merge issues and formatting. * Fixing Line feeds. * Adding 'portNORETURN' into portmacros.h. Other Updates based on PR request * Further clean-up of clang and clang-tidy issues. * Removing compiler specific pragmas from common c files. * Fixing missing lexicon entry and uncrustify formatting changes. * Resolving merge issue multiple defnitions of proto for prvIdleTask * Fixing formatting issues that are not covered by uncrustify. Use clang-tidy instead if you want this level of control. * More uncrustify formatting issues. * Fixing extra bracket in #if statement. --------- Co-authored-by: Gaurav-Aggarwal-AWS <33462878+aggarg@users.noreply.github.com> |
||
---|---|---|
.. | ||
CDK/T-HEAD_CK802 | ||
Community-Supported-Ports@4273ca3211 | ||
GCC | ||
Partner-Supported-Ports@3f9c99a682 | ||
XCC/Xtensa | ||
KnownIssues.md | ||
README.md |
FreeRTOS Third Party Ports
FreeRTOS third party ports can be supported by the FreeRTOS team, a FreeRTOS partner or FreeRTOS community members. Depending on who supports it, the support provided will differ as follows:
FreeRTOS Team Supported Third Party FreeRTOS Ports
Location: https://github.com/FreeRTOS/FreeRTOS-Kernel/tree/main/portable/ThirdParty
These third party FreeRTOS ports are supported by the FreeRTOS team. For a FreeRTOS team supported third party FreeRTOS port:
- The code has been reviewed by the FreeRTOS team.
- FreeRTOS team has access to the hardware and the test results have been verified by the FreeRTOS team.
- Customer queries as well as bugs are addressed by the FreeRTOS team.
- The code can be included in Long Term Support (LTS) releases.
A new FreeRTOS port cannot be directly contributed to this location. Instead, the FreeRTOS team will decide to take ownership of a partner supported or a community supported FreeRTOS port based on the community interest.
Partner Supported FreeRTOS Ports
Location: https://github.com/FreeRTOS/FreeRTOS-Kernel-Partner-Supported-Ports/tree/main
These FreeRTOS ports are supported by a FreeRTOS partner. For a partner supported FreeRTOS port:
- The code has not been reviewed by the FreeRTOS team.
- FreeRTOS team has not verified the tests results but tests exist and are reported to be successful by the partner.
- Customer queries as well as bugs are addressed by the partner.
A new FreeRTOS port can be directly contributed by a partner. The process to contribute a FreeRTOS port is documented here.
Community Supported FreeRTOS Ports
Location: https://github.com/FreeRTOS/FreeRTOS-Kernel-Community-Supported-Ports/tree/main
These FreeRTOS ports are supported by the FreeRTOS community members. For a community supported FreeRTOS port:
- The code has not been reviewed by the FreeRTOS team.
- Tests may or may not exist for the FreeRTOS port.
- Customer queries as well as bugs are addressed by the community.
A new FreeRTOS port can be directly contributed by anyone. The process to contribute a FreeRTOS port is documented here.