* Demo/CORTEX_LM3S6965_GCC_QEMU: Trim trailing spaces & lines * Demo/CORTEX_LM3S6965_GCC_QEMU: Fix Eclipse build 1/2 (examples) It was trying to build the examples, which pulled in symbols such as `_write` that are not implemented. * Demo/CORTEX_LM3S6965_GCC_QEMU: Fix Eclipse build 1/2 (discard .ARM.exidx) Somewhere along the line now there is the .ARM.exidx section in the files, we don't use exceptions so can just discard it. * Demo/CORTEX_LM3S6965_GCC_QEMU: Add CMake * Debug/CORTEX_LM3S6965_GCC_QEMU: Fix Qemu startup It was tripping on port.c /* Check that the maximum system call priority is nonzero after * accounting for the number of priority bits supported by the * hardware. A priority of 0 is invalid because setting the BASEPRI * register to 0 unmasks all interrupts, and interrupts with priority 0 * cannot be masked using BASEPRI. * See https://www.FreeRTOS.org/RTOS-Cortex-M3-M4.html */ configASSERT( ucMaxSysCallPriority ); Inspecting the value ucMaxPriorityValue gave 0xE0, and setting it to 0xE0 complains about overflow in FreeRTOS/Demo/CORTEX_LM3S6965_GCC_QEMU/LocalDemoFiles/IntQueueTimer.c:57 /* Shift left 5 as only the top 3 bits are implemented. */ IntPrioritySet( INT_TIMER2A, configMAX_SYSCALL_INTERRUPT_PRIORITY + ( 1 << 5 ) ); * Add qemu options to run in headless mode Signed-off-by: Gaurav Aggarwal <aggarg@amazon.com> --------- Signed-off-by: Gaurav Aggarwal <aggarg@amazon.com> Co-authored-by: Gaurav-Aggarwal-AWS <33462878+aggarg@users.noreply.github.com> Co-authored-by: Gaurav Aggarwal <aggarg@amazon.com> |
||
---|---|---|
.. | ||
Demo | ||
License | ||
Source@0030d609a4 | ||
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.