ST25 NFC/RFID tags and readers

We found that a specific card type (Mifare Desfire EV1) became unusable with the RFAL after a format. But I was able to "resurrect" it by using a Phone or a reader with a different IC.Since debugging showed that the gIsoDep.state was always getting stuck in ISODEP_S_DSL, I saw that the default retires for deselect are zero. And as the Standard states "When the PCD fails to receive an S(DESELECT) response the PCD may retry the deactivation sequence.", I increased them by manipulating RFAL_ISODEP_MAX_DSL_RETRYS inside the lirbraries headers.As a result the card also worked again on my ST25R3961b based device. But I would very much like to not change the library code and instead use officially provided interfaces. That interface seems to be rfalIsoDepInitializeWithParams(). But it is explicitly called inside rfal_nfc.c with the default parameters, just before starting the RATs. So where do I intervene to get my own settings in? Is that even possible?

I am experimenting with STs Fast Transfer Mode using FEIG MR102 Reader. I tried the FTM Demo on the ST25PC NFC. For that I connected the STEVAL-25R3916B reader and used ST25DVC Discovery board for ST25DV tag.  Please note that I am using the source code of ST25PC NFC to run the FTM Demo so that I can capture the console. I used the "Send a 100k-byte random buffer" option from FTM Demo and looks like it works fine. You can see one instance from console of the FTM in action: 2026-02-27 11:42:53.286 fastWriteMsg >> 22CA02329411AE665102E0FF08E2961EF89ABC5F493D2D14CB68C4A312312D34C056B52A067D78D7575F4B3280F5D3283699CF4A7ED9069AFB137F8DA1185045C625008F995DDA0057A51E329F00A3DA1044D27B0B9A81E4DC28D1C27683AB2430F758859F3E1BE7D6F16815749EC5C094D1A8414AD0561E5CD6CD552AA78EDAED96CE741C4142C7B8275E7D4A9BE10622D4B373B288E2707358C1DC3819A3C8C7672019D9152C1C79F7CBBA98A2D8EFE000730D45E6AA723BFA3A7DCDF38D0D8E7D556A031631D9D589BA4613EE0196C8437CA6596BCA725255EFBD8781D1

I am currently designing an NFC reader PCB based on the ST25R3916B. Could you kindly share the recommended PCB stack-up configuration and the routing guidelines for the NFC antenna? I have also attached images of the PCB layer stack-up that I am currently using. Could you please review them and confirm whether it is appropriate?

I am using a ST25R3916B with RFAL 4.0, connected to a STM32WB55 via SPI in a battery powered application, so naturally wakeup mode is used. Specifically inductive wakeup with auto averaging. For a short test on the table this works just finde, but when I let the setup run for multiple hours and thousands of wakeups, at some point it becomes unresponsive. If I measure the generated field via oscilloscope, I can still see the ~35µs pulses every 400ms, just as I have setup the mode, but there is no interrupt generated.I do not want to completely dismiss the possibility that the MCU is missing one interrupt somehow, but shouldn't a consecutive change trigger a new interrupt?What I have found in the AN is Values close to the edges can lead to a configuration that never wakes-up the system, so, if delta is the difference that triggers an interrupt, the reference value must always satisfy the following conditions: • reference - delta > 0 • reference + delta < 255Is there

(STM32L476RG+X-NUCLEO-NFC07A) I use Android ST25 (ST25AndroidApp-V3.12.2) to communicate with NFC7(STM32L476RG) by FTM.Click FTM demos of  Menu ST25DV Demostrations on Android ST25 APP, and click Send data to tag, 1000 bytes by default, the Transmission/Reception success with showd 1000/1000 bytes as showed in image below:but the show exception "Command failed"  from mDataReceived = mFtmCommands.sendCmdAndWaitForCompletion(...)of source_ST25AndroidApp-V3.12.2\app\src\main\java\com\st\st25nfc\type5\st25dv\ST25DVFtmDemoActivity.javathe frimware is built bySTMicroelectronics\ST25NFC_Embedded_Lib_ST25R3911B_1.8.0\Projects\STM32L476RG-Nucleo\Applications\X-NUCLEO-NFC07A1\FTM\STM32CubeIDEand the uart console shows successAfter build and run (with ST25FTM_ENABLE_LOG enabled), the uart log as below---------------------------------------- *****Welcome to x-cube-nfc7 example***** ---------------------------------------- 10988: RxState = ST25FTM_RX_INIT_RECEPTION 10992: F

Hello,I am back to working on testing a custom PCB with the ST25R3916B chip included on it!  This custom hardware is setup for the differential antenna connection.  The coil to be attached to this custom PCB is different than the one included on the eval board for the ST25R3916B chip.  The pads for the matching components are all included but the components still need to be calculated for the coil.  I have access to a VNA and can follow the procedure for matching... Regarding the matching component calculations...I have reviewed the AN5276 application note and have some questions &/or statements to confirm.  In general I don't fully understand the "target impedance" to match antenna to.  For my application I'm trying to maximize power transfer through a wire wound TX coil.  Under section 3.2 in AN5276..."The impedance matching is the most important factor to determine the power consumption...higher target matching impedance less power is

Hello,I'm having trouble deploying the middleware for the X-NUCLEO-NFC12A1 demo board.I have an x-NUCLEO-NFC12A1 and a NUCLEO-WBA65RI.I connected the two boards together, wired the pins correctly, and tried to use the X-CUBE-NFC12 middleware package. However, when I generate the project, it only includes the ST25R500 driver under Drivers/BSP/Components/.How can I get a proper starting point to develop with the ST25R300? Is there a specific package or example project available for it?My goal is simple: I want to use it to enable and operate a WLC with a PTX30W.Thanks a lot for your help,Yvan

Hello,I am trying to implement the Mifare Classic protocol with ST25R3916 and RFAL.For that CRC and parity bits processing need to be disabled, which ST25R3916 support, so I tried to experiment with disabling CRC and parity framing on a message sent by the tag to see how it is encoded.I am having a hard time figuring out exactly what's the encoding, and the datasheet of ST25R3916 doesn't say exactly what's in the FIFO.I set up X-CUBE-NFC6 with STM32CubeMX and simply modified the polling demo to send the command 6000 + CRC to the tag, which should respond with a 4-bytes nonce with standard ISO-14443-3A parity and no CRC.This is the only part of the code I added, after selecting the ISO-14443-3A tag:uint32_t flags = // CRC stuff RFAL_TXRX_FLAGS_CRC_TX_AUTO | RFAL_TXRX_FLAGS_CRC_RX_MANUAL | RFAL_TXRX_FLAGS_CRC_RX_KEEP | // parity bits RFAL_TXRX_FLAGS_PAR_RX_KEEP | RFAL_TXRX_FLAGS_PAR_TX_AUTO | // analog RFAL_TXRX_FLAGS_AGC_ON; uint8_t tx_buf[8] = {0x60, 0x00}; // use key A on blo

 I'm implementing a children's game board with 6 spaces to place nfc tags with 6 antennae multiplexed as described in AN6121 - which is a great application note and ideal for what I'm doing!   I've done rf and speed layout before but not anything for NFC and I'm a bit confused by a couple of things:- looking at the photos of the board in AN6121 there seems to be a thick and thin trace going to each antenna, and also a thick trace on the back of the board,  none of these look like a differential trace to me, is it just not that critical in this application or am I missing something here?  I wondered if the thick traces on opposite sides of the boards were matched to each other?- secondly I'm reading this "As shown in Figure 14, each antenna has its switching system close to the ports. This matching network is located directly on these ports."  to mean the switching should next to the loop antenna,  but this would leave 5 pairs of traces to nowhere and

Hi,I am using the X-NUCLEO-NFC09A1 with the demo project “ST25R200_v3.0.0_Linux_demo_v1.0”.The code is running on a Raspberry Pi 3B and communicates with the reader via SPI.When I run the demo and place an NFC tag near the reader, the application reports “READ Fail”.Could someone please explain what this error means and what might cause it?Thank you.

Hi, I have been working on a project that is based on the ST25R3911b Discovery Board including building prototype firmware from the discovery kit's firmware. I have made sure not to edit any of the RFAL or HAL library files.Recently I had brought this prototype to be pre-scanned for radiated immunity. During this testing, I discovered a bug that I have not seen before.The process gets stuck in an infinite loop in the rfalTransceiveRunBlockingTx() function (found in rfal_st25r3911b.c).Specifically on line 1267, while( (rfalIsTransceiveInTx() && (ret == ERR_BUSY)) );In the rfalTransceiveTx() function, the process enters the RFAL_TXRX_STATE_TX_WAIT_TXE case and checks for interrupts. However, there will not be any interrupts to process, and so the process breaks without updating the gRFAL.TxRx.state.This appears to me like the interrupt from the NFC chip was either not sent or was not received correctly, so when that Do while loop checks "(ret == ERR_BUSY)", it will always be

深圳豪华品茶工作室哪里好【溦-306-9835-004 】【信誉第一】【十年老店】午后的阳光斜斜漫进木格窗，落在临窗的茶席上。紫砂壶正腾起袅袅白雾，龙井的清香混着陈年普洱的醇厚，在工作室里漫成一片柔软的云。

第一视角)广州越秀豪华品茶工作室感受别样风情:white_heavy_check_mark:【溦-306-9835-004 】:white_heavy_check_mark:【信誉第一】【十年老店】午后的阳光斜斜漫进木格窗，落在临窗的茶席上。紫砂壶正腾起袅袅白雾，龙井的清香混着陈年普洱的醇厚，在工作室里漫成一片柔软的云。属猴人最擅长“四两拨千斤”。比如，家庭聚会时因观念冲突引发矛盾，他们一句俏皮话就能让气氛缓和；朋友求助时，他们总能想出“脑洞大开”的解决方案。这种“举重若轻”的智慧，让他们在年底少遇麻烦、多遇贵人。财运方面，属猴人年底容易因“兴趣变现”收获横财——可能是兼职做自媒体突然爆火，或是玩收藏的小物件意外升值。记住：你的“玩心”里藏着大机遇！

I have successfully integrated a ST25R100 NFC reader with an ST25DV04K tag. Reading and writing data works perfectly.But once you enclose the system in its housing, writing doesn't work, even though reads still succeed.I presume this has something to do with that tag rely entirely on the RF field to power their EEPROM during write operations.Can I increase transmitting power via software?I can't find it the Documentation.Any help greatly appreciated!William

Hello.For example, on the datasheet of ST25R200, on page 10, it shows 2 capacitors between pins VDD_A and GND_A, but on page 13 it is not shown the recommended values of these 2 capacitors.Would they be 2.2uF and 10nF, or 1uF and 10nF, for example?I'm talking about pin 14 in this case.Regards. 

Hello I am beginning the electrical schematic with the ST25R200. I saw on the datasheet, and here:https://eds.st.com/nfc-tuningcircuit/I saw that there is the single-ended and differential ways / circuits to drive the antenna.The differential circuit is bigger, it has more components.So what I ask here is about these difference (single-ended / differential), if using the single-ended scheme it's possible to reach the same tag distance reading of the differential scheme. Because our PCB is relativelly small in space available. Are there more advantages on using the differential circuit compared to the single-ended circuit?RegardsJeferson Pehls.

Hi,Comparison of STEVAL-ST25R3916B UM3033 [pg 22] & ST25R Antenna Matching Tool...Specifically the matching networks show a difference in location of parallel tuning capacitor relative to antenna connection. UM3033 antenna matching + filter [above].  Notice the location of the parallel tuning cap [C308] in relation to antenna connection ANT300.  The ST25R matching tool [above] shows antenna matching + filter.  Notice the parallel tuning cap is in spot closer to antenna connection than the UM3033 schematic. The physical STEVAL D25R16BA board shows the tunable cap next to the antenna [see red box below].  Silkscreen confirms this also.  Based on the above it seems that the STEVAL-ST25R3916B antenna matching schematic in UM3033 DOES NOT match the physical board. My question: Should tunable capacitor be placed as shown in the ST25R matching tool or should it be placed as shown in STEVAL-ST25R3916B UM3033?I've created a custom PCB f

Hello people. In 2020, our company made a PCB prototype (designed by me) which included a chip " ST25R95-VMD5T ". Our results were not good, but maybe this was due to a poor filter circuit and due to a poor matching circuit. The tag reading distance was very small, and the prototypes were not fixed (filter and matching), and we abandoned the project.  So in the same year of 2020, we were planning to make another PCB prototype, but then using the chip " ST25R3911B-AQFT ", with the intention that the reading of tags could reach a bigger distance, but we ended up not doing this prototype in 2020. Now, it's 2026, and we plan to make a PCB prototype, very simple. And our initial choice was the " ST25R3911B-AQFT ". I would like to ask if there are more recent chips than this, possibly one chip that can reach a bigger reading distance than this " ST25R3911B-AQFT ", or that reaches the same distance reading, but that has more recent technology. Remembering that this ti

Hello,I am using the ST25R3918 controlled by an MCU via RFAL, operating in NFC-F / FeliCa card emulation mode.I am monitoring the efd_o bit (bit 6) of the Auxiliary Display Register (Address: 31h) to detect when the board approaches an external reader. While I observe that efd_o stays at '1' during the initial idle state and during the first few commands, it becomes unstable (toggling between 0 and 1) after the communication sequence is completed.Sequence of operations:Receive Write Without Encryption from the reader.Send response for Write Without Encryption.Receive Read Without Encryption.Send response for Read Without Encryption.Reader terminates the communication.efd_o becomes unstable (toggling 0/1) for several hundred milliseconds. (Note: efd_o is stable at '1' during steps 1 through 4.)RFAL Configuration:discParam.devLimit = 1U;discParam.totalDuration = 60000U;discParam.techs2Find = RFAL_NFC_LISTEN_TECH_F;Questions:Is this unstable behavior of efd_o expected after a transaction

Hello,I have an ST25DV64KC chip and I’m having a problem with I2C read/write. The I2C bus is running at 100 kHz and is functional (communication with another sensor, SHT, on the bus works fine). I am also able to communicate with this NFC chip - I can read registers and read the chip’s UID correctly.The problem, however, is with reading/writing the user memory over I2C. When I try to write or read, I get NOK and the bus goes to low level and freezes. I have a main question:Q1. How is the memory actually organized? I know that the user memory has a 7-bit address of 0x53 and the system memory has an address of 0x57. I expected that the UID, which in the datasheet is listed under the System Configuration area, would be available at I2C address 0x57, but in fact it seems to be part of the EEPROM, and the UID is accessible via the user memory at I2C 0x53.So how does it actually work?? - if via I2C address 0x53 the System Configuration area is accessible at registers addresses 0x0000–0x0023

We are using NUCLEO-WB55 evaluation board + X-NUCLEO-NFC07A1 NFC tag, we downloaded your OOB demo kit STSW-ST25DV013 from  https://www.st.com/en/embedded-software/stsw-st25dv013.html, followed your instructions to program the .BIN to evaluation board,  also install the .APK included to Android tablet, tap the NFC antenna, instead of paring automatically, it pops up a windows ask if you want to pair, clicked YES it finished the paring.Our question is: is this the same result when you testing? should the OOB paring be finished automatically without pressing any extra buttons?  @Colin RAMRATTAN  

Hi everyone,I’m trying to interface an ST25R100 NFC reader with my MCU, and I’m having trouble reading ISO15693 tags. My initialization seems to work, but I never get any response from the tag. I’m hoping someone can spot what I might be missing.This is what my uart debugging spits out:INIT - NFCNFC: Init start (POR -> RESET -> POWER-DOWN -> Ready Mode)ROP_REG_OPERATION = 0x00 (after PD write)ROP_REG_GENERAL = 0x01 (after write)ROP_REG_REGULATOR = 0x08 (after write)NFC IRQ triggered!IRQ: I_osc Oscillator readyROP_REG_OPERATION = 0x0A (after enable)ROP_REG_OPERATION = 0x0A (check mode)Chip is in READY mode (en = 1)STATUS register = 0x00NFC Reader OperationROP_REG_PROTOCOL = 0x85 (after write)ROP_REG_OPERATION = 0x3A (after write)NFC IRQ triggered!IRQ: I_txe End of transmissionNFC IRQ triggered!IRQ: I_nre No-response timer expiredThis is consistent with what the datasheet says on page 22.But now I don't quiet see how I can get it to read data from my NFC-Tagvoid NFC_Init(void) {

Hello,I got back to my issues from this post.I was able to connect wires to SPI lines, and get the measurements to logic analyzer. These are the results:Logic2 screenshot Now i can see that the issue is the CS line, but i dont know why it is being changed to HIGH in these short pulses.  The GPIO config: /*Configure GPIO pin : SPI1_CS_Pin */ GPIO_InitStruct.Pin = SPI1_CS_Pin; GPIO_InitStruct.Mode = GPIO_MODE_OUTPUT_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Speed = GPIO_SPEED_FREQ_HIGH; HAL_GPIO_Init(SPI1_CS_GPIO_Port, &GPIO_InitStruct);SPI Config:hspi1.Instance = SPI1; hspi1.Init.Mode = SPI_MODE_MASTER; hspi1.Init.Direction = SPI_DIRECTION_2LINES; hspi1.Init.DataSize = SPI_DATASIZE_8BIT; hspi1.Init.CLKPolarity = SPI_POLARITY_LOW; hspi1.Init.CLKPhase = SPI_PHASE_2EDGE; hspi1.Init.NSS = SPI_NSS_SOFT; hspi1.Init.BaudRatePrescaler = SPI_BAUDRATEPRESCALER_32; hspi1.Init.FirstBit = SPI_FIRSTBIT_MSB; hspi1.Init.TIMode = SPI_TIMODE_DISABLE; hspi1.Init.

Hello everyone,I am developing an iOS application using the ST25SDK (converted/wrapped for Swift) to interface with the M24LR16E-R Dynamic NFC Tag.I am facing a blocking issue where any attempt to call readBytes() (which is used in TagReadMemoryGenViewController.readMemoryContent) throws a ComStSt25sdkSTException with error code BAD_PARAMETER.The Setup:Chip: M24LR16E-R (IC Ref: 0x4E)Platform: iOS (Swift) using CoreNFCLibrary: ST25SDK for iOSThe Problem: Upon investigation, the root cause appears to be that the ST25SDK mTag.getMemSizeInBytes() returns a memory size of 0 bytes. Consequently, when readBytes() is called, the SDK performs an internal safety check: if (address + length > mMemSizeInBytes) { throw BAD_PARAMETER; } Since mMemSizeInBytes is 0, this check always fails.Root Cause Analysis: The issue seems to originate in the iOSRFReaderInterface during the Get System Info command. The M24LR16E-R has 512 blocks (2048 bytes total). When using CoreNFC's native getSystemI

I'm developing a new secret card project using STM32L476RG and X-NUCLEO-NFC07A1 board, I plan to let the secret card to store private key and do signature related tasks. I'm not sure where can I get blank card which contains the same MCU with STM32L476RG) and the same NFC7 with X-NUCLEO-NFC07A1? I found there are blank card in sale support NFC ISO 14443 protocol. Seem the NFC7 using ISO 15693 protocol. So the NFC blank card support support ISO 15693 protocol can run my image, as showed in image below?ThanksJack Ding.