Volatile keyword and why it matters in Embedded C

Introduction

The volatile keyword tells the computer that a variable can change at any time, even if the program does not change it. This helps the program always get the latest value.

Reading a hardware sensor value that can change anytime.

Working with variables shared between main code and interrupt handlers.

Accessing memory-mapped device registers that update independently.

Using flags that can be changed by other parts of the program or hardware.

Syntax

Embedded C

volatile type variable_name;

volatile is placed before the variable type.

It tells the compiler not to optimize or cache the variable value.

Examples

This declares an integer variable sensor_value that can change anytime.

Embedded C

volatile int sensor_value;

This declares a character variable flag that may be changed outside normal program flow.

Embedded C

volatile char flag;

Sample Program

This program shows a volatile variable counter that can be changed by an interrupt handler. The main program prints the value before and after the interrupt changes it.

Embedded C

#include <stdio.h>

volatile int counter = 0;

void interrupt_handler() {
    // This simulates an interrupt changing the counter
    counter++;
}

int main() {
    printf("Counter before interrupt: %d\n", counter);
    interrupt_handler();
    printf("Counter after interrupt: %d\n", counter);
    return 0;
}

Important Notes

Without volatile, the compiler might assume the variable never changes and keep an old value.

Use volatile only when needed, because it can slow down the program.

Summary

volatile tells the program a variable can change anytime.

It is important for hardware and interrupt-related variables.

It prevents the compiler from optimizing away important updates.

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