GPIO cleanup on exit in Raspberry Pi - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of calling GPIO.cleanup() in a Raspberry Pi program?

It resets all the GPIO pins used by the program back to their default state, preventing warnings or errors in future runs and avoiding unintended behavior.

beginner

When should you call GPIO.cleanup() in your Raspberry Pi script?

You should call it at the end of your program or when your program exits, including when interrupted by the user, to ensure pins are properly reset.

intermediate

How can you ensure GPIO.cleanup() runs even if the program is stopped with Ctrl+C?

Use a try-except block to catch KeyboardInterrupt and call GPIO.cleanup() in the except block or use a finally block to always run cleanup.

beginner

What happens if you don't call GPIO.cleanup() before your program exits?

GPIO pins may remain set as inputs or outputs, causing warnings on next run or unexpected hardware behavior, like LEDs staying on or motors running.

beginner

Show a simple Python code snippet that safely cleans up GPIO pins on program exit.

import RPi.GPIO as GPIO
import time

GPIO.setmode(GPIO.BCM)
GPIO.setup(18, GPIO.OUT)

try:
    GPIO.output(18, GPIO.HIGH)
    time.sleep(2)
except KeyboardInterrupt:
    pass
finally:
    GPIO.cleanup()

Why is it important to call GPIO.cleanup() in a Raspberry Pi program?

A To increase CPU usage

B To speed up the program

C To reset GPIO pins to a safe state

D To install new libraries

Calling GPIO.cleanup() resets the pins to avoid warnings and unintended behavior.

Which Python statement ensures GPIO.cleanup() runs even if the program is interrupted by Ctrl+C?

A Using a while loop

B Using a try-except block catching KeyboardInterrupt

C Using an if statement

D Using a print statement

A try-except block catching KeyboardInterrupt allows cleanup code to run on interruption.

What could happen if you forget to call GPIO.cleanup() before your program exits?

A GPIO pins may stay active causing hardware issues

B The program will run faster next time

C The Raspberry Pi will shut down

D Nothing happens

Pins may remain set, causing warnings or hardware to stay powered.

Where is the best place to put GPIO.cleanup() in your code?

A At the start of the program

B In a comment

C Inside a print statement

D In a finally block

A finally block runs no matter what, ensuring cleanup always happens.

What does GPIO.cleanup() do to the pins?

A Resets them to input mode and frees resources

B Turns them all on

C Changes their voltage to 5V

D Disables the Raspberry Pi

Cleanup resets pins to input mode and releases resources.

Explain why and how you should use GPIO.cleanup() in a Raspberry Pi program.

Think about what happens to pins after your program stops.

Describe a simple Python code structure that ensures GPIO pins are cleaned up even if the user stops the program with Ctrl+C.

Use try, except, and finally keywords.

Practice

1. Why is it important to call GPIO.cleanup() at the end of a Raspberry Pi GPIO program?

easy

A. It resets the GPIO pins to a safe state for future use.

B. It speeds up the program execution.

C. It increases the voltage output of the pins.

D. It disables the Raspberry Pi's network connection.

Solution

1. Step 1: Understand GPIO pin states

   GPIO pins can remain set as input or output after a program ends, which may cause issues.

2. Step 2: Purpose of GPIO.cleanup()

   Calling GPIO.cleanup() resets all pins to their default safe state, preventing conflicts in future programs.

3. Final Answer:

   It resets the GPIO pins to a safe state for future use. -> Option A

4. Quick Check:

   GPIO.cleanup() resets pins = B [OK]

Hint: Always reset pins with GPIO.cleanup() after use [OK]

Common Mistakes:

• Thinking cleanup speeds up code
• Believing cleanup changes voltage
• Confusing cleanup with network settings

2. Which of the following is the correct way to ensure GPIO.cleanup() runs even if your program encounters an error?

easy

A. Place GPIO.cleanup() inside a try block only.

B. Place GPIO.cleanup() inside a finally block.

C. Call GPIO.cleanup() before setting up pins.

D. Call GPIO.cleanup() only if no errors occur.

Solution

1. Step 1: Understand try-finally structure

   The finally block runs no matter what, even if errors happen.

2. Step 2: Place cleanup in finally

   Putting GPIO.cleanup() in finally ensures pins reset even on exceptions.

3. Final Answer:

   Place GPIO.cleanup() inside a finally block. -> Option B

4. Quick Check:

   Cleanup in finally = A [OK]

Hint: Use finally block to always run cleanup [OK]

Common Mistakes:

• Putting cleanup only in try block
• Calling cleanup before setup
• Skipping cleanup on errors

3. What will be the output of this code snippet if an error occurs during the loop?

import RPi.GPIO as GPIO
GPIO.setmode(GPIO.BCM)
GPIO.setup(18, GPIO.OUT)
try:
    for i in range(3):
        if i == 1:
            raise Exception('Error!')
        GPIO.output(18, GPIO.HIGH)
finally:
    GPIO.cleanup()
print('Program ended')

medium

A. Program ended

B. GPIO pins remain set high

C. No output, program hangs

D. Exception: Error!

Solution

1. Step 1: Analyze try block with error

   The loop raises an exception at i=1, but the finally block still runs.

2. Step 2: Effect of finally block

   GPIO.cleanup() runs regardless, resetting pins, but since there is no except block, the exception propagates after finally, so print('Program ended') does not execute. The output is the exception message.

3. Final Answer:

   Exception: Error! -> Option D

4. Quick Check:

   finally runs cleanup, exception prints = B [OK]

Hint: finally block runs even on errors [OK]

Common Mistakes:

• Thinking 'Program ended' prints on error
• Thinking pins stay set after error
• Ignoring finally block execution

4. Identify the error in this code that prevents GPIO pins from being cleaned up properly:

import RPi.GPIO as GPIO
GPIO.setmode(GPIO.BCM)
GPIO.setup(17, GPIO.OUT)
try:
    GPIO.output(17, GPIO.HIGH)
except:
    print('Error occurred')
finally:
    GPIO.cleanup()

medium

A. Missing parentheses after GPIO.cleanup in finally block.

B. GPIO.setup should be called after GPIO.cleanup.

C. GPIO.output should be inside except block.

D. No try-except block needed for GPIO.

Solution

1. Step 1: Check finally block syntax

   The code uses GPIO.cleanup without parentheses, so cleanup is not called.

2. Step 2: Effect of missing parentheses

   Without parentheses, cleanup is a reference, not a function call, so pins are not reset.

3. Final Answer:

   Missing parentheses after GPIO.cleanup in finally block. -> Option A

4. Quick Check:

   Call cleanup with () = D [OK]

Hint: Always add () to call GPIO.cleanup() [OK]

Common Mistakes:

• Forgetting parentheses on cleanup
• Calling setup after cleanup
• Misplacing GPIO.output inside except

5. You wrote a program controlling multiple GPIO pins with different modes. How should you structure your code to ensure all pins reset properly even if your program crashes unexpectedly?

hard

A. Use GPIO.cleanup() inside except block only.

B. Call GPIO.cleanup() only at the very start of the program.

C. Place all GPIO setup and output calls inside a try block, and call GPIO.cleanup() in a finally block.

D. Do not use GPIO.cleanup() to avoid resetting pins.

Solution

1. Step 1: Organize GPIO code with try-finally

   Put all GPIO setup and control inside try to catch errors and ensure cleanup.

2. Step 2: Use finally block for cleanup

   Call GPIO.cleanup() in finally so it runs no matter what, resetting all pins safely.

3. Final Answer:

   Place all GPIO setup and output calls inside a try block, and call GPIO.cleanup() in a finally block. -> Option C

4. Quick Check:

   try-finally with cleanup = C [OK]

Hint: Use try-finally to guarantee cleanup on exit [OK]

Common Mistakes:

• Calling cleanup only at start
• Skipping cleanup on errors
• Avoiding cleanup to keep pins set