ST25 NFC/RFID tags and readers

Hello,I have purchased the "STEVAL-25R200SA – Discovery Kit for the ST25R200 high-performance NFC device" and attempted to run the sample application STSW-ST25R020 (Firmware for STEVAL-25R200 kit) available on the portal.I was able to build and flash the code successfully; however, the reader is unable to detect the tag when it is presented. Additionally, I do not see any output (Even with USE_LOGGER=LOGGER_ON) on the Tera Term terminal.Interestingly, when I use the same firmware along with the ST25R200 Eval GUI PC application, the reader appears to wake up, detect tags, and return to sleep mode as expected but no output on the Tera Term terminal.Could anyone assist me in identifying the issue and provide guidance on how to resolve it? Thanks & Regards,Tanuj

The AN5322 specifies the Murata LXRW series as the voltage-controlled capacitor. Murata's capacitor is EOL. What alternatives are there?

Hello,     I am trying to work with a st25r3918 rfid(should be very similar to st25r3916 and the st25r3916 driver should cover its functionality as I have understood).    I am trying to validate the interrupts(mainly the nfc for tag reading but for the moment a wake-up timer would be enough)    I have set GPIO2 on arduino uno board as INT pin as I have read that only GPIOs 2 and 3 can be set for hardware irqs     And I've found this code snippet in arduino st25r3916 lib to validate irq handling: /** Check IRQ Handling:* - use the Wake-up timer to trigger an IRQ* - wait the Wake-up timer interrupt* - return ERR_TIMEOUT when the Wake-up timer interrupt is not received*/st25r3916WriteRegister(ST25R3916_REG_WUP_TIMER_CONTROL, ST25R3916_REG_WUP_TIMER_CONTROL_wur | ST25R3916_REG_WUP_TIMER_CONTROL_wto);st25r3916EnableInterrupts(ST25R3916_IRQ_MASK_WT);st25r3916ExecuteCommand(ST25R3916_CMD_START_WUP_TIMER);if (st25r3916WaitForInterrupt

Hi,I’m exploring the ​ST25 NFC Reader for a ​bio-tracking application that requires ​fast tag read speeds and reliable ​multi-tag detection. However, I couldn’t find detailed specifications in the datasheet regarding these aspects.I’ve also purchased the ​STEVAL-ST25R200SA kit, but its provided GUI doesn’t seem to support tag read speed evaluation. Could you help clarify:​Tag Read Speed:What is the approximate ​read speed (tags/second) for the ST25 series (e.g., ST25R3916B)?Is there a document (e.g., application note or performance report) that quantifies this?​Evaluation Tools:Are there other ​ST evaluation boards (e.g., X-NUCLEO-NFC08A1) that include tools to measure read speed?​Multi-Tag Considerations:When multiple tags are present in the ​ROI (e.g., 5 tags), what factors should I consider?For example, could ​tag-to-tag coupling cause interference?Context:Tags: Small ​ISO/IEC 15693 glass tubes (2mm × 12mm).Thanks in advance for your insights!

Hello,I would like to develop a system using the NFC chip ST25R200 and the microcontroller STM32F303. The main idea is to be able to read an NFC tag, specifically the ST25DV64KC.As a first step, I plan to test this using the prototyping board NUCLEO-F303 and the NFC expansion board X-NUCLEO-NFC10A1. I'm using CubeIDE.I'm sure that ST has prepared everything for a simple and smooth integration. Because of that, I'm confused about what I'm doing wrong.After configuring the pins and integrating the middleware/software in STM32CubeMX, I get errors when I try to compile the code (I haven't changed anything in the generated code). Here is picture with Pins defined:here is Middleware/software package included and set:  SPI1, Interrupt, GPIO configure:   After generating code I go to main.c where I want to compile generated code and get a lot of errors:Can you please help me understand what I'm doing wrong?In the past, I worked with the ST25R3912, so I have some e

Hello,      I am trying to work with ST25R3918 part.    I have followed the suggestion here: Solved: ST25R3918 - STMicroelectronics Community for firmware and example usage.    The board itself is a NUCLEO-WL55JC1. I have tried both I2C and SPI communication but I cannot even read chip id reg(0x3F). According to the datasheet Datasheet - ST25R3918 - Multi-purpose NFC transceiver SPI/I2C should work even if the rfid is not in power wake up mode so reading the chip id register should be possible. ST32CubeIDE examples also seem to do the ID reading before any other configuration.   I don't receive anything on SPI/I2C when reading that reg.    I would like to know if somebody which is familiar ST25R3918 is aware of any additional register configuration before being able to retrieve the chip id reg.  Thanks,      Mihai 

Hello all, I am trying to write a new password in untraceable mode (tried in all modes) of my ST25TV02KC tag. I have downloaded the x-cube-nfc5 file and using the tagdetect example for STM32L476 board. After running the below code, the newly written password is not getting the accepted. Even the old password is also not working. Am I doing the process in the intended way? Reader : ST25R3911B-DISCO MB1325-C  

Hello everyone,I have the B-L475E-IOT01A2 board equipped with the M24SR64-Y, connected on the I2C2 bus. I managed to write URI, SMS, and email records, and even successfully wrote NDEF text via a mobile application. However, I haven't been able to write NDEF text via I2C.Is there any guide or example available that could help me resolve this issue?Thanks in advance for your help!

Hello,Murata has announced that the variable capacitors LXRW0YV201-059 will become obsolete in 2026.https://www.mouser.com/PCN/Murata_PCN_for_Mouser_(LXRW)_Mar._6_2025.pdfThese components are part of the antenna matching/EMI filter circuit in the STEVAL-ST25R3916B schematics.Do you have any recommendation for an alternative reference to replace these capacitors once they become obsolete ?Thanks in advance,Best regards

Hi,I'm using an ST25DV64KC tag to communicate with an Android app using the st25 sdk and the Mailbox. The problem arises when the app reads a message of the maximum mailbox capacity. In that case, an 0xE4 character appears as the last character but I'm pretty sure the firmware didn't put it. Here is an example of an interaction2025-05-12 08:32:09.466 12263-19515 Iso15693CustomCommand   com.wavecontrol.mtiotmobileapp       D  ==> Send readMsgLength command: 22 ab 02 7f 46 b6 7c 67 51 02 e02025-05-12 08:32:09.480 12263-19515 Iso15693CustomCommand   com.wavecontrol.mtiotmobileapp       D  Response: 00 ff2025-05-12 08:32:09.483 12263-19515 Iso15693CustomCommand   com.wavecontrol.mtiotmobileapp       D  ==> Send readMsg command: 22 ac 02 7f 46 b6 7c 67 51 02 e0 00 ff2025-05-12 08:32:09.588 12263-19515 Iso15693CustomCommand   com.wavecontrol.mtiotmobileapp       D  Response: 00 02 7b 22

I have connected the STEVAL-25R200SA via micro-USB to the computer however the device is not identified.  Is there any virtual com port driver needed for this and if so can someone provide what it is that I am missing.  

Dear..STI'm developing custom NFC PCB 4 layers 0.8mm based on 20x20mm main antenna example in STEVAL-25R200SA kit.I tried to use the components in BOM for EMC filter L 0402DF-421XJRW 420nH 510mOhm and adjust frequency to18MHz  and get EMC capacitor 186pF which is similar to the kit (180pF) I follow AN6065 as much as I understand.However I don't know the Antenna parameters, Q value, of the kit, so the matching L, C, R seems not the same as the kit. So if you have these parameters, or smith chart of the main 20x20mm antenna, please share to me.My application need very low power and the distance of the ST25DV64 tag and the reader is very close (5-10mm).I will try to tune antenna for lowest current consumption so that the reader still read the tag.Please advise Target Q, and Target matching Z, I should use with 20x20mm antenna. The supply for the ST25R200 is 3.3V(I read AN13219 from NXP as well, page 22 noted that Target Z 16 Ohm for 5V, 11 Ohm for 3.3V so I guess to reduce Targe

Hi.I'm porting the RFAL for NFC10A1 using ST25NFC_Embedded_Lib_ST25R200_1.7.0.I'm using the polling example. I have ported SPI, GPIO, and timer drivers based on my platform. I am using demo_polling.c as a basic template for my init and while loop functions and handlers.I have successfully initialized NFC10A1 board, but I end up in an infinite loop in the RFAL_TXRX_STATE_TX_WAIT_TXE state.The issue is that the ISR value read from NFC10A1 is 0 during this state. I have enabled RFAL_FEATURE_NFCA and ST25R_POLL_IRQ inside preprocessor. I have added various debug logs trying to figure out what make the system stuck. The log is attached as a zip.I tired looking at it with a logic analyzer (CH4 being the ISR pin) and discovered that despite ISR pin being pulled high, there was no proper reading of the ISR registers on NFC10A1 (which can be seen as no new SPI transmission occurred afterwards). I'm not sure why this is happening because ISR is clearly being read during system ini

When evaluating the st25R3916b chip using the X-NUCLEO-NFC08A1 development board, we found that the current reached about 100-150ma during the nfc reading and writing process. However, we did not find the standard value for this part of the current in the manual. May I ask if there are any official typical current values for this chip or development board during nfc reading and writing for our reference? What is the minimum current that this chip can achieve when reading and writing in nfc?

I am working with an ST25R3916b, utilizing the RFAL library. I am trying to work with a card that does not always send back a CRC over NFC, so I need to be able to disable the CRC RX checks dynamically. My txrx function looks like:static int st25r_nfca_rxtx_rf(const struct device *dev, uint8_t *tx_data, uint16_t tx_bitlen, uint8_t *rx_data, uint16_t rx_size, uint16_t *rx_bitlen) { LOG_DBG("Transmitting and receiving using RF interface"); ReturnCode ret; rfalTransceiveContext ctx = { .txBuf = tx_data, .txBufLen = tx_bitlen, .rxBuf = rx_data, .rxBufLen = rx_size, .rxRcvdLen = rx_bitlen, .flags = (uint32_t)((NFC_ST25R_DATA(dev)->tx_crc) ? RFAL_TXRX_FLAGS_CRC_TX_AUTO : RFAL_TXRX_FLAGS_CRC_TX_MANUAL) | (uint32_t)((NFC_ST25R_DATA(dev)->rx_crc_keep) ? RFAL_TXRX_FLAGS_CRC_RX_KEEP : RFAL_TXRX_FLAGS_CRC_RX_REMV) | (uint32_t)RFAL_TXRX_FLAGS_NFCIP1_OFF | (uint32_t)RFAL_TXRX_FLAGS_AGC_ON | (uint32_t)RFAL_TXRX_FLAGS_NFCV_FLAG_AUTO | (uint

Hi,I am currently working with the X-NUCLEO-NFC08A1 as reader another PCB with a stm32 microcontroller and a ST25DV04K tag. I don't have access to the source code of the board with the tag but i know the used protocol to interact with it.I got everything running but sometimes it seems as if the HOST_PUT_MSG flag is set before the response is fully written. I poll for the response to be written with something like this:uint8_t waitCounter = 0; /* wait for response to be written by tag. */ while (ftmGetMessageOwner() != FTM_MESSAGE_PEER && waitCounter <= FTM_MAX_RESPONSE_WAIT_TIME) { platformDelay(1); waitCounter++; } if(waitCounter == FTM_MAX_RESPONSE_WAIT_TIME){ platformLog("Tag response timeout.\n"); return true; }But with debugging I found out that sometimes the command sent before is still in the mailbox when the message owner already changed and thus being read instead of the answer.So my question is: When is the HOST_PUT_MSG bit put? Is it put by the user or

Hi all.We are evaluating the use of ST25R3911B on production line in order to communicate with our metering product which embeds STM32U5 and ST25DV.We'd like to customize STSW-ST25R001 firmware for ST25R3911B-DISCO board to our needs but the provided firmware project, part of which was clearly generated through CubeMX, targets the Keil toolchain and lacks the CubeMX .ioc project file, whereas we need to use the GCC toolchain embedded in CubeIDE.Can you provide the CubeMX .ioc project file to speedup our development as soon as possible?Thank you in advance.Best regards.

Dear Community, I am currently facing an issue related to locking an NFC tag after writing data to it. By "locking," I mean making the tag's data read-only, so that once the data is written, it cannot be modified or overwritten. The contents of the tag should be permanently locked after the initial write. This functionality is intended for use in a fintech application, where data integrity is crucial. Could you please guide me on how to implement this lock feature after writing to the tag? Thank you in advance for your support.My Write Function is working perfect private async void WriteDataToNfcCard(ICardReader reader, string data) { try { // Validate UPI link if (!data.StartsWith("upi://pay?")) { lblJustaSec.Invoke(new Action(() => { lblJustaSec.Text = "Input is not a valid UPI link."; AppendToTextConsole("Input is not a valid UPI link."); })); MessageBox.Show("Input is not a valid UPI link.", "Error", MessageBoxButtons.OK, MessageBoxIcon.Error); progressBar1.Visible =

Hello dear,We received a product of ST25R3911B-AQFT, it shows COO Thailand, but we check the PCN paper, the lable should be ST25R3911B-AQWT, but the actual lable is ST25R3911B-AQT, is it normal and correct? Thanks a lot.

I have two questions.(1) Regarding an external crystal oscillator.For the ST25R3916B, is it necessary to have an external 27.12MHz crystal between XTI and XTO? Also, are there any points to note when selecting a crystal?(2) Regarding the design of the antenna matching circuit.I am trying to design a matching circuit using the NFC/RFID Calculators following the method in the AN5276 Application note. How should I decide the values ​​to enter in the "Matching inputs section" and "Inputs section" of the NFC/RFID Calculators?

For my setup, I am using a nucleo-L476RG and a NFC08A1.  I am wanting to learn bare metal programming to really grasp micro controller programming.  I have programmed some smaller bare metal programs, SPI, I2C, etc on the nucleo.  Now, I am trying to interface with the NFC08A1.  Looking at the ST25R3916B datasheet,and reading through the SPI section I was a little confused by the read and write commands in the table 12 SPI operation modes. The other commands are pretty straight forward sending of bits.  Can someone help me understand what A5 - A0 represent?  I am thinking they are addresses to the different registers or referencing certain pins.  For instance, in Table 2 A5 is referencing the SPI enable pin.  In other areas of the data sheet for the SPI interface on Figure 16 SPI communication: writing multiple bytes it says write to the sclk falling edge data moved to address <A5-A0>.  Thanks in advance.

I am currently working on a project that involves reading NFC tags using the NFC X-NUCLEO-NFC08A1 extension, which utilizes the ST25R3916 NFC reader connected to an STM32 Nucleo-G0B1RE platform.Having completed the hardware interfacing for SPI communication between the two, I have now integrated the RFAL files into the project via the X-CUBE-NFC6 package to enable communication between the STM32Cube software and the NFC reader.Are there any modifications required in these files to adapt them to the project? Additionally, what is the difference between X-CUBE-NFC6 and STSW-ST25RFAL002?

Hi everyone,Has anyone experienced issues with the NFC tag becoming unreachable via I2C? During debugging, I noticed a HAL timeout when waiting for the tag's response after setting the address to the EEPROM, static, or dynamic register. Additionally, the NDEF message can't be read, although it can still be read and written via RF as usual.This issue occurred after multiple reconfigurations and also while an application was running with the normal startup configuration in my code, which includes reading the NDEF, disabling the FTM, and GPO. After replacing the ST25DCxxKC, the microcontroller could access the tag via I2C as normal. Therefore, I suspect the problem lies with the tag rather than the microcontroller.I have used the ST25DV64KC and the ST25DV16KC with the STM32G071RB.Best regards,Theresa

Hi ST team,We’re using the ST25R3918 in a low-power BLE+NFC product. During testing, we noticed unexpected ~10 µA additional current draw when the chip was in Power-Down mode (with all VDD rails active), despite expecting ~1–2 µA per the datasheet.After isolating all possible causes, we found this behavior:With I2C_EN pulled HIGH (selecting I²C mode), total current in power-down mode is ~13 µAWith I2C_EN pulled LOW (SPI mode), current drops to ~3 µANo I²C or SPI traffic is active at this point — chip is just powered and sitting in default state after POR, even with lines cut.This behavior seems to suggest that I²C mode selection (I2C_EN = HIGH) may keep some internal circuitry partially active, even in Power-Down mode.We’ve decided to move back to SPI mode (LOW), which solves the issue and also allows faster data transfer and shorter NFC "on-time."Is this increased current draw in Power-Down mode with I2C_EN = HIGH expected?Is there any internal I²C block or biasing circuitry that coul

Hello,I’m currently working on NFC detection using the ST25R3917 with Felica.My system configuration is as follows:PC Application ⇔ USB to I2C ⇔ ST25R3917I’m running RFAL in the PC application and have extended rfal_platform.c to control the USB to I2C interface.The current sequence of operations is:1.rfalNfcInitialize();2.rfalNfcDiscover(&discParam);    memset(&discParam, 0x00, sizeof(discParam));    discParam.compMode             = RFAL_COMPLIANCE_MODE_NFC;    discParam.devLimit             = 1U;    discParam.nfcfBR               = RFAL_BR_424;    discParam.ap2pBR               = RFAL_BR_424;    memcpy(&discParam.nfcid3, NFCID3, sizeof(NFCID3));    memcpy(&discParam.GB, GB, sizeof(GB));    discParam.GBLen                =