Reading digital input pin state in Embedded C - Step-by-Step Execution

Concept Flow - Reading digital input pin state

Start

↓

Configure pin as input

↓

Read pin state

↓

Check if HIGH or LOW

↓

If HIGH

→Do something

↓

If LOW

→Do something else

↓

End or Repeat

The program sets a pin as input, reads its state (HIGH or LOW), then acts based on that state.

Execution Sample

Embedded C

pinMode(2, INPUT);
int state = digitalRead(2);
if(state == HIGH) {
  // do something
} else {
  // do something else
}

This code sets pin 2 as input, reads its state, and runs code depending on whether the pin is HIGH or LOW.

Execution Table

Step	Action	Pin Mode	Pin State Read	Condition	Branch Taken	Output/Effect
1	Set pin 2 mode to INPUT	INPUT	N/A	N/A	N/A	Pin 2 ready for input
2	Read digital state of pin 2	INPUT	HIGH	state == HIGH?	Yes	Execute HIGH branch
3	Execute HIGH branch	INPUT	HIGH	N/A	N/A	Do something (e.g., turn LED on)
4	End or repeat	INPUT	HIGH	N/A	N/A	Program waits or loops
5	If pin state was LOW	INPUT	LOW	state == HIGH?	No	Execute LOW branch
6	Execute LOW branch	INPUT	LOW	N/A	N/A	Do something else (e.g., turn LED off)
7	End or repeat	INPUT	LOW	N/A	N/A	Program waits or loops

💡 Program stops or repeats after reading and acting on pin state

Variable Tracker

Variable	Start	After Step 2	After Step 5	Final
pin 2 mode	Undefined	INPUT	INPUT	INPUT
state	Undefined	HIGH	LOW	Depends on pin reading

Key Moments - 3 Insights

Why do we need to set the pin mode to INPUT before reading?

Because the microcontroller needs to know the pin is for input, not output. Step 1 in the execution_table shows setting pinMode to INPUT before reading the state.

What does digitalRead return if the pin is not connected?

It may return LOW or unpredictable values. The execution_table rows 2 and 5 show reading HIGH or LOW, but if floating, the value can be unstable.

Why do we check if state == HIGH instead of just using the value directly?

Because digitalRead returns either HIGH or LOW constants. Step 2 and 5 in the table show the condition check to decide which branch to take.

Visual Quiz - 3 Questions

Look at the execution_table, what is the pin state read at Step 2?

A LOW

B INPUT

C HIGH

D Undefined

💡 Hint

Check the 'Pin State Read' column at Step 2 in the execution_table.

At which step does the program decide to execute the LOW branch?

A Step 5

B Step 2

C Step 3

D Step 1

💡 Hint

Look at the 'Branch Taken' column where condition 'state == HIGH?' is No.

If we forget to set pinMode to INPUT, what would likely happen?

A digitalRead will always return HIGH

B digitalRead may return unpredictable values

C Pin will automatically be input

D Program will not compile

💡 Hint

Refer to key_moments about why setting pinMode is important.

Concept Snapshot

Set pin mode to INPUT before reading.
Use digitalRead(pin) to get HIGH or LOW.
Check if state == HIGH to decide action.
Without setting INPUT, readings may be wrong.
Repeat reading as needed in loop.

Full Transcript

This program starts by setting a pin as input so the microcontroller knows to listen to signals on that pin. Then it reads the pin's digital state, which can be HIGH or LOW. Based on the reading, it decides which code branch to run, for example turning an LED on or off. The execution table shows each step: setting pin mode, reading state, checking condition, and acting accordingly. Variables like pinMode and state change as the program runs. Beginners often wonder why setting pin mode is needed and what happens if it's skipped. The quiz questions help check understanding of pin state reading and decision making.