* Simple blinky demo working. Not tried full demo yet. * Get the full demo running. * Add Eclipse project to build the RISC-V_RV32_QEMU_VIRT_GCC gcc makefile. * Add regtest tasks to the RISC-V_RV32_QEMU_VIRT_GCC demo. * Update priority of the timer task. * Adjust timer frequency and optimisation level before committing prior to rearranging the Eclipse project. * Reorganise Eclipse project slightly. * Add note to the RISC-V-Qemu-virt_GCC readme file about the updated version in RISC-V_RV32_QEMU_VIRT_GCC. * Update headers in newly added source files so they pass the automated header check. * Update lexicon to pass automated spell check. Co-authored-by: none <> |
||
|---|---|---|
| .. | ||
| Demo | ||
| License | ||
| Source@c4f9e27c28 | ||
| 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.