mirror of
https://github.com/FreeRTOS/FreeRTOS-Kernel.git
synced 2025-04-19 21:11:57 -04:00
* Add RP2040 support (#341) * Add RP2040 support * remove spurious tab/spaces comments * add .cmake to ignored kernel checks * Apply suggestions from code review Co-authored-by: Paul Bartell <paul.bartell@gmail.com> * license and end of file newline fixes * Rename LICENSE.TXT to LICENSE.md Co-authored-by: Paul Bartell <paul.bartell@gmail.com> Co-authored-by: Gaurav-Aggarwal-AWS <33462878+aggarg@users.noreply.github.com> * RP2040 updates for SMP * whitepsace fix Co-authored-by: Gaurav-Aggarwal-AWS <33462878+aggarg@users.noreply.github.com> * whitespace fix Co-authored-by: Gaurav-Aggarwal-AWS <33462878+aggarg@users.noreply.github.com> Co-authored-by: Paul Bartell <paul.bartell@gmail.com> Co-authored-by: Gaurav-Aggarwal-AWS <33462878+aggarg@users.noreply.github.com>
1.4 KiB
1.4 KiB
Overview
This directory provides an SMP FreeRTOS-Kernel port that can be used with the Raspberry Pi Pico SDK. It supports:
- Simple CMake INTERFACE libraries, to provide the FreeRTOS-Kernel and also the individual allocator types, without copying code into the user's project.
- Running the FreeRTOS-Kernel and tasks on either core 0 or core 1, or both.
- Use of SDK synchronization primitives (such as mutexes, semaphores, queues from pico_sync) between FreeRTOS tasks and code executing on a non FreeRTOS core, or in IRQ handlers.
Note that whilst this SMP version can be run on just a single (either) core, it is probably more efficient to use the non SMP version in the main FreeRTOS-Kernel branch in that case.
Using this port
Copy FreeRTOS-Kernel-import.cmake into your project, and add:
import(FreeRTOS_Kernel_import.cmake)
below the usual import of pico_sdk_import.cmake
This will find the FreeRTOS kernel if it is a direct sub-module of your project, or if you provide the FREERTOS_KERNEL_PATH
variable in your environment or via -DFREERTOS_KERNEL_PATH=/path/to/FreeRTOS-Kernel
on the CMake command line.
Advanced Configuration
Some additional config
options are defined here which control some low level implementation details.
Known Limitations
- Tickless idle has not currently been tested, and is likely non-functional