configASSERT() for development debugging in FreeRTOS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What happens when configASSERT fails in FreeRTOS?

Consider this snippet using configASSERT in FreeRTOS:

void vTaskFunction(void *pvParameters) {
    int x = 0;
    configASSERT(x != 0);
    // Task code
}

What is the expected behavior when this task runs?

FreeRTOS

void vTaskFunction(void *pvParameters) {
    int x = 0;
    configASSERT(x != 0);
    // Task code
}

A The assertion is ignored and a warning message is printed to the console.

B The system automatically restarts the task without any warning.

C The system halts or enters an infinite loop to indicate the assertion failure.

D The task continues running normally without any interruption.

💡 Hint

Think about what an assert is supposed to do when a condition is false during development.

configASSERT is designed to catch programming errors during development by halting the system or entering a safe infinite loop when the condition is false. This helps developers notice and fix bugs early.

🧠 Conceptual

intermediate

Why use configASSERT() only in development builds?

Why is it recommended to enable configASSERT() only during development and disable it in production?

A Because configASSERT() can halt the system, which is undesirable in production environments.

B Because configASSERT() improves system performance in production.

C Because configASSERT() automatically fixes bugs in production code.

D Because configASSERT() disables all interrupts permanently.

💡 Hint

Think about what happens when an assertion fails and why that might be a problem in a live system.

Assertions are meant to catch bugs early by stopping the system. In production, stopping the system abruptly can cause failures or data loss, so assertions are usually disabled.

❓ Predict Output

advanced

What is the output of this configASSERT macro usage?

Given the following configASSERT definition and code snippet:

#define configASSERT(x) if((x) == 0) { taskDISABLE_INTERRUPTS(); for(;;); }

void test() {
    int a = 5;
    configASSERT(a > 10);
    printf("Passed\n");
}

What will be printed when test() is called?

FreeRTOS

#define configASSERT(x) if((x) == 0) { taskDISABLE_INTERRUPTS(); for(;;); }

void test() {
    int a = 5;
    configASSERT(a > 10);
    printf("Passed\n");
}

A Passed

B Nothing is printed; the system enters an infinite loop.

C Compilation error due to missing semicolon.

D Runtime error: division by zero.

💡 Hint

Check the condition inside configASSERT and what happens if it is false.

Since a=5 and the condition a>10 is false, configASSERT triggers the infinite loop after disabling interrupts, so printf is never reached.

🔧 Debug

advanced

Identify the error in this configASSERT usage

What is wrong with this configASSERT usage?

#define configASSERT(x) if(x == 0) { taskDISABLE_INTERRUPTS(); for(;;); }

void check(int val) {
    configASSERT(val > 0);
    printf("Value is %d\n", val);
}

FreeRTOS

#define configASSERT(x) if(x == 0) { taskDISABLE_INTERRUPTS(); for(;;); }

void check(int val) {
    configASSERT(val > 0);
    printf("Value is %d\n", val);
}

A The macro lacks parentheses around the condition, causing incorrect evaluation.

B The macro will cause a syntax error due to missing braces.

C The macro disables interrupts but does not halt the system.

D The macro will always print the value regardless of the assertion.

💡 Hint

Consider operator precedence and how macros evaluate expressions.

Without parentheses around x in the macro, expressions like val > 0 may not evaluate correctly, leading to unexpected behavior.

🚀 Application

expert

How to implement a custom configASSERT handler for debugging?

You want to customize configASSERT to log the file name and line number where the assertion failed before halting. Which of the following implementations correctly achieves this?

FreeRTOS

#define configASSERT(x) // your implementation here

A #define configASSERT(x) if(x) { printf("Assertion failed at %s:%d\n", __FILE__, __LINE__); taskDISABLE_INTERRUPTS(); }

B #define configASSERT(x) if(!(x)) { taskDISABLE_INTERRUPTS(); for(;;); printf("Assertion failed\n"); }

C #define configASSERT(x) if(x == 0) { for(;;); printf("Error at line %d\n", __LINE__); }

D #define configASSERT(x) if((x) == 0) { printf("Assertion failed at %s:%d\n", __FILE__, __LINE__); taskDISABLE_INTERRUPTS(); for(;;); }

💡 Hint

Remember that code after an infinite loop will never run.

Option D prints the failure message before disabling interrupts and entering an infinite loop, ensuring the message is logged before halting.

Practice

1. What is the main purpose of configASSERT() in FreeRTOS development?

easy

A. To stop the program when a condition is false, helping catch bugs early

B. To speed up the program execution by optimizing code

C. To automatically fix errors in the code during runtime

D. To log messages without affecting program flow

Solution

1. Step 1: Understand the role of configASSERT()

   configASSERT() is used to check conditions during development and halt execution if the condition is false.

2. Step 2: Compare options with this role

   Only To stop the program when a condition is false, helping catch bugs early describes stopping the program on false conditions to catch bugs early, which matches configASSERT()'s purpose.

3. Final Answer:

   To stop the program when a condition is false, helping catch bugs early -> Option A

4. Quick Check:

   configASSERT() stops program on false condition = D [OK]

Hint: Remember: configASSERT() halts on false condition to find bugs fast [OK]

Common Mistakes:

• Thinking configASSERT() speeds up code
• Believing it fixes errors automatically
• Confusing it with logging functions

2. Which of the following is the correct syntax to use configASSERT() to check if a pointer ptr is not NULL?

easy

A. configASSERT(ptr);

B. configASSERT(ptr == NULL);

C. configASSERT(ptr = NULL);

D. configASSERT(ptr != NULL);

Solution

1. Step 1: Understand the condition to check pointer validity

   We want to assert that the pointer is NOT NULL, so the condition should be true when ptr is valid.

2. Step 2: Analyze each option

   configASSERT(ptr != NULL); checks ptr != NULL, which is correct. configASSERT(ptr == NULL); checks ptr == NULL (wrong), C uses assignment (=) which is a syntax error, and D checks ptr as a boolean but is less explicit.

3. Final Answer:

   configASSERT(ptr != NULL); -> Option D

4. Quick Check:

   Check pointer not NULL with ptr != NULL [OK]

Hint: Use != NULL to assert pointer is valid, not == NULL [OK]

Common Mistakes:

• Using assignment (=) instead of comparison (== or !=)
• Checking for NULL instead of not NULL
• Relying on implicit pointer truthiness

3. Consider this FreeRTOS code snippet:

int x = 5;
configASSERT(x > 10);
printf("Reached here\n");

What will be the output when this code runs in a debug build?

medium

A. Compilation error due to configASSERT

B. Reached here

C. Program halts at configASSERT, no output

D. Undefined behavior, may crash later

Solution

1. Step 1: Evaluate the condition inside configASSERT()

   The condition is x > 10, but x is 5, so condition is false.

2. Step 2: Understand configASSERT() behavior on false condition

   configASSERT() halts the program immediately when the condition is false, so the printf line is never reached.

3. Final Answer:

   Program halts at configASSERT, no output -> Option C

4. Quick Check:

   False condition stops program = A [OK]

Hint: False condition in configASSERT() stops program before next lines [OK]

Common Mistakes:

• Assuming code after configASSERT() runs anyway
• Thinking configASSERT() causes compile error
• Ignoring that condition is false

4. You wrote this code:

int *ptr = NULL;
configASSERT(ptr != NULL);

But the program crashes immediately. What is the most likely cause?

medium

A. The pointer should be NULL to avoid crash

B. The pointer ptr is NULL, so configASSERT() halts the program

C. configASSERT() syntax is incorrect and causes crash

D. configASSERT() only works in release builds

Solution

1. Step 1: Analyze the pointer value and assertion

   ptr is NULL, but configASSERT checks ptr != NULL, which is false.

2. Step 2: Understand configASSERT() behavior on false condition

   When the condition is false, configASSERT() halts the program immediately, causing the crash.

3. Final Answer:

   The pointer ptr is NULL, so configASSERT() halts the program -> Option B

4. Quick Check:

   NULL pointer fails assert halting program = C [OK]

Hint: Crash means assert condition was false, check pointer value [OK]

Common Mistakes:

• Thinking configASSERT() syntax caused crash
• Believing NULL pointer is safe here
• Assuming configASSERT() runs only in release

5. You want to use configASSERT() to check that a task creation function returns pdPASS. Which is the best way to write this assertion?

hard

A. configASSERT(xTaskCreate(...) == pdPASS);

B. if (xTaskCreate(...) != pdPASS) configASSERT(0);

C. configASSERT(xTaskCreate(...) != pdPASS);

D. configASSERT(xTaskCreate(...) = pdPASS);

Solution

1. Step 1: Understand the goal of the assertion

   We want to assert that xTaskCreate returns pdPASS, meaning task creation succeeded.

2. Step 2: Analyze each option's correctness

   configASSERT(xTaskCreate(...) == pdPASS); asserts the return equals pdPASS directly, which is clear and correct. if (xTaskCreate(...) != pdPASS) configASSERT(0); uses an if statement with configASSERT(0), which is less direct. configASSERT(xTaskCreate(...) != pdPASS); asserts return not equal pdPASS, which is wrong. configASSERT(xTaskCreate(...) = pdPASS); uses assignment (=) instead of comparison, causing syntax error.

3. Final Answer:

   configASSERT(xTaskCreate(...) == pdPASS); -> Option A

4. Quick Check:

   Assert equality to pdPASS directly = B [OK]

Hint: Assert task creation equals pdPASS directly with == [OK]

Common Mistakes:

• Using assignment (=) instead of comparison (==)
• Asserting inequality instead of equality
• Using if with configASSERT(0) unnecessarily