Memory-mapped I/O concept in Embedded C - Mini Project: Build & Apply

Memory-mapped I/O Concept in Embedded C

📖 Scenario: You are working on a simple embedded system where you control an LED connected to a specific memory address. This address is part of the memory-mapped I/O region. Writing to this address turns the LED on or off.

🎯 Goal: You will create a small program that uses memory-mapped I/O to turn an LED on and off by writing to a specific memory address.

📋 What You'll Learn

Create a pointer to the LED control register at address 0x40021018

Create a variable to hold the LED ON value

Write the LED ON value to the memory address using the pointer

Print the value written to the LED control register

💡 Why This Matters

🌍 Real World

Memory-mapped I/O is used in embedded systems to control hardware devices like LEDs, buttons, and sensors by reading and writing to specific memory addresses.

💼 Career

Understanding memory-mapped I/O is essential for embedded software engineers working on microcontrollers, device drivers, and hardware interfacing.

1

Create a pointer to the LED control register

Create a pointer called led_reg that points to the memory address 0x40021018 as a volatile unsigned 32-bit integer.

Embedded C

// Your code here

Hint

Use a pointer with volatile to tell the compiler this memory can change outside the program.

2

Create a variable for LED ON value

Create an unsigned integer variable called LED_ON and set it to 1 to represent turning the LED on.

Embedded C

volatile unsigned int *led_reg = (volatile unsigned int *)0x40021018;
// Your code here

Hint

Use a simple unsigned int variable to hold the value 1.

3

Write the LED ON value to the memory address

Write the value of LED_ON to the memory address pointed to by led_reg using the dereference operator.

Embedded C

volatile unsigned int *led_reg = (volatile unsigned int *)0x40021018;
unsigned int LED_ON = 1;
// Your code here

Hint

Use *led_reg = LED_ON; to write the value to the hardware register.

4

Print the value written to the LED control register

Use printf to display the message "LED register value: %u\n" with the value stored at the memory address pointed to by led_reg.

Embedded C

volatile unsigned int *led_reg = (volatile unsigned int *)0x40021018;
unsigned int LED_ON = 1;
*led_reg = LED_ON;
// Your code here

Hint

Use printf("LED register value: %u\n", *led_reg); to print the value.

Practice

1.

What is the main purpose of memory-mapped I/O in embedded C?

easy

A. To perform file input/output operations

B. To allocate dynamic memory for variables

C. To manage network communication protocols

D. To control hardware devices using specific memory addresses

Solution

1. Step 1: Understand memory-mapped I/O concept

   Memory-mapped I/O assigns special memory addresses to hardware devices so the CPU can control them by reading/writing these addresses.

2. Step 2: Differentiate from other memory uses

   Unlike dynamic memory allocation or file/network I/O, memory-mapped I/O directly interfaces with hardware registers.

3. Final Answer:

   To control hardware devices using specific memory addresses -> Option D

4. Quick Check:

   Memory-mapped I/O = hardware control via memory [OK]

Hint: Memory-mapped I/O means hardware control via memory addresses [OK]

Common Mistakes:

• Confusing memory-mapped I/O with file or network I/O
• Thinking it allocates memory for variables
• Assuming it manages software protocols

2.

Which of the following is the correct way to declare a pointer for a memory-mapped hardware register at address 0x40021000 in embedded C?

easy

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

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

C. volatile int reg = 0x40021000;

D. int reg = (int *)0x40021000;

Solution

1. Step 1: Use volatile keyword for hardware registers

   Hardware registers can change anytime, so pointer must be declared volatile to prevent compiler optimizations.

2. Step 2: Correct pointer type and casting

   The pointer should be of type volatile int* and cast the address to (volatile int *) to access the register correctly.

3. Final Answer:

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

4. Quick Check:

   Use volatile pointer with correct cast [OK]

Hint: Always use volatile pointer cast for hardware addresses [OK]

Common Mistakes:

• Omitting volatile keyword
• Assigning address to int variable instead of pointer
• Wrong casting or missing pointer declaration

3.

Consider the following code snippet in embedded C:

volatile unsigned int *LED_REG = (volatile unsigned int *)0x50000000;
*LED_REG = 0xFF;
unsigned int value = *LED_REG;

What is the value of value after execution?

medium

A. 0x00

B. Compiler error

C. 0xFF

D. Undefined behavior

Solution

1. Step 1: Write 0xFF to hardware register

   The statement *LED_REG = 0xFF; writes the value 0xFF to the memory address 0x50000000.

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

   The next line reads the value from the same address, so value will be 0xFF as written.

3. Final Answer:

   0xFF -> Option C

4. Quick Check:

   Write then read same register = same value [OK]

Hint: Read returns last written value to hardware register [OK]

Common Mistakes:

• Assuming value resets to 0
• Thinking reading hardware register causes error
• Ignoring volatile keyword effects

4.

Identify the error in the following embedded C code snippet for memory-mapped I/O:

unsigned int *TIMER_REG = (unsigned int *)0x60000000;
*TIMER_REG = 0x01;

medium

A. Missing volatile keyword for pointer declaration

B. Incorrect address casting syntax

C. Pointer should be declared as int, not unsigned int

D. Cannot assign value directly to pointer

Solution

1. Step 1: Check pointer declaration for hardware register

   Hardware registers must be accessed via volatile pointers to prevent compiler optimizations that may skip reads/writes.

2. Step 2: Identify missing volatile keyword

   The pointer is declared as unsigned int * without volatile, which is incorrect for memory-mapped I/O.

3. Final Answer:

   Missing volatile keyword for pointer declaration -> Option A

4. Quick Check:

   Hardware pointers need volatile keyword [OK]

Hint: Always use volatile for hardware register pointers [OK]

Common Mistakes:

• Ignoring volatile keyword
• Confusing pointer type with variable type
• Thinking casting syntax is wrong

5.

You want to toggle a hardware LED connected to a memory-mapped register at address 0x70000000. The LED turns on when bit 0 is set to 1 and off when it is 0. Which code snippet correctly toggles the LED state without affecting other bits?

hard

A. volatile unsigned int *LED = (volatile unsigned int *)0x70000000;
*LED = *LED ^ 0x01;

B. volatile unsigned int *LED = (volatile unsigned int *)0x70000000;
*LED = 0x01;

C. unsigned int *LED = (unsigned int *)0x70000000;
*LED |= 0x01;

D. volatile unsigned int LED = 0x70000000;
LED ^= 0x01;

Solution

1. Step 1: Use volatile pointer to access hardware register

   Declare LED as volatile unsigned int pointer to ensure proper hardware access and prevent compiler optimization.

2. Step 2: Toggle bit 0 without affecting other bits

   Use XOR (^ 0x01) on *LED to flip bit 0 while leaving other bits unchanged.

3. Step 3: Check other options for errors

   volatile unsigned int *LED = (volatile unsigned int *)0x70000000; *LED = 0x01; overwrites all bits, C lacks volatile, D treats LED as variable not pointer.

4. Final Answer:

   volatile unsigned int *LED = (volatile unsigned int *)0x70000000; *LED = *LED ^ 0x01; -> Option A

5. Quick Check:

   Toggle bit with XOR on volatile pointer [OK]

Hint: Use XOR on volatile pointer to toggle bits safely [OK]

Common Mistakes:

• Overwriting entire register instead of toggling bit
• Missing volatile keyword causing optimization issues
• Using variable instead of pointer for hardware address