Memory-mapped I/O concept in Embedded C - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a pointer to a memory-mapped I/O register at address 0x40021000.

Embedded C

volatile unsigned int *reg = (volatile unsigned int *)[1];

Drag options to blanks, or click blank then click option'

A0x20000000

B0x40021000

C0x60000000

D0x10000000

Attempts:

3 left

💡 Hint

Common Mistakes

Using an incorrect address that does not map to the desired peripheral.

The address 0x40021000 is the correct base address for the memory-mapped I/O register in this example.

2fill in blank

medium

Complete the code to write the value 0x01 to the memory-mapped register pointed by reg.

Embedded C

*reg = [1];

Drag options to blanks, or click blank then click option'

A0x10

B0xFF

C0x01

D0x00

Attempts:

3 left

💡 Hint

Common Mistakes

Writing 0x10 or 0xFF which sets other bits unintentionally.

Writing 0x01 sets the first bit of the register, often used to enable a feature.

3fill in blank

hard

Fix the error in the code to correctly read the value from the memory-mapped register.

Embedded C

unsigned int value = [1]reg;

Drag options to blanks, or click blank then click option'

A*

B&

C->

D.

Attempts:

3 left

💡 Hint

Common Mistakes

Using ® which gives the address of the pointer variable, not the register.

The dereference operator * is used to read the value pointed to by reg.

4fill in blank

hard

Fill both blanks to define a pointer to a volatile 8-bit register at address 0x50000010 and write 0xFF to it.

Embedded C

volatile [1] *reg8 = (volatile [2] *)0x50000010;
*reg8 = 0xFF;

Drag options to blanks, or click blank then click option'

Aunsigned char

Bunsigned int

Cchar

Dint

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'unsigned int' which is typically 32-bit and incorrect for 8-bit registers.

Using 'unsigned char' defines an 8-bit volatile pointer suitable for 8-bit registers.

5fill in blank

hard

Fill all three blanks to create a macro that reads a 16-bit memory-mapped register at a given address.

Embedded C

#define READ_REG16(addr) (*(volatile [1] *)[2])

unsigned short val = READ_REG16([3]);

Drag options to blanks, or click blank then click option'

Aunsigned short

B(addr)

C0x40002000

Dunsigned int

Attempts:

3 left

💡 Hint

Common Mistakes

Using unsigned int which is 32-bit, or wrong addresses.

The macro casts the address to a volatile unsigned short pointer and dereferences it. The address passed to the macro is 0x40002000.

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