vTaskGetRunTimeStats() for CPU usage in FreeRTOS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a buffer for runtime stats.

FreeRTOS

char statsBuffer[[1]];

Drag options to blanks, or click blank then click option'

A512

B1024

C256

D128

Attempts:

3 left

💡 Hint

Common Mistakes

Using too small a buffer causing string truncation.

Using an uninitialized buffer.

The buffer size should be large enough to hold the runtime stats string. 1024 bytes is a common safe size.

2fill in blank

medium

Complete the code to call vTaskGetRunTimeStats with the buffer.

FreeRTOS

vTaskGetRunTimeStats([1]);

Drag options to blanks, or click blank then click option'

AstatsBuffer

B&statsBuffer

CNULL

Dbuffer

Attempts:

3 left

💡 Hint

Common Mistakes

Passing &statsBuffer which is a pointer to the whole array, not a char pointer.

Passing NULL which causes no output.

The function expects a pointer to a char array, so passing the array name (statsBuffer) is correct.

3fill in blank

hard

Fix the error in printing the runtime stats string.

FreeRTOS

printf("CPU Usage:\n%s", [1]);

Drag options to blanks, or click blank then click option'

A*statsBuffer

B&statsBuffer

CstatsBuffer

DstatsBuffer[0]

Attempts:

3 left

💡 Hint

Common Mistakes

Using &statsBuffer which is a pointer to the array, not a char pointer.

Using *statsBuffer which is a char, not a pointer.

printf expects a char pointer for %s, so passing statsBuffer (the array name) is correct.

4fill in blank

hard

Fill both blanks to declare and initialize the buffer, then get runtime stats.

FreeRTOS

char [1][512];
vTaskGetRunTimeStats([2]);

Drag options to blanks, or click blank then click option'

AstatsBuffer

Bbuffer

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for declaration and function call.

Passing an uninitialized buffer.

The buffer is declared as statsBuffer and passed to vTaskGetRunTimeStats.

5fill in blank

hard

Fill all three blanks to declare buffer, get stats, and print them.

FreeRTOS

char [1][1024];
vTaskGetRunTimeStats([2]);
printf("Task CPU Usage:\n%s", [3]);

Drag options to blanks, or click blank then click option'

AruntimeStats

DstatsBuffer

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for buffer declaration and usage.

Passing NULL or wrong pointer to vTaskGetRunTimeStats.

The buffer is named statsBuffer, passed to vTaskGetRunTimeStats, and printed.

Practice

1. What is the primary purpose of the vTaskGetRunTimeStats() function in FreeRTOS?

easy

A. To suspend all running tasks temporarily

B. To create a new task with specific priority

C. To delete a task from the scheduler

D. To display the CPU usage time of each task

Solution

1. Step 1: Understand the function's role

   vTaskGetRunTimeStats() is designed to collect and display CPU usage statistics for each task in FreeRTOS.

2. Step 2: Compare options with function purpose

   Options A, B, and C relate to task management but not CPU usage reporting, which is the key role of vTaskGetRunTimeStats().

3. Final Answer:

   To display the CPU usage time of each task -> Option D

4. Quick Check:

   Function purpose = CPU usage display [OK]

Hint: Remember: vTaskGetRunTimeStats shows CPU time per task [OK]

Common Mistakes:

• Confusing it with task creation or deletion functions
• Thinking it suspends tasks instead of reporting stats
• Assuming it modifies task priorities

2. Which of the following is the correct way to call vTaskGetRunTimeStats() to store the stats in a buffer named buffer?

easy

A. vTaskGetRunTimeStats(buffer);

B. vTaskGetRunTimeStats(&buffer);

C. vTaskGetRunTimeStats(buffer[]);

D. vTaskGetRunTimeStats(*buffer);

Solution

1. Step 1: Check function parameter type

   vTaskGetRunTimeStats() expects a pointer to a char array (string buffer), so passing the buffer name directly is correct.

2. Step 2: Analyze each option's syntax

   vTaskGetRunTimeStats(buffer); passes the buffer correctly. vTaskGetRunTimeStats(&buffer); passes address of buffer pointer (wrong). vTaskGetRunTimeStats(buffer[]); uses invalid syntax. vTaskGetRunTimeStats(*buffer); dereferences buffer incorrectly.

3. Final Answer:

   vTaskGetRunTimeStats(buffer); -> Option A

4. Quick Check:

   Pass buffer name directly [OK]

Hint: Pass buffer name directly, no & or * needed [OK]

Common Mistakes:

• Using &buffer which is wrong for arrays
• Adding [] inside function call
• Dereferencing buffer pointer incorrectly

3. Given the following code snippet, what will be the output stored in statsBuffer?

char statsBuffer[100];
vTaskGetRunTimeStats(statsBuffer);
printf("%s", statsBuffer);

Assuming two tasks "TaskA" and "TaskB" run and TaskA used 70% CPU, TaskB used 30%.

medium

A. TaskA 7
TaskB 3

B. TaskA 70%
TaskB 30%

C. TaskA 7000
TaskB 3000

D. TaskA 700
TaskB 300

Solution

1. Step 1: Understand output format of vTaskGetRunTimeStats()

   The function outputs CPU usage as run time counter ticks, not percentages. If TaskA used 70% CPU, it might show 7000 ticks and TaskB 3000 ticks (assuming 10000 total ticks).

2. Step 2: Match options with expected output

   TaskA 7000 TaskB 3000 shows usage in ticks (7000 and 3000), matching expected output. Options B, C, and D show percentages or smaller numbers, which are not the direct output format.

3. Final Answer:

   TaskA 7000 TaskB 3000 -> Option C

4. Quick Check:

   Output shows ticks, not percentages [OK]

Hint: Output shows ticks, not percent values [OK]

Common Mistakes:

• Assuming output shows percentages directly
• Confusing ticks with smaller numbers
• Expecting formatted percentages in output

4. You called vTaskGetRunTimeStats(statsBuffer); but the output is empty. What is the most likely cause?

medium

A. The function requires a NULL pointer as argument

B. Run time stats collection is not enabled in FreeRTOSConfig.h

C. The buffer size is too large

D. The tasks have zero priority

Solution

1. Step 1: Identify prerequisites for run time stats

   Run time stats must be enabled in FreeRTOSConfig.h (configGENERATE_RUN_TIME_STATS set to 1) for vTaskGetRunTimeStats() to work.

2. Step 2: Analyze other options

   Buffer size being too large does not cause empty output. Passing NULL is invalid. Task priority does not affect stats collection directly.

3. Final Answer:

   Run time stats collection is not enabled in FreeRTOSConfig.h -> Option B

4. Quick Check:

   Enable run time stats in config [OK]

Hint: Check configGENERATE_RUN_TIME_STATS is enabled [OK]

Common Mistakes:

• Assuming buffer size too large causes empty output
• Passing NULL pointer mistakenly
• Thinking task priority disables stats

5. You want to monitor CPU usage of tasks over time using vTaskGetRunTimeStats(). Which approach correctly ensures accurate and meaningful stats?

hard

A. Enable run time stats, provide a large buffer, call periodically, and reset counters between calls

B. Call vTaskGetRunTimeStats() once at startup with a small buffer

C. Disable run time stats and manually count task switches

D. Call vTaskGetRunTimeStats() inside each task to get its own CPU usage

Solution

1. Step 1: Understand requirements for accurate CPU stats

   Run time stats must be enabled, buffer must be large enough to hold all task info, and stats should be collected periodically to track changes over time.

2. Step 2: Evaluate each option

   Enable run time stats, provide a large buffer, call periodically, and reset counters between calls describes the correct approach including resetting counters to avoid cumulative overflow. Call vTaskGetRunTimeStats() once at startup with a small buffer is insufficient (only once, small buffer). Disable run time stats and manually count task switches disables stats, losing automation. Call vTaskGetRunTimeStats() inside each task to get its own CPU usage is incorrect because stats are global, not per task.

3. Final Answer:

   Enable run time stats, provide a large buffer, call periodically, and reset counters between calls -> Option A

4. Quick Check:

   Enable + buffer + periodic calls + reset = accurate stats [OK]

Hint: Enable stats, use big buffer, call regularly, reset counters [OK]

Common Mistakes:

• Calling once only at startup
• Disabling run time stats
• Calling inside each task expecting per-task stats