You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

History

Aniruddha Kanhere 2fcb0f48b1 Fix small bugs in Kernel (#998 ) * Fix small bugs * Cast sizeof to BaseType_t * Test removing assert to fix UT * Revert change to tasks.c Since configIDLE_TASK_NAME must be defined as a string according to the documentation, the macro will always be NULL terminated. Which means that the check `if( cIdleName[ xIdleTaskNameIndex ] == ( char ) 0x00 )` will catch the end of string. * Update coverity config; Add coverity version; Update pvPortMalloc declaration to match the definitions. * Add port files to sed command * Remove warnings about unused parameters in port code --------- Co-authored-by: Rahul Kar <118818625+kar-rahul-aws@users.noreply.github.com>		12 months ago
..
CDK/T-HEAD_CK802	Add trace hook macro for most ports (#794 )	1 year ago
Community-Supported-Ports@f051e9bff8	Update partner and community supported port submodule pointer (#919 )	1 year ago
GCC	Fix small bugs in Kernel (#998 )	12 months ago
Partner-Supported-Ports@da0185fbf1	Update partner and community supported port submodule pointer (#919 )	1 year ago
XCC/Xtensa	use configSTACK_DEPTH_TYPE consequently (updated for 11.0.x) (#942 )	1 year ago
xClang/XCOREAI	Fix portSET_INTERRUPT_MASK_FROM_ISR definition for atomic operation (#940 )	1 year ago
KnownIssues.md	Add a Known Issues file in the Third Party folder (#434 )	3 years ago
README.md	Update portable/ThirdParty/README.md (#474 )	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.