Writing to a hardware register in Embedded C

Introduction

We write to hardware registers to control devices like LEDs, motors, or sensors directly from our program.

Turning an LED on or off by changing its control register.

Setting the speed of a motor by writing to its speed register.

Configuring a sensor by writing settings to its control register.

Starting or stopping a hardware timer by writing to its control register.

Syntax

Embedded C

*(volatile uint32_t *)REGISTER_ADDRESS = VALUE;

REGISTER_ADDRESS is the memory address of the hardware register.

volatile tells the compiler the value can change anytime outside the program.

Examples

Write the value 0x01 to the hardware register at address 0x40021018.

Embedded C

*(volatile uint32_t *)0x40021018 = 0x01;

Define a name for the register and write 0xFF to it.

Embedded C

#define LED_REG (*(volatile uint32_t *)0x50000000)
LED_REG = 0xFF;

Sample Program

This program writes the value 1 to the LED register to turn it on.

Embedded C

#include <stdint.h>

#define LED_REGISTER (*(volatile uint32_t *)0x50000000)

int main() {
    // Turn on the LED by writing 1 to the register
    LED_REGISTER = 1;
    
    // Normally embedded programs run forever, but here we just return
    return 0;
}

Important Notes

Always use volatile when accessing hardware registers to prevent unwanted compiler optimizations.

Be careful with the register address; writing to the wrong address can cause unexpected behavior.

Hardware registers often require specific values or bit patterns; check the device manual.

Summary

Writing to hardware registers lets your program control physical devices.

Use pointers with volatile to access registers safely.

Always check the correct address and value before writing.

Practice

1. What is the main reason to use the volatile keyword when writing to a hardware register in embedded C?

easy

A. To tell the compiler the value can change unexpectedly and prevent optimization

B. To make the variable read-only

C. To allocate memory on the stack

D. To initialize the register with zero

Solution

1. Step 1: Understand the role of volatile

   The volatile keyword tells the compiler that the variable's value can change at any time, outside the program's control.

2. Step 2: Prevent compiler optimization on hardware registers

   Hardware registers can change independently, so the compiler must not optimize away reads or writes to them.

3. Final Answer:

   To tell the compiler the value can change unexpectedly and prevent optimization -> Option A

4. Quick Check:

   volatile prevents optimization for hardware registers [OK]

Hint: Use volatile to stop compiler optimizing hardware register access [OK]

Common Mistakes:

• Thinking volatile makes variable read-only
• Assuming volatile allocates memory
• Using volatile to initialize values

2. Which of the following is the correct syntax to write the value 0xFF to a hardware register at address 0x40021000 in embedded C?

easy

A. register = 0xFF at 0x40021000;

B. volatile int 0x40021000 = 0xFF;

C. unsigned int *0x40021000 = 0xFF;

D. *((volatile unsigned int *)0x40021000) = 0xFF;

Solution

1. Step 1: Use pointer casting with volatile

   To write to a hardware register, cast the address to a pointer to volatile unsigned int.

2. Step 2: Dereference pointer and assign value

   Use the dereference operator (*) to write the value 0xFF to the address.

3. Final Answer:

   *((volatile unsigned int *)0x40021000) = 0xFF; -> Option D

4. Quick Check:

   Pointer cast + dereference = correct syntax [OK]

Hint: Cast address to volatile pointer and dereference to write [OK]

Common Mistakes:

• Trying to assign value directly to address
• Missing volatile keyword
• Incorrect pointer syntax

3. What will be the output of the following code snippet if the hardware register at address 0x50000000 initially contains 0x00?

volatile unsigned char *reg = (volatile unsigned char *)0x50000000;
*reg = 0xAA;
unsigned char val = *reg;

medium

A. val will be 0xAA

B. val will be 0x00

C. val will be undefined

D. Compilation error

Solution

1. Step 1: Write 0xAA to the hardware register

   The pointer reg points to the register address; writing 0xAA stores this value in the register.

2. Step 2: Read back the value from the register

   Reading from *reg returns the stored value 0xAA, which is assigned to val.

3. Final Answer:

   val will be 0xAA -> Option A

4. Quick Check:

   Write then read returns stored value [OK]

Hint: Write then read from register returns stored value [OK]

Common Mistakes:

• Assuming register value does not change after write
• Confusing pointer dereference with variable assignment
• Expecting compilation error due to volatile

4. Identify the error in the following code that writes 0x1F to a hardware register at address 0x60000000:

unsigned int *reg = (unsigned int *)0x60000000;
*reg = 0x1F;

medium

A. Incorrect address format

B. Missing volatile keyword in pointer declaration

C. Wrong data type for register value

D. Dereferencing pointer incorrectly

Solution

1. Step 1: Check pointer declaration for hardware register

   The pointer should be declared as volatile to prevent compiler optimizations on hardware registers.

2. Step 2: Understand impact of missing volatile

   Without volatile, compiler may optimize away reads/writes, causing incorrect hardware behavior.

3. Final Answer:

   Missing volatile keyword in pointer declaration -> Option B

4. Quick Check:

   Hardware register pointers must be volatile [OK]

Hint: Always add volatile to hardware register pointers [OK]

Common Mistakes:

• Ignoring volatile keyword
• Thinking address format is wrong
• Assuming data type must be different

5. You need to toggle bit 3 (zero-based) of a hardware register at address 0x70000000 without affecting other bits. Which code snippet correctly performs this operation?

hard

A. *((volatile unsigned int *)0x70000000) |= (1 << 3);

B. *((volatile unsigned int *)0x70000000) &= ~(1 << 3);

C. *((volatile unsigned int *)0x70000000) ^= (1 << 3);

D. *((volatile unsigned int *)0x70000000) = (1 << 3);

Solution

1. Step 1: Understand toggling a bit

   Toggling means flipping the bit: if 0 then 1, if 1 then 0. This is done using XOR (^=) with a mask.

2. Step 2: Apply XOR with bit mask

   Using ^= (1 << 3) flips only bit 3 without changing other bits.

3. Final Answer:

   *((volatile unsigned int *)0x70000000) ^= (1 << 3); -> Option C

4. Quick Check:

   XOR toggles bits, OR sets bits, AND clears bits [OK]

Hint: Use XOR (^=) with bit mask to toggle bits safely [OK]

Common Mistakes:

• Using OR (|=) which only sets bits
• Using AND (&=) which clears bits
• Assigning mask directly overwrites all bits