|
|
|
 |
How can I enable Context-ID trace for FreeRTOS on ARM?
|
| |
| Ref: 0561 |
|
Please refer to ~~/demo/arm/kernel/freertos/readme.txt and ~~/demo/arm64/kernel/freertos/readme.txt
|
|
|
|
|
TASK.TaskList is flickering while target is running.
|
| |
| Ref: 0437 |
|
Unfortunately, FreeRTOS does not proved a single list of all generated tasks.
Instead, it manages several lists, depending on the task state. The tasks
are rearranged and re-listed when they switch the task state.
If the task list is displayed, while the target is running (aka emulation
access or dual-port access), the debugger reads the task lists sequentially.
It can easily happen, that the lists are not consistent over this time period,
causing the debugger to read broken task lists. This results in a temporary
wrong display with a changing task list.
If the target is halted within a task, the lists are consistent and the
task list display is correct.
|
|
|
|
|
Why does TASK.STacK not show a complete stack coverage?
|
| |
| Ref: 0424 |
|
Unfortunately, FreeRTOS does not save the stack size of a task. Therefore the debugger doesn't know the end of the stack and cannot calculate the stack coverage.
If all tasks use the same stack size, you can specify the stack size in bytes as second parameter to the TASK.CONFIG command. E.g. for ARM based systems with each task having a stack of 1024 bytes:
TASK.CONFIG ~~/demo/arm/kernel/freertos/freertos.t32 0 0x400
See also rtos_freertos.pdf, chapter "Manual Configuration".
|
