tone() function for frequency generation in Arduino - Time & Space Complexity

Time Complexity: tone() function for frequency generation

O(1)

Understanding Time Complexity

We want to understand how the time cost changes when using the tone() function in Arduino.

Specifically, how does the program's running time grow as we generate sounds of different lengths or frequencies?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

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

void loop() {
  tone(8, 1000, 500); // Play 1000 Hz tone for 500 ms
  delay(1000);         // Wait 1 second
}
    

This code plays a 1000 Hz sound on pin 8 for half a second, then waits for one second, repeating forever.

Identify Repeating Operations

• Primary loop: The loop() function repeats indefinitely.
• Operations per iteration: tone() call (sets up hardware timer asynchronously) and delay(1000) (fixed block).
• Key fact: tone() is non-blocking; it returns immediately after setup.

How Execution Grows With Input

Consider 'input size n' as the duration parameter in ms. The tone() call time does not depend on n.

Input Size (duration in ms)	Approx. Operations (time for tone() call)
10	Constant ~few μs setup (timer config)
100	Constant ~few μs setup (timer config)
1000	Constant ~few μs setup (timer config)

Pattern observation: Execution time for tone() is constant, independent of duration. Sound plays in background via interrupts; CPU continues immediately.

Final Time Complexity

Time Complexity per loop iteration: O(1)

Fixed operations: timer setup for tone() and fixed delay. No growth with duration n.

Common Mistake

[OK] Correct thinking: "The tone() function runs instantly no matter the duration."

[X] Why opposite is wrong: tone() does not block or toggle the pin in a loop; it configures hardware timers/interrupts for async operation.

Interview Connect

Grasping non-blocking functions like tone() is key for real-time embedded systems, where distinguishing CPU time from hardware-managed tasks matters.

Self-Check

"What if we removed the duration parameter and let tone() run indefinitely? How would the time complexity of the tone() call change?"

Hint: Still O(1); sound persists until noTone(), but call returns immediately.

Practice

1. What does the tone() function do in Arduino?

easy

A. Generates a sound of a specific frequency on a pin

B. Reads the voltage from a sensor

C. Turns on an LED

D. Sends data over serial communication

Solution

1. Step 1: Understand the purpose of tone()

   The tone() function is used to create sound by generating a square wave of a specific frequency on a pin.

2. Step 2: Compare options with function behavior

   Only Generates a sound of a specific frequency on a pin describes generating sound with frequency, which matches tone() usage.

3. Final Answer:

   Generates a sound of a specific frequency on a pin -> Option A

4. Quick Check:

   tone() = sound frequency generation [OK]

Hint: Remember: tone() makes sound, not reads or sends data [OK]

Common Mistakes:

• Confusing tone() with digitalWrite()
• Thinking tone() reads sensor data
• Assuming tone() controls LEDs

2. Which of the following is the correct syntax to play a 1000 Hz tone on pin 8 for 500 milliseconds?

easy

A. tone(8, 1000, 500);

B. tone(1000, 8, 500);

C. tone(8, 500, 1000);

D. tone(8, 1000); delay(500);

Solution

1. Step 1: Recall tone() function parameters

   The correct order is tone(pin, frequency, duration). So pin 8, frequency 1000 Hz, duration 500 ms means tone(8, 1000, 500);.

2. Step 2: Check each option

   tone(8, 1000, 500); matches the correct order. tone(1000, 8, 500); swaps pin and frequency. tone(8, 500, 1000); swaps frequency and duration. tone(8, 1000); delay(500); starts continuous tone but does not stop after 500 ms, unlike duration parameter.

3. Final Answer:

   tone(8, 1000, 500); -> Option A

4. Quick Check:

   tone(pin, freq, duration) = tone(8, 1000, 500) [OK]

Hint: Remember parameter order: pin, frequency, duration [OK]

Common Mistakes:

• Swapping frequency and pin parameters
• Confusing duration with frequency
• Omitting duration when required

3. What will be the output behavior of this Arduino code snippet?

void setup() {
  tone(9, 440, 1000);
  delay(1500);
  noTone(9);
}
void loop() {}

medium

A. Pin 9 outputs a 440 Hz tone for 1.5 seconds, then stops

B. Pin 9 outputs a 440 Hz tone continuously without stopping

C. Pin 9 outputs a 440 Hz tone for 1 second, then stops

D. No sound is produced because noTone() is called immediately

Solution

1. Step 1: Analyze tone() with duration

   The tone(9, 440, 1000); plays a 440 Hz tone on pin 9 for 1000 milliseconds (1 second).

2. Step 2: Understand delay and noTone()

   The program waits 1500 ms, which is longer than the tone duration, so the tone stops automatically after 1 second. Then noTone(9); stops any tone if still playing (safe call).

3. Final Answer:

   Pin 9 outputs a 440 Hz tone for 1 second, then stops -> Option C

4. Quick Check:

   tone(9, 440, 1000) plays 1s tone [OK]

Hint: Duration in tone() controls length; noTone() stops early [OK]

Common Mistakes:

• Thinking tone plays for delay length
• Assuming noTone() stops tone immediately before playing
• Confusing tone duration with delay time

4. Identify the error in this code snippet that tries to play a 500 Hz tone on pin 7:

void setup() {
  tone(7, 500);
  delay(3000);
  noTone(7);
}
void loop() {
  tone(7, 500, 1000);
}

medium

A. tone() requires frequency before pin number

B. Calling tone() inside loop() with duration causes overlapping tones

C. noTone() should be called before tone() in setup()

D. delay() cannot be used with tone()

Solution

1. Step 1: Review tone() usage in loop()

   Calling tone(7, 500, 1000); repeatedly in loop() will restart the tone every cycle, causing overlapping or interrupted sounds.

2. Step 2: Check other options

   noTone() can be called after tone(), tone() parameters order is correct, and delay() can be used with tone(). So only Calling tone() inside loop() with duration causes overlapping tones describes the real problem.

3. Final Answer:

   Calling tone() inside loop() with duration causes overlapping tones -> Option B

4. Quick Check:

   Repeated tone() with duration in loop causes overlap [OK]

Hint: Avoid tone() with duration inside loop() to prevent overlap [OK]

Common Mistakes:

• Calling noTone() before tone() unnecessarily
• Mixing parameter order in tone()
• Thinking delay() blocks tone() sound

5. You want to play a melody using tone() on pin 6 with these notes and durations: 262 Hz for 500 ms, 294 Hz for 500 ms, and 330 Hz for 1000 ms. Which code correctly plays this sequence without overlapping tones?

hard

A. void setup() {
tone(6, 262, 500);
delay(1000);
tone(6, 294, 500);
delay(1000);
tone(6, 330, 1000);
delay(1000);
}
void loop() {}

B. void setup() {
tone(6, 262);
delay(500);
tone(6, 294);
delay(500);
tone(6, 330);
delay(1000);
}
void loop() {}

C. void setup() {
tone(6, 262, 500);
tone(6, 294, 500);
tone(6, 330, 1000);
}
void loop() {}

D. void setup() {
tone(6, 262, 500);
delay(500);
tone(6, 294, 500);
delay(500);
tone(6, 330, 1000);
delay(1000);
}
void loop() {}

Solution

1. Step 1: Understand tone() with duration and delay

   Using tone(pin, freq, duration) plays the note for the duration. To avoid overlap, delay should match the tone duration before playing the next note.

2. Step 2: Evaluate each option

   void setup() { tone(6, 262, 500); delay(500); tone(6, 294, 500); delay(500); tone(6, 330, 1000); delay(1000); } void loop() {} plays each tone with correct duration and delays matching durations, so notes play sequentially without overlap. void setup() { tone(6, 262); delay(500); tone(6, 294); delay(500); tone(6, 330); delay(1000); } void loop() {} omits duration in tone(), causing continuous tones. void setup() { tone(6, 262, 500); tone(6, 294, 500); tone(6, 330, 1000); } void loop() {} calls tone() three times without delay, overlapping sounds. void setup() { tone(6, 262, 500); delay(1000); tone(6, 294, 500); delay(1000); tone(6, 330, 1000); delay(1000); } void loop() {} uses delays longer than tone durations, causing unwanted silence.

3. Final Answer:

   tone(6, 262, 500); delay(500); tone(6, 294, 500); delay(500); tone(6, 330, 1000); delay(1000); -> Option D

4. Quick Check:

   Match delay to tone duration for clean melody [OK]

Hint: Use delay equal to tone duration to separate notes [OK]

Common Mistakes:

• Omitting delay after tone() with duration
• Calling multiple tone() without delay causing overlap
• Using longer delays causing silence gaps