Code organization with functions in Arduino - Step-by-Step Execution

Concept Flow - Code organization with functions

Start

↓

Define function

↓

Setup function runs once

↓

Loop function runs repeatedly

↓

Call function inside loop

↓

Function executes code block

↓

Return to loop

↓

Loop function runs repeatedly

The program starts by defining functions, then runs setup once, then repeatedly runs loop, calling functions inside loop to organize code.

Execution Sample

Arduino

void blinkLED() {
  digitalWrite(LED_BUILTIN, HIGH);
  delay(500);
  digitalWrite(LED_BUILTIN, LOW);
  delay(500);
}

void setup() {
  pinMode(LED_BUILTIN, OUTPUT);
}

void loop() {
  blinkLED();
}

This code defines a function to blink the LED, sets the LED pin mode once, then repeatedly calls the blink function to blink the LED.

Execution Table

Step	Function Called	Action	Pin State	Delay(ms)
1	setup	Set LED pin as OUTPUT	LED pin mode=OUTPUT	0
2	loop	Call blinkLED()	LED LOW	0
3	blinkLED	digitalWrite HIGH	LED ON	0
4	blinkLED	delay(500)	LED ON	500
5	blinkLED	digitalWrite LOW	LED OFF	500
6	blinkLED	delay(500)	LED OFF	1000
7	loop	Call blinkLED() again	LED OFF	1000
8	blinkLED	digitalWrite HIGH	LED ON	1000
9	blinkLED	delay(500)	LED ON	1500
10	blinkLED	digitalWrite LOW	LED OFF	1500
11	blinkLED	delay(500)	LED OFF	2000
...	loop continues	...	...	...

💡 Loop runs forever, repeatedly calling blinkLED to blink LED on and off.

Variable Tracker

Variable	Start	After setup	After blinkLED 1	After blinkLED 2	...final
LED_BUILTIN state	LOW	Configured OUTPUT	HIGH then LOW	HIGH then LOW	Repeating HIGH/LOW

Key Moments - 3 Insights

Why do we define blinkLED() before using it in loop()?

Arduino requires functions to be defined before they are called, so the compiler knows what blinkLED() means when loop() calls it (see execution_table step 2).

Does setup() run multiple times?

No, setup() runs only once at the start to initialize things like pin modes (see execution_table step 1). Loop() runs repeatedly.

What happens if we put the blink code directly inside loop() instead of a function?

The code would work the same, but using a function like blinkLED() keeps code organized and easier to read or reuse (see execution_table steps 2-6).

Visual Quiz - 3 Questions

Look at the execution_table, what is the LED pin state right after step 3?

A LED is ON (HIGH)

B LED is OFF (LOW)

C LED pin mode is set

D LED is blinking

💡 Hint

Check step 3 in execution_table where digitalWrite HIGH is called.

At which step does the program first wait for 500 milliseconds?

A Step 2

B Step 4

C Step 5

D Step 6

💡 Hint

Look for delay(500) in execution_table rows.

If we remove the blinkLED() function and put its code directly in loop(), what changes in the execution_table?

A Delay will be removed

B Pin State will never change

C Function Called column will show 'loop' only

D Setup will run multiple times

💡 Hint

Without blinkLED(), loop() contains all code, so only loop() is called.

Concept Snapshot

Functions organize code into reusable blocks.
Define functions before calling them.
setup() runs once; loop() runs repeatedly.
Call functions inside loop() to keep code clean.
Use digitalWrite and delay inside functions for actions.

Full Transcript

This example shows how Arduino code uses functions to organize tasks. First, a function blinkLED() is defined to turn the LED on and off with delays. The setup() function runs once to set the LED pin as output. Then the loop() function runs forever, calling blinkLED() each time to blink the LED. The execution table traces each step: setup configures the pin, loop calls blinkLED, which changes the LED state and waits. Variables track the LED pin state changing from LOW to HIGH and back. Key moments clarify why functions must be defined before use, that setup runs once, and how functions help keep code organized. The quiz checks understanding of LED states, timing, and function calls. This method helps beginners see how code flows and how functions improve readability and reuse.