Volatile keyword and why it matters in Embedded C - Step-by-Step Execution

Concept Flow - Volatile keyword and why it matters

Declare volatile variable

↓

Compiler reads variable

↓

Variable value may change anytime

↓

Compiler must NOT optimize reads/writes

↓

Program uses latest variable value

↓

Correct behavior with hardware/interrupts

The volatile keyword tells the compiler a variable can change anytime outside program control, so it must always read/write it fresh.

Execution Sample

Embedded C

volatile int flag = 0;

void interrupt_handler() {
  flag = 1;
}

int main() {
  while(flag == 0) {
    // wait
  }
  return 0;
}

This code waits until an interrupt sets 'flag' to 1. 'flag' is volatile to ensure the loop sees the change.

Execution Table

Step	Action	Variable 'flag' Value Read	Compiler Optimization Allowed?	Effect on Program
1	Initialize flag to 0	0	No (volatile)	flag is 0, loop starts
2	Enter while loop, check flag	0	No	Loop continues waiting
3	Interrupt occurs, sets flag to 1	1	No	flag updated outside main flow
4	Next loop check reads flag	1	No	Loop exits because flag == 1
5	Program continues after loop	1	No	Correct behavior, sees updated flag

💡 Loop exits when flag changes to 1, compiler reads fresh value each time due to volatile

Variable Tracker

Variable	Start	After Step 1	After Step 3	Final
flag	undefined	0	1	1

Key Moments - 2 Insights

Why can't the compiler optimize by caching 'flag' in a register inside the loop?

Because 'flag' is declared volatile, the compiler must read it from memory every time to catch changes made outside the program flow, like interrupts (see execution_table step 4).

What happens if 'flag' is NOT declared volatile?

The compiler might cache 'flag' in a register and never see the interrupt change, causing an infinite loop (compare execution_table step 2 and 4).

Visual Quiz - 3 Questions

Look at the execution table, what value of 'flag' causes the loop to exit?

A -1

B 0

C 1

D Undefined

💡 Hint

Check step 4 and 5 where the loop condition changes and exits.

At which step does the interrupt change the value of 'flag'?

A Step 1

B Step 3

C Step 2

D Step 5

💡 Hint

Look for the step where 'flag' changes from 0 to 1 in the execution_table.

If 'flag' was not volatile, what might the compiler do during the loop?

A Cache 'flag' in a register and never see changes

B Set 'flag' to 1 automatically

C Always read 'flag' from memory

D Ignore the variable completely

💡 Hint

Refer to key_moments about compiler optimization and caching.

Concept Snapshot

volatile keyword in C:
- Declares variable can change unexpectedly
- Prevents compiler optimizations caching variable
- Ensures every read/write accesses actual memory
- Essential for hardware registers, interrupts
- Without volatile, program may behave incorrectly

Full Transcript

The volatile keyword tells the compiler that a variable's value can change at any time outside the normal program flow, such as by hardware or interrupts. This means the compiler must always read the variable from memory and not optimize by caching it in a register. In the example, a volatile flag variable is set to 0 initially. The program waits in a loop checking this flag. When an interrupt sets the flag to 1, the loop sees the change immediately and exits. Without volatile, the compiler might cache the flag value and never see the update, causing an infinite loop. This trace shows each step where the flag is read and updated, explaining why volatile matters for correct embedded programming.

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