Skip to content

Commit 7d7a63e

Browse files
authored
Merge pull request #4233 from benmcmorran/patch-2
Add build flags to improve RTOS view
2 parents c69ff8b + 8b01075 commit 7d7a63e

File tree

1 file changed

+43
-15
lines changed

1 file changed

+43
-15
lines changed

docs/embedded/rtos-view.md

Lines changed: 43 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -24,24 +24,29 @@ The RTOS Object View allows users to view various components of an RTOS while de
2424

2525
## Supported RTOSes and their supported object types
2626

27-
- ThreadX
28-
- All of the types listed in **Available object types**
29-
- FreeRTOS
27+
- Azure RTOS (ThreadX)
28+
- Block pools
29+
- Byte pools
30+
- Event flags
31+
- Mutexes
32+
- Queues
33+
- Semaphores
3034
- Threads
35+
- Timers
36+
- FreeRTOS
3137
- Queues
38+
- Threads
3239
- Zephyr
33-
- All of the types listed in **Available object types**
34-
35-
### Available object types
36-
37-
- Block Pools
38-
- Byte Pools
39-
- Event Flag Groups
40-
- Mutexes
41-
- Queues
42-
- Semaphores
43-
- Threads
44-
- Timers
40+
- Mailboxes
41+
- Memory slabs
42+
- Message queues
43+
- Mutexes
44+
- Pipes
45+
- Queues
46+
- Semaphores
47+
- Stacks
48+
- Threads
49+
- Timers
4550

4651
## Usage
4752

@@ -51,3 +56,26 @@ Use the RTOS Object View to:
5156
- Access thread variables or various objects in the Watch view.
5257

5358
Use the arrow keys to select objects within the view. Use the **Enter** key to navigate to the linked content.
59+
60+
## Configuring an embedded application for the RTOS view
61+
62+
The RTOS Object View will attempt to automatically display information, but setting certain build flags can allow the RTOS Object View to display additional details. The build flags are specific to the RTOS being used. The exact mechanism used to set these flags varies depending on the build system used by the project. Consult your RTOS and build system documentation for more details.
63+
64+
### Azure RTOS (ThreadX)
65+
66+
All features should work by default.
67+
68+
### FreeRTOS
69+
70+
- Thread base priority is only available if `configUSE_MUTEXES` is enabled.
71+
- Thread run count is only available if `configGENERATE_RUN_TIME_STATS` is enabled.
72+
- The end address of a thread's stack space is only available if `portSTACK_GROWTH` or `configRECORD_STACK_HIGH_ADDRESS` are enabled.
73+
- The thread list will be retrieved faster if `configMAX_PRIORITIES` is set to the lowest possible value that still satisfies the application's requirements.
74+
75+
### Zephyr
76+
77+
- All thread information is only available if `CONFIG_DEBUG_THREAD_INFO` is enabled.
78+
- Thread stack usage is only availabe if `CONFIG_INIT_STACKS` and `CONFIG_THREAD_STACK_INFO` are enabled.
79+
- For all object types other than threads, information is only available if `CONFIG_TRACING` and `CONFIG_TRACING_OBJECT_TRACKING` are enabled.
80+
- The maximum usage of a memory slab is only available if `CONFIG_MEM_SLAB_TRACE_MAX_UTILIZATION` is enabled.
81+
- The list of threads waiting on an object is only available if `CONFIG_WAITQ_SCALABLE` is disabled.

0 commit comments

Comments
 (0)