1e8d541ed4
The tracelyzer code was declaring a local stack variable of type `uint32_t` and passing it as output parameter to a function which expected `uint64_t` on a 64-bit platform. This resulted in 4 byte memory corruption. The problem was that the function signature uses `TraceUnsignedBaseType_t` type for the output parameter which gets defined to `uint32_t` on a 32-bit platform and to `uint64_t` on a 64-bit platform, while the local stack variable was declared as `uint32_t`. This commit changes the type of local stack variable to `TraceUnsignedBaseType_t` to match the function parameter type. Tracelyzer creates a task internally stack size of which is controlled using TRC_CFG_CTRL_TASK_STACK_SIZE. It was earlier defined to 1024. The POSIX port requires the stack size to be minimum PTHREAD_STACK_MIN. The commit updates the TRC_CFG_CTRL_TASK_STACK_SIZE to PTHREAD_STACK_MIN. The demo directory contained one extra trcConfig.h and trcKernelPortConfig.h. This commit deletes those files. Signed-off-by: Gaurav Aggarwal <aggarg@amazon.com> Signed-off-by: Gaurav Aggarwal <aggarg@amazon.com> |
||
|---|---|---|
| .. | ||
| Demo | ||
| License | ||
| Source@def7d2df2b | ||
| 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.