ST25 NFC/RFID tags and readers

Hello, is there any additional documentation that supports this system diagram? My project will have one antenna that will be an RFID tag whereas the other antenna will be reader. Can ST25r100 support this use case? I'd like to have the ability to write to a card as well and it seems like only RFO1 and RFO2 will have the

I’m currently working on a project where I already managed to read ISO14443 tags (NTAG213) successfully.To improve the reading quality and range, I now want to switch to ISO15693 tags.However, I’ve spent more than 30 hours trying, and so far, I haven’t been able to read a single one.I know that using the RFAL (Radio Frequency Abstraction Layer) is the right approach for ISO15693, but no matter what I do, it just doesn’t work.I’ve tried several examples, libraries, and even asked AI tools for help — but I also know that AI isn’t great when it comes to low-level driver implementation.Does anyone here have experience with ISO15693 and RFAL on ESP32? Any working examples or tips would be really appreciated.

I am using ST25R3916B with differential antenna without varicaps.The antenna is configured to receive maximum signal  from the smartphone on the RFI1.There is a TFT display between the antenna and the smartphone. The smartphone reads the tag with great difficulty even when pressed against the display.The ST25R3916B reads cards in card reader mode at a distance of about 2 cm from the display (when setting up the antenna to get the maximum signal from smartphone).Question: How can I increase the tag's reading range with my smartphone? ST25R3916B has sensitivity control registers, but there is no method for setting these parameters.Best regards.

Hi STNow I am using ST25R3916B evaluation board, it works well with the project code you provided.My final target is using 3920B on automotive for demostrating NFC card detection as well as digital car access to customer.But we will finally change to other platform's MCU, not use ST's hsot MCU.Due to our MCU has limited Fash / RAM size, we are considering to build our own middleware code to drive NFC frond end. but it looks like it's hard to understand the protocol through I2C waveform, and no any protocol document is avaiable on your website.Is migating RFAL the only way I can do for realizing NFC function with 3916B / 3920B? ThanksLeo   

I am entering the world of NFC with a somewhat complex project, but I took the initiative to start it. The goal was to create a sensor that would work only with Energy Harvesting from the reader.For this, I chose the ST25R300 chip to be the chip for my reader board and sensor power supply, mainly due to its high transmission power.I am having difficulty getting it to work properly. Basically, I ran several tests with some DEBUG codes on the reader board. In these tests, I found some inconsistencies. The first is the VDD_A voltages, which come from a reading of the chip itself, which is registering almost 6V, and the other inconsistency is the RSSI giving 0.I believe the error is in my antenna and matching circuit. I would like someone to help me improve this system by pointing out where I may have made a mistake in their design.I made the antenna using the ST website (eDesignSuite antenna design tool). I also made the maching circuit using ST's eDesignSui

I am using a custom PCB based on ST25R3911B + STM32F072C8T6, and I am encountering an issue where FeliCa cards cannot be read.Initially, I used the X-CUBE-NFC5 software package downloaded from ST’s official website, along with the integrated RFAL library (the RFAL version should be V2.0.10). With this version, I was able to correctly implement most of the required functionality, including polling cards using ISO14443 / FeliCa / ISO15693 protocols. However, after running for several hours, the reader would occasionally enter a strange freeze/hang state. Because of this, I decided to upgrade the RFAL library.I then downloaded the STSW-ST25RLIB001 package from ST and ported the RFAL library from it (RFAL version should be V4.0.0). After the upgrade, the problem changed: as soon as a FeliCa card is detected, the system freezes immediately.To isolate the issue, I discarded all my own application logic and ran only demoCycle. In the demo, ISO14443 and ISO15693 cards w

Hello everyone,I am using the X-NUCLEO-NFC10A1 NFC reader with an NXP MCU.I am able to successfully detect a MIFARE Classic 4K card using this reader.However, when I try to authenticate a sector for read/write access, I encounter an issue.I am sending the authentication command using the sequence:[ AUTH_CMD + BLOCK_ADDRESS ]After sending this command, I get a timeout error.I tried increasing the timeout value, but the issue still persists.When I manually append the CRC to the authentication command and transmit it, the reader returns a framing error.Could someone please confirm:    Is this the correct way to perform MIFARE Classic 4K authentication using the ST25R200?    If yes, what could be the reason for the timeout or framing error?If anyone has reference code, application notes, or examples related to MIFARE Classic authentication with ST25R200, please share.Thank you in

Hi,I am using the st25r3916b chip with phase awaken, wake-up timer range of 800 msec and delta 3.Once it wakes up, I go to read the value in the register 0x3A (Phase measurement display register) in order to check which is the difference between of the stored value and the one which awakes the chip.What I can see is that the value change is less than 3. How can this be?Best regards, Sandra

It is getting hang at this point, going to infinite loop MCU: STM32F407SPI1 InterfaceTried ST25R_SELFTEST as well same problem 

Hi, we use the ST25DV16KC and for development i use the ST25R3911B.   Problem is: ST25R3911B connected via micro usb to the pc.    so far looks good Pressing the TAG Editor Button   I just w

HiFrom the ST25R3919B datasheet, I cannot find or understand the voltage level of EXT_LM. Does the EXT_LM voltage level depend on the VDD supply?”BR

Hi I am evaluating NFC function on your STEVAL 25R3916B board, but I would like to see how it works with the I2C interface. Currently, the default configuration is SPI.I have downloaded STM32CubeIDE and STEVAL-25R3916B_V2.1.0 project code, but am not sure where should I put this definition "RFAL_USE_I2C", could you help me check where this macro needs to be placed?Thanks Leo

Dear  STMicroelectronics TeamI am currently developing a wearable board (WB) that integrates NFC communication and wireless charging features. For this design, I am considering using the ST25DV64KC as the NFC Dynamic Tag and the ST25R3916B as the NFC Reader/Transmitter.I work for a design company based in Colombia, with mass production planned in China and Taiwan. I have reviewed the document AN5918, which appears to be focused on NFC-based wireless charging designs.I would like to request kindly:Access to the full AN5918 application note, andDetailed guidelines or parameters for implementing the DC r

Questions about the Transparent mode.The ST25R200 is cheaper then discrete components for a non-standard RFID interface ( at 848 KHz subcarrier )Questions about the transparent mode:I am struggling with the receiver in this mode.( An example with signal values from an oscilloscope, to just send a command and get the response would be enough.I assume the reponse being 10% modulation from the tag using the 848KHz subcarrier, for 102Kb/s standard bitrate. )Could someone give an indication about the signals coming out of the transparant mode.Is there a document?Just showing the TX being used to 'send a command' and the response on the receive channel would be really helpfulIn the picture in the datasheet, the receiver does have a 848KHz ( fs/16 ) receiver, followed by a dual ADC.( Is this a real ADC or just a comparator ? )( I and Q , I assume what is their sample rate ? 848 Khz, are these one bitter ? See questions fur

Hello, I have a problem after updating the system to Android 16. Before, everything was great. I have a custom application to work with ST25DV04KC. Now, the NFC service crashes before connection, and the system app opens NDEEF. Only on the first "tap," after turning NFC on/off, the connection is correct. Is there any workaround before they change it in Android? Thanks for any help.

Hi Team,I am working with the STEVAL-D25R16B kit and have encountered a critical discrepancy in detection range between the embedded "Reader/Writer" demonstration and the PC-based USB mode.Here are the test results using ISO15693 tags:The Setup:Tag A: Placed at 2 cm (Near)Tag B: Placed at 10 cm (Far)1. Testing in USB Mode (PC GUI):Result: SUCCESS.The reader successfully detects both Tag A (2cm) and Tag B (10cm).2. Testing in Standalone "Reader/Writer" Demo:Result: FAILURE.The reader detects Tag A, but fails to detect Tag B at 10cm.Tag B is only detected if moved closer to 5 cm.

HelloI want to emulate NTAG215, but I don't think the CE corresponding to T2t is in RFAL. I'm not sure if I understand it correctly, but,First of all, the status of my code is as follows.FreeRTOS-based ListenerCylce pollingEmulate nfc contextUID, SAK, ATQA are read, but RFAL_NFC_STATE_ACTIVATED does not seem to receive T2t commands from the reader without a single turnIf necessary, I will upload a portion of the code I am working on.Help me!

I'm attempting MIFARE communication using the ST25R3916 microcontroller, but the NT does not return during the AUTH communication. I successfully obtained the UID, and after tag selection, the SAK returned as 0x08. However, after sending 06, 01, the CRC error in the 0x1C register is set. The NT should then return from the tag, but not a single byte is returned.The AUTH sequence is described below.DIRECT_COMMAND_SEND(0xDB); //Clear FIFOREG_WRITE(0x22,0b00000000); //TX BYTE Number(MSB)REG_WRITE(0x23,0b00010000); //TX BYTE Number(LSB)BSS=0; //SS=0__delay_us(10);SPI_send(0b10000000); //FIFO write commandSPI_send(0x60); //FIFO data1SPI_send(0x01); //FIFO data2BSS=1; //SS=1__delay_us(10);DIRECT_COM(0xC4); //FIFO Transmit With CRCAfter this, a CRC error occurs, and NT doesn't return a single byte.Does anyone know why?  

Hello @all, I've downloaded ST25DVCryptoDemo for iOS from here, in order to take a look into the demo code for a new project.Once I've tried to build the Demo app I've got a big amount of errors. In fact the console gave me this message "too many errors emitted, stopping now"Could someone please help me to fix those issues and make everything works properly?I've also download the ST25SD

Hello,I am using the ST25R3916B reader on a custom board to read NFC-A cards. I first experimented on the X-Nucleo-nfc08a1 expansion board connected to esp32-s3 devkit. I modified the RFAL library a bit to fit my needs and kept most registers at their default values. With this setup I was able to communicate with an NFC-A card perfectly.On my custom board, which is powered by 3V, I am able to communicate with the reader: read IC ID, read/write registers, receive interrupts. But I still haven't been able to communicate with the card. I receive no ATQA for my REQA. In fact no rxs or rxe interrupts are being raised (txe interrupt is being raised after sending direct command Send REQA). Code used on X-nucleo-nfc08a1 and custom board are exactly the same, except they have different SDA and IRQ pins.I am still checking out the hardware design to check for any issues, especially with the antenna matching circuit. In the mean time I wanted to check a few other thin

To realize carkey function, what conditions do card readers need and what aspects of hardware will be measured?

Hello everyone,I just received the STEVAL-25R200A evaluation kit and I have a few doubts.1. Can I connect this board directly to another MCU?2. If yes, are the SPI pins available on the PCB?3. I found that the board uses an STM32G0B1KEU. Should I develop and test the firmware for this MCU using STM32CubeIDE first, and then later port it to my custom board?Thank you! 

Hi,The ST25DV supports I2C speeds upto 1MHz, for which the datasheet has mentioned the rise and fall time using the RC time constant of <150ns according to I2C standards.We are using it at 100kHz only but there is no mention of rise and fall time for 100kHz ( acc to I2C standard it should be <1000ns), and the following point is mentioned in datasheet as attached.Does this mean that ST25DV supports only <150ns rise and fall time even if it used only at 100kHz? 

I am using ST25DV04KC tag and using the V_EH pin to power the VCC of the tag only( It will generate around 3.3V which is enough to power up the tag in I2C mode I believe) . I am looking for guidance on the maximum pullup voltage on the I2C and GPO line from an external rail of around 3.6V, if it is okay? what can be the max voltage on the I2C and GPO pins? is it independent of VCC or dependent on VCC?

 Hi,I need to write the same kind of NDEF data to ~20 different NFC stickers placed on a panel. The idea is to have ~20 small antennas, select one at a time, and write to the sticker sitting above that antenna.Questions:Can I do this with X-NUCLEO-NFC12A1 + STM32 by multiplexing the RF path (switches/decoder → select 1-of-20 antennas)?Any recommended switch/multiplexer parts or reference designs for 13.56 MHz?What are the practical limits on antenna count and cable/trace length when switching like this?Do I need individual tuning (matching caps) per antenna position?Is there a better Nucleo shield for this use-case (e.g., higher RF drive) or is NFC12A1 enough?Goal: operator chooses pad 1…20, we write an NDEF, verify, then move to the next pad.Kindly advise—exampl