c3e1df031e
* Pass top of stack to configINIT_TLS_BLOCK Picolibc wants to allocate the per-task TLS block within the stack segment, so it will need to modify the top of stack value. Pass the pxTopOfStack variable to make this explicit. Signed-off-by: Keith Packard <keithpac@amazon.com> * Move newlib-specific definitions to separate file This reduces the clutter in FreeRTOS.h caused by having newlib-specific macros present there. Signed-off-by: Keith Packard <keithpac@amazon.com> * Make TLS code depend only on configUSE_C_RUNTIME_TLS_SUPPORT Remove reference to configUSE_NEWLIB_REENTRANT as that only works when using newlib. configUSE_C_RUNTIME_TLS_SUPPORT is always set when configUSE_NEWLIB_REENTRANT is set, so using both was redundant in that case. Signed-off-by: Keith Packard <keithpac@amazon.com> * portable-ARC: Adapt ARC support to use generalized TLS support With generalized thread local storage (TLS) support present in the core, the two ARC ports need to have the changes to the TCB mirrored to them. Signed-off-by: Keith Packard <keithpac@amazon.com> * Add Thread Local Storage (TLS) support using Picolibc functions This patch provides definitions of the general TLS support macros in terms of the Picolibc TLS support functions. Picolibc is normally configured to use TLS internally for all variables that are intended to be task-local, so these changes are necessary for picolibc to work correctly with FreeRTOS. The picolibc helper functions rely on elements within the linker script to arrange the TLS data in memory and define some symbols. Applications wanting to use this mechanism will need changes in their linker script when migrating to picolibc. Signed-off-by: Keith Packard <keithpac@amazon.com> --------- Signed-off-by: Keith Packard <keithpac@amazon.com> Co-authored-by: Keith Packard <keithpac@amazon.com> Co-authored-by: Gaurav-Aggarwal-AWS <33462878+aggarg@users.noreply.github.com> |
2 years ago | |
|---|---|---|
| .. | ||
| CDK/T-HEAD_CK802 | 2 years ago | |
| Community-Supported-Ports@4273ca3211 | 3 years ago | |
| GCC | 2 years ago | |
| Partner-Supported-Ports@3f9c99a682 | 4 years ago | |
| XCC/Xtensa | 2 years ago | |
| KnownIssues.md | 3 years ago | |
| README.md | 3 years ago | |
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.