Volatile keyword and why it matters in Embedded C - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the volatile keyword mean in embedded C?

The volatile keyword tells the compiler that a variable's value can change at any time, outside the program's control, so it should not optimize or cache its value.

beginner

Why should you use volatile for hardware registers or shared variables?

Because hardware registers or shared variables can change unexpectedly (like by hardware or another thread), volatile ensures the program always reads the current value from memory.

intermediate

What can happen if you forget to declare a variable as volatile when needed?

The compiler might optimize by caching the variable's value, causing the program to use outdated data and behave incorrectly.

beginner

Example:
volatile int flag;
What does this declaration tell the compiler?

It tells the compiler that flag can change anytime, so it must always read flag from memory and never assume it knows its value.

intermediate

How does volatile relate to interrupt service routines (ISRs)?

Variables shared between main code and ISRs should be volatile so the main code always sees the latest value changed by the ISR.

What does the volatile keyword prevent the compiler from doing?

A Running the program faster

B Allowing variables to be changed

C Optimizing away repeated reads of a variable

D Declaring variables

volatile tells the compiler not to optimize by caching or removing repeated reads of a variable because its value can change unexpectedly.

When should you use volatile in embedded C?

A For variables changed by hardware or interrupts

B For variables that never change

C For local variables inside functions only

D For constants

Use volatile for variables that can change outside the program flow, like hardware registers or variables modified by interrupts.

What might happen if a shared variable between main code and ISR is NOT declared volatile?

A The program will run faster

B The main code might use a stale cached value

C The variable will always update correctly

D The compiler will throw an error

Without volatile, the compiler may cache the variable, so main code might not see updates made by the ISR.

Which of these is a correct use of volatile?

A volatile int sensor_value;

B int volatile sensor_value = 5;

C None of the above

D Both A and B

Both volatile int and int volatile are valid ways to declare a volatile variable in C.

Does volatile guarantee atomicity or thread safety?

A No, it only prevents compiler optimizations

B Yes, it makes operations atomic

C Yes, it locks the variable

D No, it disables interrupts

volatile only tells the compiler not to optimize; it does not make operations atomic or thread-safe.

Explain in your own words why the volatile keyword is important in embedded programming.

Think about variables that can change outside your program's control.

Describe a situation where forgetting to use volatile could cause a bug.

Imagine a flag changed by an interrupt that main code checks.

Practice

1. What does the volatile keyword tell the compiler about a variable?

easy

A. The variable is stored in a register for faster access

B. The variable is constant and never changes

C. The variable is only used inside a function

D. The variable can change at any time outside the program flow

Solution

1. Step 1: Understand the role of volatile

   The volatile keyword tells the compiler that the variable's value can change unexpectedly, such as by hardware or interrupts.

2. Step 2: Identify what this means for the compiler

   The compiler must not optimize away reads or writes to this variable because its value can change outside normal program flow.

3. Final Answer:

   The variable can change at any time outside the program flow -> Option D

4. Quick Check:

   volatile means variable changes anytime [OK]

Hint: Volatile means variable can change anytime outside code [OK]

Common Mistakes:

• Thinking volatile means variable is constant
• Assuming volatile stores variable in register
• Confusing volatile with static or const

2. Which of the following is the correct syntax to declare a volatile integer variable named flag?

easy

A. int volatile flag;

B. volatile int flag;

C. Both A and B are correct

D. int flag volatile;

Solution

1. Step 1: Recall volatile declaration syntax

   In C, volatile can appear before or after the type specifier, so both volatile int flag; and int volatile flag; are valid.

2. Step 2: Check each option

   int volatile flag; and volatile int flag; are both correct syntax. int flag volatile; is invalid because volatile must come before or immediately after the type, not after the variable name.

3. Final Answer:

   Both A and B are correct -> Option C

4. Quick Check:

   Volatile can be before or after type [OK]

Hint: Volatile can be before or after type keyword [OK]

Common Mistakes:

• Placing volatile after variable name
• Using volatile without type
• Confusing volatile with const syntax

3. Consider this code snippet:

volatile int flag = 0;

void loop() {
  while(flag == 0) {
    // wait
  }
  // do something
}

What happens if flag is not declared volatile and is changed by an interrupt?

medium

A. The loop may never end because compiler optimizes flag check

B. The loop ends immediately as expected

C. Compilation error due to missing volatile

D. The program crashes

Solution

1. Step 1: Understand compiler optimization without volatile

   If flag is not volatile, the compiler may assume it does not change inside the loop and optimize by reading it once.

2. Step 2: Effect on loop behavior

   Because the compiler caches the value, changes made by interrupts to flag may be ignored, causing the loop to never end.

3. Final Answer:

   The loop may never end because compiler optimizes flag check -> Option A

4. Quick Check:

   Without volatile, compiler may cache variable [OK]

Hint: Without volatile, compiler may cache variable causing infinite loop [OK]

Common Mistakes:

• Thinking code will always work without volatile
• Assuming volatile causes compilation errors
• Believing volatile slows down program always

4. Identify the problem in this code snippet:

int data_ready = 0;

void ISR() {
  data_ready = 1;
}

void main_loop() {
  while(data_ready == 0) {
    // wait
  }
  // process data
}

How to fix it?

medium

A. Declare data_ready as volatile int data_ready = 0;

B. Make data_ready a global constant

C. Remove the while loop

D. Declare data_ready as static int data_ready = 0;

Solution

1. Step 1: Identify variable shared with ISR

   data_ready is changed inside an interrupt service routine (ISR) and read in main loop.

2. Step 2: Understand why volatile is needed

   Without volatile, compiler may optimize and cache data_ready, ignoring changes from ISR.

3. Step 3: Fix by declaring volatile

   Declaring volatile int data_ready = 0; tells compiler to always read fresh value.

4. Final Answer:

   Declare data_ready as volatile int data_ready = 0; -> Option A

5. Quick Check:

   Shared ISR variables must be volatile [OK]

Hint: Make ISR-shared variables volatile to avoid caching [OK]

Common Mistakes:

• Using static instead of volatile
• Removing loop without fixing variable
• Making variable constant incorrectly

5. You have a hardware register at address 0x4000 that changes asynchronously. Which declaration ensures safe access to this register in embedded C?

hard

A. int *reg = (int *)0x4000;

B. volatile int *reg = (int *)0x4000;

C. const int *reg = (int *)0x4000;

D. static int *reg = (int *)0x4000;

Solution

1. Step 1: Understand hardware register behavior

   Hardware registers can change anytime outside program control, so compiler must not optimize access.

2. Step 2: Choose correct pointer declaration

   Declaring pointer as volatile int * tells compiler to always read/write actual memory, not cached value.

3. Step 3: Evaluate options

   int *reg = (int *)0x4000; lacks volatile, risking optimization. const int *reg = (int *)0x4000; makes it constant, disallowing writes. static int *reg = (int *)0x4000; uses static incorrectly.

4. Final Answer:

   volatile int *reg = (int *)0x4000; -> Option B

5. Quick Check:

   Hardware registers need volatile pointers [OK]

Hint: Use volatile pointer for hardware registers [OK]

Common Mistakes:

• Omitting volatile causing stale reads
• Using const preventing writes
• Confusing static with volatile