Pin and I2C tester for ESP32 and Arduino

A test firmware exercises every pin: output, input, pull-ups. The site shows burnt and shorted pins and finds modules on I2C.

Connect the board over USB

First disconnect everything that could be damaged by switching the pins on: motors, relays, modules, LEDs without a resistor. The tester switches every pin on in turn.

The tester runs on ESP32, ESP32-C3, ESP32-S3, ESP32-C5, ESP8266 (NodeMCU, Wemos D1 mini), Arduino Uno and Nano. If the board has other firmware, the site offers to flash the tester.

How the tester checks a board

The tester works with the olerast tester check firmware for ESP32, ESP32-C3, S3, C5, ESP8266, Arduino Uno and Nano, and talks to it over the serial port at 115200 baud. The firmware reads every pin with the pull-up on and with the pull-down on. If a pin follows the pulls, it switches the pin to output, drives 1 and 0 and reads the level back from the pin. Then it looks for shorts: one pin outputs 0 and 1 while the others listen.

A pin that the pulls can't move stays an input: it may be shorted to ground or to power. The firmware does not touch the flash, PSRAM, USB and communication port pins. The I2C scanner polls addresses 0x08-0x77 at 100 kHz. On the Uno and Nano the tester shows the chip's supply voltage, measured against the internal 1.1 V reference (the ATmega328P datasheet gives 1.0 to 1.2 V).

Examples

  • If GPIO25 and GPIO26 are bridged by a blob of solder, the tester marks both as "shorted": when one outputs 0, the other reads 0 too.
  • The scanner on a Nano found 0x27, 0x57 and 0x68. That is the PCF8574 adapter of an LCD1602 display, the EEPROM on a clock module and the DS3231 clock itself (or an MPU6050, which has the same address).

Common mistakes

  • People test a board with motors, relays and LEDs without a resistor still connected. The tester switches the outputs on one by one, and the load fires.
  • People swap SDA and SCL or forget to power the module. The scanner reports "Nobody answered".

FAQ

How do I check that an Arduino Nano works?
Connect the Nano and click "Connect". If the board doesn't have the tester on it, the site offers to flash it, and the flasher shows the ATmega328P chip and the bootloader. A reply like that shows that the USB adapter, the chip and the bootloader work. After flashing, "Check all pins" tests D2-D13 and A0-A5 and looks for shorts. A6 and A7 can only be read through the ADC.
What can I check on a Nano with a multimeter, without flashing anything?
When powered from USB, the 5V pin relative to GND will read a bit under 5 V: in the Arduino Nano schematic the USB power goes through an MBR0520 Schottky diode. The 3V3 pin gives about 3.3 V, supplied by the USB-UART chip. On an unpowered board, a resistance close to zero between 5V and GND means a short.
What are the I2C addresses of a 1602 display, an OLED and common sensors?
An LCD1602 with a PCF8574T adapter answers at 0x27, with a PCF8574AT at 0x3F. An OLED on an SSD1306 or SH1106 answers at 0x3C, or at 0x3D after you move the address resistor. The MPU6050 and DS3231 are at 0x68 (an MPU6050 with AD0 tied to power is at 0x69), the BME280 at 0x76 or 0x77 depending on the SDO pin, and the PCA9685 at 0x40 and at the all-call address 0x70.
How do I tell a burnt pin from a boot pin?
The tester calls a pin burnt when its output, once switched on, doesn't hold 1 or 0 on the pin. A boot pin, or a pin with an LED (on the DOIT DevKit V1 that is D2), reads 0 or 1 under the pull because of a resistor on the board. The tester adds a note and doesn't switch its output on. Flash, USB and communication port pins are marked "not touched".
Why doesn't the scanner see my I2C module?
Check the module's power, the common ground and the wires: SDA to SDA, SCL to SCL. On the Uno and Nano the bus is only on A4 (SDA) and A5 (SCL), on an ESP the pins are chosen in the tester. If a line is pulled to ground, the tester says so and doesn't start the scan. Modules usually have 4.7-10 kΩ pull-ups already, a bare chip needs its own resistors to 3.3 V.
What is left on the board after the check?
The tester firmware stays on the board, written over your program. When you disconnect, the tester sets the pins to input without pulls. Flash your own program back from the Arduino IDE or with the flasher.

You might also need