ST25 NFC/RFID tags and readers

Hi, I am running ST25R100 on a different processor and coding it at the register level. With the codes I shared below, I was able to run the chip in wakeup mode as I wanted and ensure that an interrupt occurs when the card is approached. However, I could not succeed in the second stage, which is reading the card. How can I do it, which registers should I write to, please help

Hello friendsI am looking for an implementation for RFAL listening modeDoes anyone have a sample code to send me?

Hello,Despite the mandatory `rfalWorker()` hell> "It MUST be executed frequently in order to execute the RFAL internal states and perform the requested operations"... the RFAL is very interesting to have a flexible way to communicate with the ST25R family - current and future (my opinion only :')) Especially for the amount of standards it helps to follow. But, please, can you consider to make it usable not only for a single chip? It use a lots of unique global variables (gNfcDev, gNfcip, gNfca, etc...), use same timers, communication bus, etc...All of that make it unusable to control multiple chips, a shame when we now have multi cores ARM :(

Hi everyone,I'm working on a low-cost, batteryless NFC-based sensor node and would appreciate your input.My goal is to measure an analog signal using a basic op-amp + ADC circuit (e.g., voltage, temperature), digitize the signal via I²C-compatible ADC, and store or transmit the data using an ST25DV64KC dynamic NFC tag. The NFC reader (e.g., smartphone) should power the system via the tag’s energy harvesting output (V_EH) and read the data wirelessly.To minimize cost and complexity, I would like to avoid using a microcontroller. So the intended setup would include:analog frontend (op-amp),I²C-based ADC,ST25DV64KC.In addition, I would like the same system to read a second passive NFC tag, such as an ST25TV02KC, to get its UID or basic data.My key questions:Is it feasible to build this system without a microcontroller, using only ADC + ST25DV64KC?Since both ST25DV and most ADCs are I²C slaves, is there any way to operate them without an I²C master?Would a microcontroller still be required

Hello,i'm using arduino to code a STM32C011J6M6 and I want to use the Energy harvesting pin of ST25DV04K to source the IC when the VCC be off and the NFC Field be on.But with this code the EH is on just when VCC and NFC Field are on.if I remove all the EH_MODE code part, the circuit continues to works, so i believe that I'm coding this wrong. Someone already works with this kind of programming?Best Regards #include <Wire.h> #define LED PC13 #define SCL_PIN PB6 #define SDA_PIN PB7 #define TILT PA13 #define ST25DV64K_ADDR 0x53 int memAddr = 0; int counter = 0; #define PTR_EH_MODE 0x0002 #define PTR_EH_CTRL_DYN 0x2002 void setup() { pinMode(LED, OUTPUT); pinMode(TILT, INPUT); Wire.begin(); configureEnergyHarvesting(); } void loop() { digitalWrite(LED, HIGH); delay(500); uint8_t tiltCount = countTiltEvents(); writeEEPROM(memAddr++, 5); writeEEPROM(memAddr++, (uint8_t)26); writeEEPROM(memAddr++, 52); writeEEPROM(memAddr, (uint8_

Hello everyone, I'm exploring the possibility of using NFC technology to operate and read data from a sensor equipped with an I2C ADC (Analog-Digital Converter). Specifically, I'm interested in leveraging an antenna cable or a smartphone as part of my main system setup. Here's the scenario I have in mind: I want to utilize NFC functionality to communicate with the sensor. The sensor incorporates an I2C ADC for digital data output. Ideally, I would like to use either an antenna cable or a smartphone to facilitate this NFC communication. System Diagram:[Main System] - [Antenna Cable/Smartphone (AAT)] - [NFC Reader] - [I2C] - [ADC] My questions are: Has anyone here successfully implemented a similar setup using NFC to communicate with an I2C ADC-equipped sensor? What specific NFC reader ICs or modules would you recommend for this application? Are there any particular challenges or considerations I should be aware of, especially regarding antenna cables or smartphone integrat

Hello,I'm developing a system based on a ST25DVxxKC (tag side) and a ST25R3916B (reader side) and I need to use the FTM feature. This is what I'm currently testing:- The reader detects the tag. (That part works fine.)- When detected, the reader sends a message to the tag using FTM. (That part also works fine, at least no RFAL error.)- The tag detects it (I set up GPO wtih RF_PUT_MSG_EN and  RF_GET_MSG_EN), the flag in IT_STS is RF_PUT_MSG as expected.- The tag then reads the message length (MB_LEN_Dyn register) via I2C. The length is correct, it's the exact length of the message sent by the reader (in my case, 152 bytes).- The tag then reads the mailbox buffer @address 0x2008. Successful, no NACK.- But the content I read is NOT the data sent by the reader, but the first NDEF record that is stored into the tag's EEPROM (followed by zeroes). This could be due to a bug on my side, but I don't explicitely read any EEPROM user data in this test, neith

Hi ST membersI am using the ST25R95, following the application note and matching tool to define LC components for EMC filter and matching circuit. the function test is good, but I have a high pulse at 3rd harmonics 40.8MHz and 7th 94.92MHz, do you have similar case happens with emission issue? have any suggestion？ thanks！

 Hello ST Community,I'm currently trying to implement a simple function: turning the RF field ON and OFF for a desired duration using the X-NUCLEO-NFC08A1 board.Here is my current setup and progress:I’m using the STM32F401RE Nucleo board as the host MCU.I've referred to UM3007 (Getting Started with X-NUCLEO-NFC08A1) and “Getting started with the X-CUBE-NFC6” documents.I have installed the required X-CUBE-NFC6 software pack in STM32CubeIDE.SPI1 is configured as per the documentation in .ioc .However, after code generation, no SPI-related code is generated (e.g., no MX_SPI1_Init() function).In the .ioc file's System View, the Middleware section shows nothing loaded — I suspect this may be part of the issue.Overall, it feels like the NFC board is not properly interfacing with the MCU, but I can’t identify what’s wrong.Additionally, my goal is only to generate the 13.56 MHz RF field with desired strength and timing — no tag detection or NDEF handling is needed. From the datasheet, I u

Hello ST Community,I found this forum and the example code to our custom hardware very helpful and are successfully reading both NFC-A/NFC-V and emulating NFC-A on ST25R3918.During testing, I've noticed that NFC-V tags with NDEF messages can also trigger background reads on both iOS and Android. Since NFC-V have longer ranges, would it be better to do CE using this format? At the moment the code is using demoT4T to respond to readers in NFC-A CE (RFAL_NFC_LISTEN_TECH_A) in the rfalNfcDiscoverParam.do { rfalNfcWorker(); switch( rfalNfcGetState() ) { case RFAL_NFC_STATE_ACTIVATED: transceiveBlocking( NULL, 0, &rxData, &rcvLen, &err, 0, false); break; case RFAL_NFC_STATE_DATAEXCHANGE: case RFAL_NFC_STATE_DATAEXCHANGE_DONE: txLen = demoCeT4T( rxData, *rcvLen, txBuf, sizeof(txBuf)); transceiveBlocking( txBuf, txLen, &rxData, &rcvLen, &err, RFAL_FWT_NONE, false ); break; case RFAL_NFC_STATE_START_DISCOVERY: return; case RFAL_NFC_ST

 Hi everyone,I'm working on writing the configuration password (PWD_CFG, 0x00) to an ST25TV02KC NFC tag using the ST25R3916B reader and the RFAL middleware (X-CUBE-NFC6). I am following the standard procedure:Open a CONFIG security session using PresentPassword (XORed Password)Generate a new XOR-coded password using GetRandomNumberCall WritePassword to write a new password (in this case, still 0x00..0x00 for testing)Here's the code I use:   if (generateXorPassword(uid, pwd_cfg, xorPwd) != RFAL_ERR_NONE) goto ERROR_RED_LED; if (rfalST25xVPollerPresentPassword( // 0x00 = PWD_CFG RFAL_NFCV_REQ_FLAG_DEFAULT | RFAL_NFCV_REQ_FLAG_ADDRESS, uid, 0x00, // PWD_CFG xorPwd, sizeof(xorPwd) ) != RFAL_ERR_NONE) { goto ERROR_RED_LED; } // CONFIG Security Session is now open! { // Change PWD_CFG (0x00) if (generateXorPassword(uid, pwd_cfg, xorPwd) != RFAL_ERR_NONE) goto ERROR_RED_LED; if(rfalST25xVPollerWritePassword( RFAL_NFCV_REQ_FLAG_DEFAULT | RFAL_NFCV_REQ_FLAG

Hello, I have x nucleo 09a1 and I managed to run it in wake up mode with a different processor than stm and register. But there is a high current in wake up mode and power down mode. I am sharing the relevant graphics and code, please help.

Hi everyone, I’m trying to split an ST25TV02KC NFC-V tag into two memory areas using the RFAL (RF Abstraction Layer) library:1. Area 1 (blocks 0 … END_A1) should be public (read/write without password)2. Area 2 (blocks END_A1+1 … max) should be protected by the CONFIG passwordMy overall approach:1. Enable Multi-AreaRead block 0x0A (the LCK_CONFIG register) Set bit 0 in byte 1 to enable multi-area2. Open CONFIG Security SessionGET_RANDOM_NUMBER (opcode 0xB4) with 1-byte manufacturer code (0x02)PRESENT_PASSWORD (opcode 0xB3) with [IC-code, PWDID, encrypted 4-byte challenge]3. WriteConfiguration for END_A1FID=0x00, PID=0x01, DATA=END_A14. Verify with READ_CONFIGURATION (opcode 0xA0)5. Write user data into Area 1 (public) or Area 2 (protected)Despite following the ST25TV02KC datasheet, every time I issue the WRITE_CONFIGURATION command for setting END_A1, RFAL returns a timeout (RFAL_ERR_TIMEOUT, code 4). Questions:1. Am I missing any preliminary command or flag before WRITE

Hi everyone,I’m currently working with ST25TV02KC NFC tags and the ST25R3916B reader, using the RFAL library.I’m trying to access the configuration registers via the following functions:rfalST25xVPollerReadConfiguration(...)rfalST25xVPollerWriteConfiguration(...) I’ve already opened the CONFIG security session successfully using PresentPassword with PWD_CFG, so write access should be allowed.What I’m trying to do:Read and write configuration registers like:RW_PROTECTION_A1 → FID: 0x00, PID: 0x00END_A1 → FID: 0x00, PID: 0x01According to the datasheet (Table 4), these are valid config registers in group FID 0x00. Here is how I call the read function:uint8_t regVal = 0;ReturnCode err = rfalST25xVPollerReadConfiguration(RFAL_NFCV_REQ_FLAG_DEFAULT, uid, 0x01, &regVal); // PID = 0x01 for END_A1 And the write function:uint8_t newVal = 0x20; // Example: change END_A1 to enable dual-area modeReturnCode err = rfalST25xVPollerWriteConfiguration(RFAL_NFCV_REQ_FLAG_DEFAULT, uid,

Hi everyone,I'm working with the ST25TV02KC NFC tag (NFC Forum Type 5) and using the ST25R3916B as my custom reader (on a PCB). I’d like to be able to read from and write to the tag using my reader, but also allow partial access via smartphone (e.g. Android phone using NFC).Here’s what I want to achieve:Some fields should be read-only on the phone.Some fields should be readable and writable.Some data should be completely hidden from the phone but accessible to the ST25R3916B reader.Example layout:ReadOnly: Min_Value, Max_ValueReadAndWrite: Calibration_Zero, Calibration_SpanMy questions:How can I configure the tag's memory to enforce this kind of access control?Is it possible to hide certain memory areas entirely from a smartphone (but still access them from my own reader)?Are there tools or example configurations (e.g. NDEF files, memory layout examples) for this?Any advice, example code, or documentation links would be greatly appreciated!Thanks in advance!

 Hello,Tag reading was working perfectly on my previous setup.I now want to migrate my project from an STM32G0B1RE to an STM32L073RZ. Since the Arduino UNO R3 physical pinout standard is respected, the X-NUCLEO-NFC08A1 shield (which uses SPI, IRQ, LEDs, etc.) remains pin-compatible across different STM32 Nucleo boards (G0, L0, L4, etc.), as long as they follow the UNO R3 layout.So, I created a new project in STM32CubeMX targeting the STM32L073RZ, and reused the configuration from my working G0-based project.Current status:Initially, execution would stop inside `demoCycle()`, initialization was successful (I could see `Initialization succeeded` in the UART), but no tags could be read.After fixing the IRQ setup, execution no longer reaches `demoCycle()`, it now stops at the call to `MX_X_CUBE_NFC6_Init()`.Any idea what could be preventing `rfalNfcInitialize()` from completing correctly on the STM32L073RZ?Thanks in advance!

HelloI’m currently designing an NFC product using the ST25R3911B reader IC and evaluating two standard NFC antennas from Leankon for read distance performance:LK1860701 (larger size)LK1860601 (smaller size)Test Setup & Observations:Matching Circuit Optimization:Used datasheet parameters to optimize the matching network for both antennas.Followed the recommended test methodology from the datasheet.Test Tag:Evaluated performance using ST’s Tag 5 as the reference target.Results:Both antennas achieved a similar read distance of ~80mm.However, according to Leankon’s datasheet, the LK1860701 should achieve ~100mm.Questions:Is this discrepancy normal? Could there be variations due to environmental factors or matching circuit tuning?Are there any key considerations I might have missed to further improve the read distance? For reference, two antenna datasheets are attached,LK1860101 NFC antenna  LK1860701 NFC Antenna &nbs

Hello, I am currently working on initializing ST25R3916B (X-NUCLEO-NFC08A1) with Nucleo-H563ZI microcontroller, using the Zephyr RTOS and the zephyr-st25r driver. My primary goal is to successfully initialize the ST25R3916B chip to a state where it can respond to basic SPI commands and eventually perform NFC operations. I am encountering an issue during the initialization phase where the STM32 appears to be correctly sending write and read commands via SPI, but the MISO line consistently reads 0X00 , indicating that the ST25R3916B is not responding or not driving the MISO line with expected data. Hardware Setup: This is the content my overlay file:  / {chosen {zephyr,spi-st25r3916 = &st25r3916_nfc;};}; &spi1 { pinctrl-0 = <&spi1_sck_pa5 &spi1_miso_pg9 &spi1_mosi_pb5>; pinctrl-names = "default"; status = "okay"; st25r3916_nfc: st25r3916@0 { compatible = "st,st25r"; reg = <0>; spi-max-frequency = <4000000>; irq-gpios = <&gpiog 1

I want to use ST25R100 directly with register settings without a library. How can I start it in wake up mode? When I try the code I gave below, the Interrupt pin comes to a fixed 3.3V and does not change.void st25r100_WakeUp_Init(void) { // 0. Wake-up ve reader disable → reset mantığı st25r100_write_register(0x00, 0x00); // EN=0, WU_EN=0 nrf_delay_ms(10); // Donanım beklesin // 1. Her ihtimale karşı IRQ flag temizle st25r100_read_register(0x3E); // Temizle // 2. Wake-Up kontrol: auto-ref aktif, IRQ her seferde st25r100_write_register(0x28, 0x0F); // b00001111 // 3. Auto-ref ayarları → yavaş güncellenen, stabil st25r100_write_register(0x29, 0x3A); // iq_aaw = 11 (32), td = 010 (~34 µs) // 4. Eşik değeri: yüksek (farkı zor algılasın) st25r100_write_register(0x2B, 0x20); // i_diff = 32 // 5. Wake-up periyodu: orta (~100 ms) st25r100_write_register(0x2A, 0x05); // td_mt=010, wut=101 // 6. Sadece wake-up IRQ açık st25r100_write_register(0x3B, 0xFD); // mask_wut = 0, diğerleri maskeli

Hi,I have some noise on the Vdd pin of the ST25R3911B.I send the fieldon() command and there is a huge noise at 27MHz frequency on the Vdd (8) pin.Below is a screenshot of the refdesign disco Vdd pin with the fieldon and the noise observed on my board (same base time). There is a huge difference between them. It is a problem for me because when the tag is at field limit, I have rfal error (err 9) and this error is not present on the demokit. I think it comes from this noise.There are 100nF and 10uF decoupling caps on the Vdd. Here is the routing of the readerIt seems that the reader generates noise at the crystal oscillator frequency. What can I do to reduce this noise? Any idea?Best Regards

Hi,I would like to know if it is possible to use another oscillator source other than a crystal for the ST25R300?I saw another post for the ST25R3911B, Is it possible to use a Clock Oscillator instead of Quartz crystal oscillator?, although obviously this is not the same chip I would like to use.On the ST25R300 I do see there is a test register I can access, but I don't see any details on using an external oscillator.Would a similar setup be possible for this chip?Thank you, Kaitlyn

Hello,      I am working with X-CUBE-NFC6 example and I am able to read and write data to a rfid tag successfully.     Just as a note, hw configuration is nucleo U083RC boards with NFC08A1 expander board for rfid reader.     I would like to be able to read 2 or 3 tags at the same time but checking the demoCycle() function  code in the app_x-cube-nfcx.c I am not sure it's possible , I would have to discard a tag once it's read so it's not detected again and others tags are read ? Thanks,     Mihai     

Hi There, I am developing a product where I need to remotely wake up my electronics from 0.5-1.5 m, and also read back some user information about the unit I just woke up (e.g. serial number, firmware version the MCU is running etc). It needs to be as low power draw as possible while asleep. I was thinking that RFID could be a good candidate for this, with an IC that can harvest RF energy to output a signal (gpio or just output voltage/current based on harvested energy) that I can use to wake my MCU. It can also send back user data to the scanner such as firmware version and serial data. Given my range, I was thikning that UHF is the most appropriate (correct me if I am wrong here). Does STM have any products that suit my needs? I was looking at the STM25DV04KC, however being in the HF range, I am concerned I will not get the range that I require. If it could, what size of antenna would I require to get 0.5-1.5m wake range? If it cant, do you have any other recommen

Hello, I am planning on implementing a ST25R3916 circuit starting from X-NUCLEO-NFC08A1 schematic, but LXRW0YV600-054 is marked EOL for 2026. Is there any recommendation for change of the implementation?  Thank you! Best regards, Dragos

Hello!I'm completely lost in my search for a solution.Question description: The 25R3916 in 14443A emulation mode. When sending data to the reader with a length of up to 255 bytes, everything works perfectly. However, if I need to send data longer than that (e.g., a response to an APDU read record request 00B2041400), which is 3 bytes longer (including the successful APDU response [x90_x00]), things start to get complicated.What should the EMD suppression configuration register be set to, and what is the algorithm for sending the data?