Writing to a hardware register in Embedded C - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this hardware register write simulation?

Consider this embedded C code simulating writing to a hardware register. What value will be stored in REG after execution?

Embedded C

volatile unsigned int REG = 0x00;

void write_register(unsigned int value) {
    REG = value | 0x0F;
}

int main() {
    write_register(0xF0);
    return REG;
}

A 0xF0

B 0xFF

C 0x0F

D 0x00

💡 Hint

Remember the bitwise OR operation sets bits that are set in either operand.

The function write_register sets REG to the bitwise OR of value and 0x0F. Since value is 0xF0, OR with 0x0F results in 0xFF.

🧠 Conceptual

intermediate

Which statement correctly describes volatile keyword in hardware register access?

Why is the volatile keyword important when declaring hardware registers in embedded C?

A It allows the variable to be shared between multiple threads.

B It makes the variable read-only to protect hardware registers.

C It initializes the variable to zero automatically.

D It tells the compiler the variable can change unexpectedly, preventing optimization.

💡 Hint

Think about how hardware registers can change outside program control.

The volatile keyword prevents the compiler from optimizing away reads or writes to the variable, because the value can change at any time due to hardware events.

🔧 Debug

advanced

Why does this hardware register write code cause a runtime error?

Examine the code below. It attempts to write to a hardware register but causes a runtime error. What is the cause?

Embedded C

unsigned int *REG = NULL;

void write_register(unsigned int value) {
    *REG = value;
}

int main() {
    write_register(0xAA);
    return 0;
}

A Dereferencing a NULL pointer causes a runtime error.

B The value 0xAA is invalid for hardware registers.

C Missing volatile keyword causes undefined behavior.

D The function write_register is missing a return statement.

💡 Hint

Check the pointer initialization before dereferencing.

The pointer REG is initialized to NULL. Dereferencing it to write causes a runtime crash (segmentation fault).

📝 Syntax

advanced

Which option correctly writes 0x55 to a hardware register at address 0x4000?

Choose the correct C code snippet to write the value 0x55 to a hardware register located at memory address 0x4000.

A *(volatile unsigned int *)0x4000 = 0x55;

B volatile unsigned int *reg = 0x4000; *reg = 0x55;

C *(unsigned int 0x4000) = 0x55;

D unsigned int reg = (volatile unsigned int *)0x4000; reg = 0x55;

💡 Hint

Remember how to cast an address to a pointer and write through it.

Option A correctly casts the address to a volatile pointer and dereferences it to assign the value.

🚀 Application

expert

How many bits are set in the hardware register after this write?

Given the following code, how many bits are set to 1 in the REG after execution?

Embedded C

volatile unsigned char REG = 0x00;

void set_bits(unsigned char mask) {
    REG |= mask;
}

int main() {
    set_bits(0x0F);  // sets lower 4 bits
    set_bits(0x33);  // sets bits 0,1,4,5
    return 0;
}

A 4

B 5

C 6

D 7

💡 Hint

Count the bits set after both OR operations.

After first call, REG = 0x0F (bits 0-3 set). After second call, REG |= 0x33 sets bits 0,1,4,5. Combined bits set are 0,1,2,3,4,5 = 6 bits.

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