881305dcb8
* Demo: RISC-V_RV32_QEMU_VIRT_GCC: Increase the memory for RVA23 compilation * Demo: RISC-V_RV32_QEMU_VIRT_GCC: Update the regtest to include fpu registers * Demo: RISC-V_RV32_QEMU_VIRT_GCC: Fix small issues for 64-bit configs * Demo: RISC-V_RV32_QEMU_VIRT_GCC: Enable FPU unit * Demo: RISC-V_RV32_QEMU_VIRT_GCC: Enable compilation for RVA23 platforms * Demo: RISC-V_RV32_QEMU_VIRT_GCC: Fix copyright related CI issues * Demo: RISC-V_RV32_QEMU_VIRT_GCC: Update submodule manifest * Demo: RISC-V_RV32_QEMU_VIRT_GCC: Update a few typos and left overs * Demo: RISC-V_RV32_QEMU_VIRT_GCC: Apply @aggarg's sugestions * Update pointer to Freertos-Kernel |
||
|---|---|---|
| .. | ||
| Demo | ||
| License | ||
| Source@4d9cd906d3 | ||
| Test | ||
| links_to_doc_pages_for_the_demo_projects.url | ||
| README.md | ||
Directories:
-
The FreeRTOS/Source directory contains the FreeRTOS source code, and contains its own readme file.
-
The FreeRTOS/Demo directory contains a demo application for every official FreeRTOS port, and contains its own readme file.
-
The FreeRTOS/Test directory contains the tests performed on common code and the portable layer code, and contains its own readme file.
See FreeRTOS/SourceOrganization for full details of the directory structure and information on locating the files you require.
The easiest way to use FreeRTOS is to start with one of the pre-configured demo application projects (found in the FreeRTOS/Demo directory). 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 file, and start to add in your own application source files.