NTAG I2C: The NFC Tag That Talks to a Microcontroller

What it is

NTAG I2C is a connected NFC tag: a chip that behaves like an ordinary NFC Forum Type 2 Tag when a phone taps it, but also exposes a second, wired I2C bus to that same memory. That's what separates it from a passive tag like NTAG213 or NTAG215 — see how those fit into the wider NFC Forum Tag Types. With NTAG I2C, a microcontroller on the other end of the I2C bus can read what the phone just wrote, write something back before the next tap, and wake up the moment a phone's field shows up.

The original NTAG I2C is discontinued. NXP now points new designs to NTAG I2C plus, which is backward compatible with an extended feature set. That's the chip most projects should be buying today.

How it actually works

One chip, two interfaces, shared memory

The RF side works like any Type 2 Tag — a phone taps it, reads or writes NDEF records, and moves on. The I2C side runs in parallel, up to 400 kHz, and a microcontroller wired to it sees the same EEPROM the phone just touched. Neither side needs to know the other exists.

SRAM pass-through and the field-detect pin

A separate 64-byte SRAM buffer handles the fast, frequent traffic. In pass-through mode, data written over NFC lands directly in SRAM and shows up on the I2C bus immediately, and vice versa, at up to 40 kbit/s — roughly 10x faster than EEPROM, with none of EEPROM's 500,000-write-cycle ceiling. A field-detect pin goes active the instant an RF field appears, typically wired straight to a microcontroller's wake pin, so the MCU can sleep until a phone actually taps it. EEPROM capacity itself follows the same rules as any other NTAG chip.

Energy harvesting

NFC runs on inductive coupling at 13.56 MHz — the reader's magnetic field is what powers a passive tag in the first place. NTAG I2C plus taps that same field and harvests up to 15 mW, routing it out to an external microcontroller or sensor. A brief, low-draw task can run entirely off a phone tap. No battery required.

Where you'll see it

The clearest example is smart-home bring-up: tap a phone, and a sleeping microcontroller wakes up, reads a small configuration payload, and joins a network or triggers a routine. You can see the same pattern with simpler passive tags in NFC smart home triggers. Sensor pairing and one-time device setup follow the same shape — instead of a companion app doing Bluetooth discovery, a single tap hands the microcontroller exactly what it needs.

That's a different feature from tamper-sensing chips like NTAG 424 DNA, which proves a tag hasn't been swapped rather than bridging to a microcontroller. Both are "the tag does more than store text," just pointed in different directions. To be clear on scope: this is for hardware you build and own, not for interacting with tags — access badges, transit cards, payment cards — that belong to someone else.

Tips, gotchas, and a quick how-to with NFCore

Route frequent small messages through SRAM pass-through rather than EEPROM. It's faster and it doesn't wear out. Save EEPROM writes for values that change rarely, like a device ID or a one-time pairing key. If the tag will sit somewhere physically accessible, set the chip's 32-bit password so a stranger with an NFC reader can't casually read or overwrite it.

During development, NFCore reads NTAG I2C's UID and NDEF content the same way it reads any other Type 2 Tag — a quick way to confirm what actually landed in memory before you start debugging the I2C wiring.

Frequently Asked Questions

What's the difference between NTAG I2C and a regular NFC tag like NTAG215?

A regular tag like NTAG215 is passive memory only. NTAG I2C adds a second, wired I2C interface to that same memory (plus a small SRAM buffer), so a microcontroller can read and write it too, and wake up the moment a phone's field appears.

Do I need a battery to use NTAG I2C with a microcontroller?

Not necessarily. The chip harvests up to 15 mW from the phone's field and can power a small external circuit for the duration of a tap. Anything that needs to run continuously still needs its own power supply.

Can NFCore read an NTAG I2C tag like any other NFC tag?

Yes. NTAG I2C presents itself over RF as a standard Type 2 Tag, so NFCore reads its UID and NDEF memory the same way it reads an NTAG213 or NTAG215. The I2C side only matters to the microcontroller wired to the chip.

What's SRAM pass-through mode for?

It's a fast lane that skips EEPROM entirely — up to 40 kbit/s, roughly 10x faster than EEPROM writes, with no write-cycle ceiling. High-frequency traffic between phone and microcontroller should go through SRAM, not permanent memory.

Conclusion

NTAG I2C's real trick isn't any single feature. It's that one chip presents two interfaces to the same memory, so a phone tap and a microcontroller can hand data back and forth without Bluetooth, Wi-Fi, or a companion app. As more makers wire microcontrollers directly to taps, expect more connected-tag variants built around the same idea. Open NFCore and read a few NDEF records off a passive tag first if you want to see the phone side of that relationship before wiring up the I2C bus.