Reading a hardware register in Embedded C - Time & Space Complexity

Time Complexity: Reading a hardware register

O(n)

Understanding Time Complexity

When reading a hardware register, we want to know how the time to read changes as we do more reads.

We ask: How does the work grow if we read the register many times?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

volatile uint32_t *REG = (uint32_t *)0x40000000;
uint32_t read_value;

for (int i = 0; i < n; i++) {
    read_value = *REG;
}
    

This code reads a hardware register at a fixed address n times in a loop.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Reading the hardware register once per loop.
• How many times: The read happens n times, once each loop cycle.

How Execution Grows With Input

Each time we increase n, the number of reads grows the same amount.

Input Size (n)	Approx. Operations
10	10 reads
100	100 reads
1000	1000 reads

Pattern observation: The work grows directly with n. Double n, double the reads.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete grows in a straight line as you read more times.

Common Mistake

[X] Wrong: "Reading a hardware register is instant and does not add time."

[OK] Correct: Each read takes some time, so doing many reads adds up and grows with n.

Interview Connect

Understanding how repeated hardware reads affect time helps you reason about performance in embedded systems.

Self-Check

"What if we added a delay inside the loop after each read? How would the time complexity change?"

Practice

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

easy

A. It makes the variable read-only.

B. It allocates extra memory for the variable.

C. It tells the compiler the value can change anytime, preventing optimization.

D. It initializes the variable to zero automatically.

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.

2. Step 2: Prevent compiler optimization

   This prevents the compiler from optimizing away repeated reads or caching the value, ensuring the program reads the actual hardware register each time.

3. Final Answer:

   It tells the compiler the value can change anytime, preventing optimization. -> Option C

4. Quick Check:

   volatile prevents optimization = B [OK]

Hint: Use volatile to avoid compiler caching hardware register reads [OK]

Common Mistakes:

• Thinking volatile makes variable read-only
• Assuming volatile allocates extra memory
• Believing volatile initializes variables

2. Which of the following is the correct syntax to read a 32-bit hardware register at address 0x40021000 in embedded C?

easy

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

B. volatile int *reg = 0x40021000;

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

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

Solution

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

   The pointer must be declared volatile to prevent optimization, so volatile int * is correct.

2. Step 2: Dereference the volatile pointer to read the value

   Dereferencing (volatile int *)0x40021000 reads the 32-bit register safely.

3. Final Answer:

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

4. Quick Check:

   volatile pointer dereference = A [OK]

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

Common Mistakes:

• Not using volatile for pointer or dereference
• Assigning address directly to pointer without cast
• Using non-volatile pointer causing optimization

3. What will be the output of this code snippet if the hardware register at 0x50000000 contains the value 0xABCD1234?

volatile unsigned int *reg = (volatile unsigned int *)0x50000000;
unsigned int val = *reg;
printf("0x%X", val);

medium

A. 0xABCD1234

B. 0x1234ABCD

C. 0x0

D. Compilation error

Solution

1. Step 1: Understand pointer and dereference

   The pointer reg points to the hardware register address and is volatile to read actual value.

2. Step 2: Read and print the register value

   Dereferencing *reg reads the value 0xABCD1234, which is printed in hexadecimal format.

3. Final Answer:

   0xABCD1234 -> Option A

4. Quick Check:

   Dereference prints register value = C [OK]

Hint: Dereference volatile pointer to get exact register value [OK]

Common Mistakes:

• Assuming byte order changes output
• Forgetting volatile causes stale reads
• Expecting compilation error due to pointer cast

4. Identify the error in this code snippet intended to read a 16-bit hardware register at address 0x40001000:

unsigned short *reg = (unsigned short *)0x40001000;
unsigned short val = *reg;

medium

A. Incorrect pointer type; should be int * instead of unsigned short *.

B. Missing volatile keyword for pointer declaration.

C. Address should be assigned without a cast.

D. Dereferencing pointer without using & operator.

Solution

1. Step 1: Check pointer declaration for hardware register

   Hardware registers can change anytime, so pointer must be declared volatile.

2. Step 2: Identify missing volatile keyword

   The code lacks volatile, risking compiler optimization and stale reads.

3. Final Answer:

   Missing volatile keyword for pointer declaration. -> Option B

4. Quick Check:

   volatile missing = A [OK]

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

Common Mistakes:

• Ignoring volatile causes wrong reads
• Changing pointer type unnecessarily
• Misusing address-of operator on pointer dereference

5. You need to read a 8-bit status register at address 0x60000010 repeatedly in a loop until bit 3 becomes 1. Which code snippet correctly implements this in embedded C?

hard

A. volatile unsigned char *status = (volatile unsigned char *)0x60000010;
while (!(*status & (1 << 3))) {}
// proceed

B. unsigned char *status = (unsigned char *)0x60000010;
while (!(*status & (1 << 3))) {}
// proceed

C. volatile unsigned char status = *(volatile unsigned char *)0x60000010;
while (!(status & (1 << 3))) {}
// proceed

D. unsigned char status = *(unsigned char *)0x60000010;
while (!(status & (1 << 3))) {}
// proceed

Solution

1. Step 1: Use volatile pointer to read changing register

   Declare a volatile pointer to the 8-bit register to read fresh value each loop.

2. Step 2: Loop until bit 3 is set by checking bit mask

   Use bitwise AND with (1 << 3) to test bit 3 in the register value inside the loop.

3. Final Answer:

   volatile unsigned char *status = (volatile unsigned char *)0x60000010; while (!(*status & (1 << 3))) {} // proceed -> Option A

4. Quick Check:

   volatile pointer + bit check loop = D [OK]

Hint: Use volatile pointer and bit mask in loop condition [OK]

Common Mistakes:

• Not using volatile pointer causing stale reads
• Reading register once before loop instead of inside
• Incorrect bit mask or missing parentheses