NFC-EMULATE-FORUM-TAG2(1)

📦 version 1.8.0, in alpine 3.24, arch rolling, debian bookworm, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

✨ NFC-EMULATE-FORUM-TAG2(1) ✨

okay bestie, pull up a chair 💅 this is nfc-emulate-forum-tag2, section 1 of the manual pages, and it's about to be your whole personality for the next five minutes.

🌸 NAME 🌸

nfc-emulate-forum-tag2 — the NFC Forum tag type 2 emulation command line demonstration tool. say it with me: demonstration. tool. iconic. 👑

🦋 SYNOPSIS 🦋

nfc-emulate-forum-tag2

that's it. no flags, no arguments, no drama. she just runs. 💖

🎀 DESCRIPTION 🎀

So nfc-emulate-forum-tag2 is a demo tool that emulates an NFC-Forum Tag Type 2 — and it's got NDEF content on it, so it's not just a vibe, it's a functional vibe. ✨

Some devices that are compliant with NFC-Forum Tag Type 2 can be used with this example, but heads up: read mode only. that's the whole range of motion, bestie. 🙈

💀 IMPORTANT 💀

ngl this is the part where you need to listen to me. This example was developed using PN533 USB hardware as the target and a Google Nexus S phone as the initiator. that's the canon setup. 🫶

It is known to NOT work with the Nokia 6212 Classic, and it could fail with several NFC Forum compliant devices — and here's exactly why, no cap:

  • The emulated target has only a 4-byte UID, while most devices assume a Tag Type 2 always has a 7-byte UID (like a real Mifare Ultralight tag). so they look at her and go "ma'am, where's the rest of you" 😭
  • The chip is emulating an ISO/IEC 14443-3 tag, with no hardware helper at all. So if the initiator has too strict timeouts for software-based emulation — which is usually the case, fr fr — this example will fail. This is not a bug and we literally can't do anything about it using this hardware (PN531/PN533). the hardware said what it said. 💀

ACR122 devices (like touchatag, etc.) can be used by this example, but if something goes wrong, you will have to unplug/replug your device. and no, this is not a libnfc's bug — this problem is due to ACR122's internal MCU sitting in front of the NFC chip (PN532). not her fault, not our fault, it's the MCU's fault. 🙈

seriously though — that unplug/replug thing is real, don't come for libnfc about it 💅

🐛 BUGS 🐛

Please report any bugs on the libnfc issue tracker at:

https://github.com/nfc-tools/libnfc/issues

go off, tell them everything, they want to hear it. 🫶

📜 LICENCE 📜

libnfc is licensed under the GNU Lesser General Public License (LGPL), version 3.

libnfc-utils and libnfc-examples are covered by the BSD 2-Clause license.

👑 AUTHORS 👑

  • Roel Verdult <roel@libnfc.org>
  • Romain Tartière <romain@libnfc.org>
  • Romuald Conty <romuald@libnfc.org>

This manual page was written by Romuald Conty. It is licensed under the terms of the GNU GPL (version 2 or later).

🌈 ok that's the whole page, bestie 🌈

this one's dated September 19, 2012, and it lives in section 1 of the manual as NFC-EMULATE-FORUM-TAG2(1) — so if you ever need to find her again, you know exactly where she's at. mwah. 💖🎀✨

📦 where this page comes from