Why GPIO is the foundation of embedded in Embedded C - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set a GPIO pin as output.

Embedded C

GPIO_InitTypeDef GPIO_InitStruct = {0};
GPIO_InitStruct.Pin = GPIO_PIN_5;
GPIO_InitStruct.Mode = [1];
HAL_GPIO_Init(GPIOA, &GPIO_InitStruct);

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

AGPIO_MODE_OUTPUT_PP

BGPIO_MODE_INPUT

CGPIO_MODE_ANALOG

DGPIO_MODE_IT_RISING

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing input mode instead of output mode.

To set a GPIO pin as output, you use GPIO_MODE_OUTPUT_PP which means push-pull output mode.

2fill in blank

medium

Complete the code to read the state of a GPIO pin.

Embedded C

int pin_state = HAL_GPIO_ReadPin(GPIOB, [1]);

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

AGPIO_PIN_3

BGPIO_PIN_0

CGPIO_PIN_12

DGPIO_PIN_7

Attempts:

3 left

💡 Hint

Common Mistakes

Using a pin number not defined or not connected.

We read the state of pin 7 on port B using GPIO_PIN_7.

3fill in blank

hard

Fix the error in the code to toggle a GPIO pin.

Embedded C

HAL_GPIO_TogglePin(GPIOC, [1]);

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

AGPIO_PIN_13

BGPIO_PIN_8

CGPIO_PIN_5

DGPIO_PIN_0

Attempts:

3 left

💡 Hint

Common Mistakes

Using a pin that is not configured as output.

Pin 13 on port C is commonly used for toggling an LED on many boards.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that maps pin numbers to their states if the pin state is high.

Embedded C

pin_states = {pin: HAL_GPIO_ReadPin(GPIOA, pin) for pin in pins if HAL_GPIO_ReadPin(GPIOA, pin) [1] [2]

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

A==

BGPIO_PIN_5

CGPIO_PIN_SET

D!=

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong comparison operator or wrong pin state constant.

The condition checks if the pin state is equal to GPIO_PIN_SET, which means the pin is high.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps pin names in uppercase to their states if the state is low.

Embedded C

pin_status = { [1]: HAL_GPIO_ReadPin(GPIOB, [2]) for [3] in pins if HAL_GPIO_ReadPin(GPIOB, pin) == GPIO_PIN_RESET }

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

Apin.upper()

Bpin

Dpin_name

Attempts:

3 left

💡 Hint

Common Mistakes

Using inconsistent variable names or wrong key formatting.

The dictionary keys are the uppercase pin names, values are the pin states, and the loop variable is pin.

Practice

1. Why are GPIO pins considered the foundation of embedded systems?

easy

A. Because they allow microcontrollers to interact with external devices by sending and receiving signals

B. Because they store large amounts of data for processing

C. Because they provide power to the microcontroller

D. Because they control the clock speed of the processor

Solution

1. Step 1: Understand GPIO function

   GPIO pins are used to send and receive simple digital signals to control or read from external devices.

2. Step 2: Identify why this is foundational

   Since embedded systems interact with hardware, GPIO pins are essential for this communication.

3. Final Answer:

   Because they allow microcontrollers to interact with external devices by sending and receiving signals -> Option A

4. Quick Check:

   GPIO = Basic hardware communication [OK]

Hint: GPIO connects microcontrollers to hardware signals [OK]

Common Mistakes:

• Thinking GPIO stores data
• Confusing GPIO with power supply pins
• Assuming GPIO controls processor speed

2. Which of the following is the correct way to configure a GPIO pin as output in embedded C?

easy

A. GPIO_DIR &= ~(1 << PIN_NUMBER);

B. GPIO_DIR |= (1 << PIN_NUMBER);

C. GPIO_DATA |= (1 << PIN_NUMBER);

D. GPIO_DATA &= ~(1 << PIN_NUMBER);

Solution

1. Step 1: Understand GPIO direction register

   Setting a bit in the direction register (GPIO_DIR) to 1 configures the pin as output.

2. Step 2: Analyze options

   GPIO_DIR |= (1 << PIN_NUMBER); sets the bit, configuring output. GPIO_DIR &= ~(1 << PIN_NUMBER); clears the bit (input). Options C and D modify data, not direction.

3. Final Answer:

   GPIO_DIR |= (1 << PIN_NUMBER); -> Option B

4. Quick Check:

   Set direction bit = output [OK]

Hint: Set GPIO_DIR bit to 1 for output [OK]

Common Mistakes:

• Modifying GPIO_DATA instead of GPIO_DIR
• Clearing bit instead of setting for output
• Confusing input and output configuration

3. Given the code snippet:

GPIO_DIR |= (1 << 3);  // Set pin 3 as output
GPIO_DATA &= ~(1 << 3); // Clear pin 3 (set low)
GPIO_DATA |= (1 << 3);  // Set pin 3 (set high)
int state = (GPIO_DATA & (1 << 3)) ? 1 : 0;

What is the value of state after execution?

medium

A. 0

B. Undefined

C. 1

D. Depends on previous pin state

Solution

1. Step 1: Trace pin configuration and data changes

   Pin 3 is set as output. Then pin 3 is cleared (low), then set (high).

2. Step 2: Evaluate final pin state

   After setting pin 3 high, reading GPIO_DATA & (1 << 3) returns non-zero, so state = 1.

3. Final Answer:

   1 -> Option C

4. Quick Check:

   Pin set high means state = 1 [OK]

Hint: Last pin set operation determines state [OK]

Common Mistakes:

• Ignoring the last set operation
• Confusing bitwise AND result with zero
• Assuming pin state depends on previous value

4. Identify the error in this GPIO pin initialization code:

GPIO_DIR &= ~(1 << 5);  // Configure pin 5 as output
GPIO_DATA |= (1 << 5);  // Set pin 5 high

medium

A. Pin 5 is configured as input, not output

B. Pin 5 is not set high correctly

C. GPIO_DATA should be cleared, not set

D. No error, code is correct

Solution

1. Step 1: Analyze GPIO_DIR operation

   Clearing bit 5 in GPIO_DIR sets pin 5 as input, not output.

2. Step 2: Check pin configuration vs usage

   Setting GPIO_DATA bit 5 high has no effect if pin is input.

3. Final Answer:

   Pin 5 is configured as input, not output -> Option A

4. Quick Check:

   Clear DIR bit = input, not output [OK]

Hint: Clear DIR bit = input, set DIR bit = output [OK]

Common Mistakes:

• Confusing input and output bits
• Assuming setting DATA works for input pins
• Ignoring direction register effect

5. You want to toggle an LED connected to GPIO pin 2 every second. Which code snippet correctly implements this using GPIO registers in embedded C?

while(1) {
    // Toggle pin 2
    GPIO_DATA ^= (1 << 2);
    // Wait 1 second
    delay(1000);
}

What is the key reason this code works for controlling the LED?

hard

A. Because XOR operation clears the pin permanently

B. Because delay(1000) sets the pin high for 1 second

C. Because GPIO_DIR is automatically set to output by default

D. Because toggling GPIO_DATA bit changes the pin output state, turning LED on/off

Solution

1. Step 1: Understand GPIO_DATA toggle

   XOR operation flips the bit state, changing pin output from high to low or low to high.

2. Step 2: Connect toggle to LED behavior

   Changing pin output turns LED on or off, creating blinking effect with delay.

3. Final Answer:

   Because toggling GPIO_DATA bit changes the pin output state, turning LED on/off -> Option D

4. Quick Check:

   Toggle bit = LED blink [OK]

Hint: XOR toggles pin state to blink LED [OK]

Common Mistakes:

• Assuming delay sets pin state
• Forgetting to set GPIO_DIR as output
• Misunderstanding XOR effect on bits