• I2C
  • Beginner
  • 6 min
  • Serial CLI or Web Serial Terminal

Recipe · Beginner · I2C

How to identify an unknown I2C device

A scan tells you which addresses acknowledge. Identification is the next step: compare address hints, run discovery, confirm ACK, then choose the safest first read.

I2C bus with SDA and SCL signal lines.
Treat the address as a clue, not a full device identity.

Wiring View

Unknown I2C device BP I2C Device SDAI2C SDA GPIODevice SCLI2C SCL GPIODevice VCCCorrect supplyDevice GNDBP GND
Generated from the wiring summary: Unknown I2C device to BP I2C.
Step 1

Commands

Start by configuring SDA, SCL and bus frequency. Then scan for ACK, ask for extended discovery, use the address mapper, and confirm the specific address with ping.

Result

What it means

You have a confirmed 7-bit I2C address and a short list of likely device families. That is enough to decide whether a register read, EEPROM shell or module-specific workflow is appropriate.

Troubleshooting

  • If scan finds nothing, return to wiring, pull-ups, voltage and SDA/SCL order before trying register reads.
  • If several devices share the bus, identify each ACK address separately.
  • Do not assume an address is unique; many unrelated chips use the same common ranges.
  • Avoid broad dumps until you know the target is a memory-like device or a safe read-only register map.

Next steps

  • Use read <addr> <reg> only after finding a safe register from a datasheet or known module family.
  • Use the eeprom [addr] shell for 24XX/AT24C-style EEPROMs instead of raw dumps.
  • Use I2C health diagnostics when ACK is intermittent or the bus looks unstable.

Unknown I2C device FAQ

Does identify prove the exact chip model?

No. identify maps common addresses and likely device families. The exact chip still depends on markings, module layout, datasheet behavior or safe register responses.

Why use discovery after scan?

scan answers the basic ACK question. discovery adds more context, which is useful when several devices acknowledge or when the address alone is too common.

What is the safest first read after identification?

Prefer a documented ID, status or version register from the suspected device family. Avoid writes and full dumps until you know the target register map and side effects.

Go deeper