PINTEST(1)

πŸ“¦
version 2.0.1 Β· 2 versions
, in ubuntu noble, ubuntu questing

πŸ’– PINTEST(1) πŸ’–

okay so bestie, welcome to pintest β€” the gpiozero pintest tool. it's a whole utility for testing the GPIO pins on a Raspberry Pi, inspired by pigpio's gpiotest example script and wiringPi's pintest utility. ✨


🌸 SYNOPSIS 🌸

     pintest [-h] [--version] [-p PINS] [-s SKIP] [-y] [-r REVISION]

πŸ¦‹ DESCRIPTION πŸ¦‹

so this is a utility for testing the function of GPIOs on a Raspberry Pi. and like. real talk: you can genuinely damage the GPIOs on a Pi by passing too much current through them (or too much voltage, in the case of inputs). so the pintest utility is here to help you figure out whether any of the GPIOs on your Pi are broken. 🫢

by default it tests all the physically exposed GPIOs β€” like, the ones on the main GPIO header β€” but maybe you only wanna test a subset, or you wanna exclude certain GPIOs? totally valid. that's what the pintest --pins or pintest --skip options are for. πŸ’…

NOTE: you must make sure that nothing is connected to the GPIOs you intend to test. no cap. by default, the utility will prompt you before proceeding, and it repeats this warning at you. πŸ™ˆ

if any GPIO turns out to be faulty, it gets reported in the output and the utility exits with a return code of 1. and if all the specified GPIOs test fine? return code is zero. slay. πŸ‘‘


✨ OPTIONS ✨

  • -h, --help β€” show this help message and exit πŸ’–
  • --version β€” Show the program's version number and exit
  • -p PINS, --pins PINS β€” the pin(s) to test. you can give it a comma-separated list of pins. pin numbers can be in any form that gpiozero accepts, e.g. 14, GPIO14, BOARD8. the default is to test all pins ⭐
  • -s SKIP, --skip SKIP β€” the pin(s) to skip testing. also takes a comma-separated list of pins. again, pin numbers can be in any form accepted by gpiozero, e.g. 14, GPIO14, BOARD8. the default is to skip no pins 🚫
  • -y, --yes β€” proceed without prompting. (no vibe check, we just go πŸƒβ™€οΈ)
  • -r REVISION, --revision REVISION β€” force board revision. the default is to autodetect the revision of the current device. > heads up bestie: you should avoid this option unless you are very sure the detection is incorrect. like, very sure. πŸ‘€

🌈 EXAMPLES 🌈

test all the physically exposed GPIOs on the board:

$ pintest

test just the I2C GPIOs, without prompting:

$ pintest --pins 2,3 --yes

exclude the SPI GPIOs from testing:

$ pintest --exclude GPIO7,GPIO8,GPIO9,GPIO10,GPIO11

and remember β€” pin numbers can be given in any form accepted by GPIO Zero, e.g. 14, GPIO14, or BOARD8. iykyk πŸ’«


πŸŽ€ SEE ALSO πŸŽ€

pinout(1), gpiozero-env(7)


πŸ’œ AUTHOR πŸ’œ

Ben Nuttall


2015-2024 Ben Nuttall


okay that's the whole page, bestie, you're officially a GPIO diagnostician πŸ’…βœ¨ this was version 2.0.1 from Feb 15, 2024, brought to you by gpiozero β€” mwah, go test those pins, love u, bye 🫢🌸

πŸ“¦ where this page comes from