ST25 NFC/RFID tags and readers

Hello!We are using ST25R3916B in our new NFC-based access control product. We use NFC-A and T4 communication for Mifare Classic, Desfire cards, and Android NFC apps. The STSW-ST25RFAL002 with the following configuration seems to be using around 8KB of additional RAM.  Is there any chance of reducing memory needs?  #define RFAL_FEATURE_LISTEN_MODE true /*!< Enable/Disable RFAL support for Listen Mode */ #define RFAL_FEATURE_WAKEUP_MODE false /*!< Enable/Disable RFAL support for the Wake-Up mode */ #define RFAL_FEATURE_LOWPOWER_MODE false /*!< Enable/Disable RFAL support for the Low Power mode */ #define RFAL_FEATURE_NFCA true /*!< Enable/Disable RFAL support for NFC-A (ISO14443A) */ #define RFAL_FEATURE_NFCB false /*!< Enable/Disable RFAL support for NFC-B (ISO14443B) */ #define RFAL_FEATURE_NFCF false /*!< Enable/Disable RFAL support for NFC-F (FeliCa) */ #define RFAL_FEATURE_NFCV false /*!< Enable/Disable RFAL support for NFC-V (ISO15693)

 I am porting the ST25R3911B NFC module library to work with the Quectel EC200U 4G module in the Helios SDK. While I have successfully achieved rfalNfcInitialize and rfalFieldOnAndStartGT, I am facing issues when running the NFC-A polling code. The execution gets stuck inside the while loop mentioned in the callback of the ISR.Observed Behavior:The module sometimes gets stuck in the ISR loop, with the interrupt pin remaining high even when no NFC-A card is near.Occasionally, instead of getting stuck, it throws RFAL_ERR_IO.In rare cases, it does not throw any error but gets stuck as soon as an NFC-A card is brought near.ST25R_SELFTEST_TIMER and ST25R_SELFTEST pass without any errors.Polling Code: while (1) { rfalNfcWorker(); MYLOG("Checking NFC \n"); err = rfalFieldOff(); /* Turn the Field Off */ if(err != RFAL_ERR_NONE){ MYLOG("Error in rfalFieldOff: %d\n", err); } platformDelay(500); err = rfalNfcaPollerInitialize(); /* Initialize RFAL for NFC-A */ if(err != RFAL_E

Hello,I am using the Nucleo-STM32F411RE development board and X-NUCLEO-NFC08A1 NFC module, particularly NFC Tag read/write from Android Phone for my development use cases.To achieve this, I downloaded the X-CUBE-NFC6 package as it was mentioned in the product brief. However, I could not find any example projects specifically for the STM32F4 series.I also attempted to modify examples from other STM32 series, but I encountered faults and was unable to successfully run the code.Could anyone provide a working example for the STM32F4 series, or share a step-by-step user guide? As I am new to STM32 MCU boards, this has been quite time-consuming, and any guidance would be greatly appreciated.Thank you for your help!Best regards,Akash M

Hello!I am using ST25R3916 (X-NUCLEO-NFC06A1) and RFAL Library V3.0.1. When working with STM32L4RGT3 (NUCLEO-L476RG) everything works fine, but if I use STM32L053R8 (NUCLEO-L053R8) functions rfalNfcaPollerFullCollisionResolution() and rfalISO14443ATransceiveAnticollisionFrame() regardless of MCU frequency and stack size settings all the time return RFAL_ERR_FRAMING error.What could be the reason for this behavior depending on the MCU?STM32L053R8 (NUCLEO-L053R8) together with ST25R3911 (X-NUCLEO-NFC05A1) works fine, but when connected to ST25R3916 (X-NUCLEO-NFC06A1) it gives this error..Best regards, Rob.

Is there an alternative to platformTimer functions? I started with 6 timers and am currently at 32, Somehow eventually it uses up all the timers and stops working. It seems like the timers are not destroyed when the NFC is deactivated.Below is my application, Please suggest to me if there is a better way to implement thisEnvironment:MCU: PSOC6RTOS: FreeRTOSTransceiver: ST25R3916BCommunication: SPITimers: Timers are using FreeRTOS timers.My application at a high level:Wait for the trigger to start NFC discovery scansOn trigger, Poweron and Initialize ST25R3916B -  rfalNfcInitializStart NFC discovery scan for ~1sec - rfalNfcDiscoverif anything is discovered communicate using T4 commands - rfalNfcIsDevActivated, rfalNfcDataExchangeStartwait for 100msecStop discovery and deinitialize - rfalNfcDeactivate, rfalDeinitializerepeat these steps 5 timesPower off ST25R3916BGo back to sleep to wait for next triggerMy current implementation is based

I've been reading through the Wake-Up Mode and Automatic Antenna Tuning application notes, and while I understand that AAT and Wake-Up with inductive sensing require more involved software wake-up logic, it doesn't seem to me that capacitive sensing would. For inductive sensing with AAT, the AAT outputs are left floating during Power Down Mode, so upon wake-up, they need time to settle for an accurate measurement.But the capacitive wake-up is a separate mechanism that has nothing to do with AAT or the NFC antenna. Is there any reason that AAT + capacitive wake-up wouldn't work together?edit: this is for the ST25R3916, with custom firmware

I have two Nucleo boards, both NUCLEO-L476RG. The first board is equipped with the X-NUCLEO-NFC08A1 (ST25R3916B), while the second board has the NFC 5 Click board (ST25R3918).I am trying to establish peer-to-peer (P2P) communication between these boards, with the ST25R3916B configured as the initiator and the ST25R3918 as the target.Both boards successfully detect NFC tags, confirming that the basic hardware setup is functioning correctly. However, I have not been able to achieve P2P communication.Any guidance or assistance in resolving this issue would be greatly appreciated. I have attached the initiator and target codes for reference. 

I want to trigger a RFID reading at certain intervals using ST25R3911 and from this I want a RFID reading to be done within 1 second. When I try this in RFAL (using democode for polling): err = rfalNfcDiscover( &discParam ); if( err != RFAL_ERR_NONE ) { printf("Err %d!\n\r", (int)err); return false; } state = DEMO_ST_START_DISCOVERY;   It takes about 10 second to do a RFID reading which is way too long. When analyzing what RFAL is doing this is what I see when checking gNfcDev.state in rfalNfcWorker: void rfalNfcWorker( void ) { ReturnCode err; rfalWorker(); /* Execute RFAL process */ printf("State %d\n\r", (int)gNfcDev.state); switch( gNfcDev.state ) {   RFAL_NFC_STATE_POLL_TECHDETECT - about 5 secondsRFAL_NFC_STATE_POLL_COLAVOIDANCE - about 4 seconds Which is obvisously too long for a user to hold an RFID card in front of the reader. What is RFAL doing and how can I reduce time from request reading to reading done within

I have PCB which support 3.3 V or 4 V power supply which I want to connect with ST25R3911B. I want to run 4V power supply as it can provide more current and I assume outputpower of ST25R3911B  will be higher on 4 V than on 3.3 V.In data sheet of ST25R3911B  it is stated that power supply is 2.4 to 5.5V so this should be fine. BUT when checking the registers 4.0V seems to be an invalid voltage: IO configuration register 2Bit 7 - sup3 V0: 5 V supply1: 3.3 V supply 5 V supply, range: 4.1 V to 5.5 V3.3 V supply, range: 2.4 V to 3.6 Vmin. 3.0 V for VHBR So the question is what will happen when using 4.0V for 5V supply range? Will it not work at all?Also when running PCB on battery voltage this will give voltage bewteen 4.0 to 3.0 V, which seems to be outside specification of ST25R3911B.Can someone help how to use use ST25R3911B in my application? 

In my design VDD = 2.9V and VDD_IO = 2.0V.  To minimize current when the NFC feature is not needed, I want to power down the VDD supply.  But I want to leave VDD_IO powered on.  Is there a concern with VDD being powered up and down repeatedly while VDD_IO is always on?

hi,st25r200 read configuration of  st25tv02k tag via  rfalST25xVPollerReadConfiguration()  ,but always fail. Error code is 05.However, st25r200 can read and write user data block of the  tag correctly.Could anyone give me an example of using this function? Thanks a lot.   zh

Hello,I am currently working as a student on designing my own hardware for reading and writing NFC tags. Although I lack experience in RF design, I have completed the electronic design and antenna matching process. My setup includes an STM32U575RGTx microcontroller connected to an ST25R3916B NFC chip via SPI. The antenna, sourced from Taoglas, is connected to the matching circuit, and I have confirmed the RF field using a spectrum analyzer.This project does not utilize the STM HAL; instead, I am working in bare metal. I have developed a HAL for SPI communication, which is functioning without errors. Additionally, I have ported the RFAL library to my project to facilitate interaction with the NFC chip.At present, I have two types of tags for testing: NFC-A T2T and NFC-V tags. I have enabled the necessary configuration in rfal_platform.h and implemented the example from the X-NUCLEO-NFC08A1 to attempt reading the tags.However, I am encountering issues. When I try to read the NF

Hello,I'm designing a battery powered device with integrated payment terminal. The goal is to pass EMV Level 1 certification.Our approach is very bare metal. We design the board, circuitry and firmware from scratch. No HAL or RFAL is being used. Our own proprietary C++ library for ST MCUs is.For the past few weeks I've struggled with antenna matching so that Analogue Tests for Radio Frequency Power TAB111 pass on all three EMVCo Test PICCs. That's ok now and I believe my system has a proper antenna shape, impedance and Q so that the signal shape is correct.But I'm facing issues with demodulation. In certain conditions an IRQ due to start of receive doesn't occur. Namely when Negative modulation is transmitted by PICC. Or when TEST PICC with High Linear Load is used for testing.When no load is applied, the result of Measure Amplitude is 2.74 V, which is very close to recommended 2.8 V on RFI inputs. The voltage divider appears to be chosen correctly. Even with high load, the Voltage hov

I'm trying to change from ST25DV16K board to ST25DV64KC and use it.The board setup part seems to be fine, but there's a problem with the interrupt setup part.When writing data to the EEPROM of the tag board with RF from NFC08A1, the code that worked on 16K doesn't work on 64KC. What's the problem?This is my code.int nfc_gpo_it_init(){    int ret = 0;    ST25DV_PASSWD passwd = {.MsbPasswd = 0, .LsbPasswd=0};      if (ST25DV_PresentI2CPassword(&NfcTagObj, passwd) < 0)    {        printf("Error Point1\n");        return -1;    }    ret = Nfctag_Drv->ConfigIT(&NfcTagObj, ST25DV_GPO_ENABLE_MASK | ST25DV_GPO_RFWRITE_MASK);    if(ret != 0)    {        printf("error\n\r");    }    passwd.MsbPasswd = 123;    passwd.LsbPasswd = 123;    if (ST25DV_PresentI2CPassword(&NfcTagObj, passwd) < 0)&nbs

Hello,I am working on a project where I need to read the UID of an NFC tag using the ST25R3916 and communicate via I2C. After powering on, I can successfully read single register, but after setting the device to "Ready mode" by setting bit 7 of the Operation Control Register (0x02), I only read zeros, even when attempting to read the FIFO.

I'm working with the STEVAL-25R200SAand trying to implement Transparent Mode to directly receive raw data from the MISO line. I've followed the datasheet and configured everything as per the documentation, but I'm still not receiving any data.Setup and Code Implementations:In my main() function, the while loop calls these functions repeatedly:while (1) { serCycle(); enterTransparencyMode(); readTransparentMode(); HAL_Delay(1000); }I start by calling enterTransparencyMode() which ensures the transmitter and receiver are enabled, configures the AFE, sends the command to enter Transparent Mode, and raises the BSS (CS) line to keep it high as required by the datasheet:void enterTransparencyMode(void) { printf("Setting up device for transparency mode\r\n"); // Read initial state uint8_t regValue, statusReg; st25r200ReadRegister(ST25R200_OPERATION_REGISTER, &regValue); st25r200ReadRegister(ST25R200_STATUS_REGISTER, &statusReg); printf("Initial state - Operation: 0x%02X, St

This seems like an "easy" topic, yet I'm struggling to get a clear understanding.Section 3.2 of the datasheet (Operating Conditions) defines a single, wide range for VDD (2.4V to 5.5V).  But Section 1.3.2 (IO Configuration Register 2) defines two non-contiguous VDD range (either 2.4V to 3.6V or 4.1V to 5.5V).  Does this indicate that VDD between 3.6V and 4.1V is not supported?Based on Section 3.2, we did a HW design where VDD is powered from a battery (3.3V to 4.2V) and we have an issue where sometimes the Adjust Regulator command fails to complete (no interrupt received within 10ms).  And wondering if we are violating the supported VDD range.I've also dug through RFAL001 and it looks like it sets sup3_V to 5V if VDD > 3.6V.  This also indicates the VDD range from 3.6V to 4.1V is not supported because (in 5V mode) the minimum VSP_RF is 3.9V and VDD has to be about 0.25V higher.

Hi Community,We are currently developing an NFC reader for our access control system that needs to read NFC passes stored in Google Wallet and Apple Wallet. The system should: Read emulated NFC tags from both Android and iOS devices Extract the NDEF payload from these wallet passes Convert the payload to Wiegand format (can be done externally if the NFC reader doesn't come with an MCU on-board) Send the Wiegand data to our relay board for access verification I'm looking for NFC reader hardware and development boards that can support this functionality, specifically the ability to read Apple VAS and Google SmartTap protocols. Most standard NFC readers don't seem to support these proprietary wallet protocols.  Has anyone worked on a similar project or can suggest compatible hardware or development strategies? Any insights on obtaining necessary certifications or implementing these protocols would be greatly appreciated. PS: I have looked at a few posts like this, and this, and thi

We are considering transferring power along with NFC communication using the ST25R3916 chip.From one of the application notes, we found the following block diagram, as shown in the image below. According to the diagram, the power amplifier is placed in cascade with the matching circuit.Could you please point us to relevant documents to help us design a power amplifier according to our requirements? 

Hi,About rfalST25xVPollerFastReadMultipleBlocks and rfalNfcvPollerReadMultipleBlocks。I use st25r3916 to read NFCV tag.The farthest reading distance of my reader can reach 70mm.When I use the command RFALNFCVPoller Read Multipleblocks, I can successfully read data between 0-70mm, but when I use RFAL ST25XVPoller FastTreadmill Blocks, when the amount is between 55 mm and 70 mm, I will fail to read, and the returned error codes are mainly 04, 09 and 21. There is no problem with tag. I can read it with other competing products in this position. How can I determine what the problem is, the software configuration problem? Or is there not enough energy after the RF field is far away?Do you need any other configuration to use fast reading?I hope you can help me answer it. Thank you.

Hello everyone,As a students at a company do I try to build a tool or method to evaluate some parameters of NFC coils (Q and L). I have been given some NFC tags to proof the correct functionality later. One of those tags is the "ANT7-T-ST25DV04K" with a 14 mm x 14 mm, 13.56 MHz dual layer etched antenna.My problem is, I could not find any values for the quality factor (Q-factor) and the inductance L for this NFC coil.So, I would like to ask if anyone knows the Q-factor and/or the inductance L of this coil.Otherwise, if you know these parameters of an other NFC tag, it would help, too. Kind regards,STSD20 PS. Of course I have already looked in the product datasheet.

Hello!Is there any additional information about on how to use on ST25R3916 the bypass mode of internal VDD_RF regulator to be able to a transmitter output current higher than 350 mA (up to 500 mA) supplied from an external source.In ST25R3916 datasheet only gives this information:"If a transmitter output current higher than 350 mArms is required the VDD_RF regulator cannot be used to supply the transmitter. VDD_RF and VDD_DR have to be externally connected to VDD_TX (connection of VDD_RF to supply voltage higher than VDD_TX is not allowed)."Also i see in the ST25R3916 Discovery Board (MB1414B) schematic open jumper J206 and unplaced decoupling capacitors C209, C210.What are my steps to enable VDD_RF regulator bypass mode? Only close jumper J206 and placed capacitors C209, C210? Is there anything also that needs to be done?Best regards, Rob.

I want to use my ST25DV with both I2C and RF interfaces. There is no clear arbitrage between the 2,  but the first is served. Moreover, I tested that while I2C is operating in reading and writing bytes in a for loop, the RF can corrupt the data in some way making the I2C lose data, or answer busy. I tried to switch off the RF using the dynamic command RF_MNGT_Dyn at address 2003h setting RF_SLEEP =1, while I2C is writing or reading. But the data result was corrupted again. this is my code simplified: Turn EEPROM on;sleep RF;wait RF OFF time;Write 64 bytes with I2C;Read 64 bytes with I2C;Calculate CRC and identify if byte written are equal to written; 

Hi ST Community,I'm developing an NFC reader for a payment interface and require recommendations for suitable STMicroelectronics chips that are compliant with EMV Level 1 and preferably Level 2Regards 

We've had issue with reading NTAG215 cards with some devices, presumably due to the large spread-out antenna, so I'm working on a better understanding of the power output so that we can properly calibrate devices out of manufacturing.Currently, I do not have any RFO resistors enabled, so Tx power should be at its maximum. The datasheet says that the maximum allowed voltage level on an RFI is 3 Vpp, but on devices functioning optimally, I see up to 3.2 Vpp from the output of a Measure Amplitude command, particularly when an NTAG215 card is in the device's field. Does this signify that something in hardware or firmware is implemented incorrectly? Should I be setting the RFO resistance so that > 3 Vpp is never seen on an RFI pin? Does it matter at all? The electrical characteristics section says that in reader mode the recommended signal level is 2.5 Vpp, so should I be optimizing for that?Thanks for your help.