ST25 NFC/RFID tags and readers

in NFC readers product selection page the "interface to host" feature for solutions ST25R3916, ST25R3916B, ST25R3917B, and ST25R3919B is listed as "SPI" only, But when I open the product page of these solutions I find that they support both SPI and I2C protocols and they are listed under the "External Communication" tab. Which one should I believe?P.S: The Datasheets of these solutions are grouped with other solutions which already have both I2C and SPI support so they don't solve this conflict "e.g: the same datasheet is for both ST25R3916 & ST25R3917, but ST25R3917 is already approved to have both SPI & I2C interface to host by product Selection tab while ST25R3916 is featured as SPI only in the product selection tab".

Hi everyone,I am using a ST25DV04KC-IE8T3 connected to a low power consumption display.I'm trying to power the display with ST25 when ST25 detect the RF. (the display can work from 1.5V to 5V with just on/off configuration).ST25DV04KC-IE8T3 GPO is open drain, can I enter a command which can allow this operation described above ?Thank you so much. 

I have a question regarding ST25R3911B resource optimization.https://www.st.com/resource/en/user_manual/um2890-rfnfc-abstraction-layer-rfal-stmicroelectronics.pdfAdditionally, I have read the RFAL user manual mentioned below, and in the FEATURES CONFIGURATION section, the features appear to be independent of one another. However, I would appreciate it if you could confirm whether there is any dependency among them.We are only using "RFAL_NFCA_T4T," and we're inquiring about ways to optimize the RFAL library and memory resource as they are currently too large.It seems that we might need to modify the platform.h, specifically looking to optimize the defines from line 165 to line 185.We have ported NFC using the ST25R3911B RFAL library.When we tag an NFC Card and read it through Uart, we intend to use only the "RFAL_NFCA_T4T" mode.The debug information is as follows:DEBUG START from UART===========================rfalNfcIsDevActivatedRFAL_NFC_LISTEN_TYPE_NFCANFCA Passive ISO-DEP device fo

Hi! I am attempting to use the current 1.10.0 Java SDK on a windows 10 pro computer with JDK 1.8.0_144. (Java 8) x86 - for use with ST25R3911-DISCO at first, and hopefully then the Feig USB reader. I have carefully followed the st25pcdemoapp_...pdf document as well as created my own simple demonstration [pictured] and gotten the same result: "streader.dll: Can't find dependent libraries"I have found the 2020 post with the same issue, and the linked zip file does not fix the problem. I have now used dependency walker to attempt to hunt down what is missing, which can be seen in the attached screenshots.It appears there are a bunch of windows 10 SDK dlls that are not found, but I am so far unable to figure out where to find them to install them. The microsoft KBs appear to be for prior versions of windows. Any advice on resolving these dependency issues?Thank you!

Hi all,  I have designed and built a custom circuit using the ST25R3916 (in differential mode with AAT) and a ATxmega128A4U micro controller. I have spent the last two weeks trying to get it working so my phone can detect it as a card as a starting point. Eventually I want to the phone to read data files from the device.  I believe I have the hardware working, as I have a 13.56MHz signal on the antenna which is +-7V and I get EON and EOF interrupts when I place my phone over the antenna.  However, I am not able to get the phone to detect it as a card. I feel that I am 90% of the way there, but I am struggling to understand the configuration of the chip fully and the RFAL code in ST25 embedded lib (STSW-ST25R016 for 3916) which I have spent quite a bit of time looking at. It is way more complicated than I need and I cant find the basic initialisation that I need.  I have been through other forum threads including this one, and tried to replicate the register settings

Hello,I'm building a proprietary NFC reader based on ST25R3917 chip and STM32F070CBT6 MCU. I use Bare Metal approach without any HAL or RFAL which might complicate my query a bit but I'll try to ask anyway. So far I'm able to Poll Type A and Type B cards, carry APDU over higher protocol layer etc without any issues. What I'm struggling with is switching over to WakeUp mode to save power.Below is a log of i2c communication from none-eabi-gdb. << represents a flow to the reader:<< Direct Command: 0xc0<< Address: 0x0, Data: {0x0, 0x80, 0x0}<< Address: 0x16, Data: {0x6e, 0x9f, 0xff, 0xff}<< Address: 0x10, Data: {0x7, 0x0}<< Address: 0x13, Data: {0x21, 0x1b}<< Address: 0x2, Data: {0x80}<< Direct Command: 0xd3<< Address: 0x34, Data: {0x63}<< Address: 0x33, Data: {0x32, 0x30}<< Address: 0x32, Data: {0x38, 0x34}<< Address: 0x2, Data: {0x4}<< Address: 0x16, Data: {0xff, 0xff, 0xfb, 0xff}Basically I follow&nb

Hello,I am working on a version of the STM32L476RG_NUCLEO_AP2P_PROP_NFC8 demo included with the RFAL library examples, trying to get it going on a NUCLEO-F072RB.I have my code running, and if I bring an L476RG flashed with the unmodified AP2P demo, the boards will transact, but the F0 board is always the initiator.  Previously, when using two L476RG boards and the original demo, they would change which was the initiator and target depending on the timing they were brought in proximity.I've been debugging thoroughly, but I can't quite narrow down what my issue could be.  rfalNfcWorker() seems to be setting gNfc.state to the correct states: RFAL_NFC_STATE_POLL_TECHDETECT, RFAL_NFC_STATE_LISTEN_TECHDETECT, etc.  I've noticed when stepping through, though, that it never leaves RFAL_NFC_STATE_POLL_TECHDETECT, but if I set a breakpoint at the different cases in rfalNfcWorker() it will cycle through them during discovery.My big issue: when I program two F0 boards with my modifi

Hello,This is sort of related to my earlier post, and is an effort to uncomplicate things a little.  I have configured a project using X-CUBE-NFC6 on a NUCLEO-L476 and NFC08A1 board.  The demo runs fine, and can detect the different technologies.However, when I comment out the technologies in rfal_defConfig.h and rfal_features.h so that the only technologies used are RFAL_FEATURE_ISO_DEP and RFAL_SUPPORT_MODE_POLL_ACTIVE_P2P (and LISTEN), I cannot get two L476 boards with the same software to initiate a AP2P connection.When I load one of the boards with the AP2P_PROP example from the ST25 Embedded Lib examples, however, I can get both boards to communicate.  Two boards with AP2P_PROP also will communicate.  It is only the X-CUBE projects that seem to have the issue.I have spent many, many hours going through debugging both projects to see the difference, but there is none that I can tell.  Is there some analog config difference that would make this happen?

Hi, I am trying to understand the difference between blocking/non-blocking rfal apis.  ReturnCode rfalNfcvPollerReadMultipleBlocks( uint8_t flags, const uint8_t* uid, uint8_t firstBlockNum, uint8_t numOfBlocks, uint8_t* rxBuf, uint16_t rxBufLen, uint16_t *rcvLen );  It seems to me that the above api is a blocking one. How can I achieve the same functionality in a non-blocking way ? The reason I am asking this is because it seems that this api is taking too much time to execute (Without the time required to perform I2C read). Is my understanding correct on the RFAL library sequence for the above api ?RFAL library request ST25R3916 for the requested amount of data.RFAL waits in a busy wait loop until interrupt pin changesOnce the interrupt pin changes, RFAL library performs read from ST25R3916.I am concerned about step 2 as it is a busy wait loop and other threads seem to be starving. 

Hello community,I'm developing a FW for a board that uses the ST25DVxxxKC to show some board info (as tags) and to allow to update the FW.I've no problem or doubt on the board side (FW).I'm trying also to develop an application on a PC equipped with Windows OS to test the board, but after a couple of days of search and test I've found that I don't know how to connect with the board in both mode (FTM and standard/nDef).I've been able to connect to the board using my ACR1552U and the Windows standard library (WinSCard.dll), but I've no idea of which protocol to use.My application is written using Qt, but also Visual Studio Code could be an option.I've downloaded the app examples provided by ST, but I haven't found nothing that can give me some hint.If anybody has any suggestion, it would be very valuable.ThanksRoberto

I have purchased X-NUCLEO-NFC03A1 (CR95HF) evalboard, and nucelo-F072RB board.I want to develop RFID reader/writer . Please suggest a firmware example code which I can program in the eval board. Secondly Does ST has any PC based utility which can be used to send commands to nuclo board to read and write RFID cards/tags. Please share videos which demonstrate the same. Thanks

Hi Sir/Madam, I am working with I2C in x-nucleo-nfc07a1 where ST25DV IC incorporated interfaced with Nucleo-WB55 board, what is the slave address(device address) for this?I am firmware engineer, I have I2C Scanning program wherePreviously, I work with Temp sensor, the scanning code gives me slave address as 0x4a,I also work the following,Heart rate sensor in which it is 0x57PN532 NFC reader in which it shows 0x24And right now I work with X-Nucleo-NFC07A1 in which ST25DV64KC is incorporated, here the scanning code shows none. I want to know, why it is not? and how to deal with i2c communication to store data in EEPROM? HAL_I2c functions deals with 5 parameters, DevAddr, TargetAddr, Data Buffer, No.of.Bytes req, delay, out of which DevAddr what we can use?In the datasheet of ST25DV64KC, Table 89 Device select code and Table 91 I2C CFG are confusing with the bit assignment. I also attach the respective datasheet for your reference.Best Regards,Bhuvaneswaran T

Currently, I'm using CR95HF on our product which went into mass production already.  The tag is small with diameter only 9mm.  In the field, we are seeing a few percentage of unsuccessful read from the first read and need to retry several times.  How can we increase reading distance?  Is it possible to boost the transmit power from the reader chip? The tag has NTAG213 on it.  Our reader antenna is in octagon shape.    

Hi,It may be a *** question but, im quite sure i read time ago that on VDD_AM pin the 2u2 cap must not be place at one sccenario, but now im not able to find where i read that info and also i dont remember which was the scenario. I start to think im wrong, and both caps (2u2 and 10n) must be placed always.Could someone confirm it?thanks in advancedignacio 

Hello,I am trying to port/get running the NFC08A1 RFAL polling demo on the NUCLEO-F072B.  I had no issues using L476RG.  I am fairly certain I have SPI set up correctly in CubeMX.  But, I am getting stuck at initialization, specifically at st25r3916CheckChipID(). ID is read as 0x18, which is causing it to return false and throw an error.  I was taking a look at the SPI traces and MISO (pink) looks not quite as clean as MOSI (blue) (sorry, had to capture using phone camera):Rise/fall on MISO looks a little slow compared to MOSI.  Could this be causing the issue?  From the datasheet, it looks like chip ID should come back as 0x31:Anywhere else you think I should look?  Thanks.

I'm working on implementing STEVAL-ST25R3916B reader expansion board circuit schematic into custom PCB. Can I please get the actual design files for these, including the layout. I did find the pdf version but it would be great to have the design files. If the files are in Orcad format can I please get the .alg for the .brd file?Thank you, BV

I have a product already developed using the M24LR64ER and I need to read and write using an IPhone 14 with IOS 17, would it be possible to read and write using Swift's "import CoreNFC"?

I am in the final stretch of my project using the ST25R95 with an ATTINY88.  I am working on custom hardware and not using libraries.I have all of the ST25R95 related commands working on my development setup with an Arduino UNO and X-NUCLEO-NFC03A1 but I moved to the custom hardware and I am not able to read a tag.I used the EMI Filter Calculator to determine the values for the EMI filter and matching circuit.  Measuring with a spectrum analyzer, I have a higher level of output at 13.56 MHz than the NUCLEO dev board.  So my matching must be pretty good.I have attached the SPI trace from boot to the SENDRECV REQ command to wake the ISO14443-A tag but I get a 0x87 response.Any ideas?

Hello everyone,before introducing you to the issue I am experiencing, let me share my setup:uC: STM32U585I2C: Fast Mode PlusIde: STM32CubeIdePower Source: 3.6VDC (laboratory power supply)st25dvxxkc package: GitHub st25dvxxkc RF Reader: ST25 App (Google Play Store)Before sending any I2C command to protected area an I2C security session is opened with ST25DVxxKC_PresentI2CPassword() function; My RF Interface is NOT working anymore after sending ST25DVxxKC_SetI2CCFG_RFSWITCHOFF(&(pObj->Ctx), &reg_value) I2C command. I'm trying to restore it but until now I have not succeed. In order to restore it I've tried to apply some I2C command such ST25DVxxKC_ResetRFOff_Dyn() from st25dvxxkc package I pasted beforehand, but it's not working since it writes NULL data:ret = pObj->IO.Write((pObj->IO.DeviceAddress | ST25DVXXKC_ADDR_RFSWITCH_BIT_I2C) & ~ST25DVXXKC_ADDR_MODE_BIT_I2C, ST25DVXXKC_ICREF_REG, NULL, 0);which is of course denied from HAL_I2C_Mem_Wri

I'm developing an app in Xamarin in order to read and write via mailbox the ST25 chip. In Android everything works fine but on iOS it's more complicated. Has anyone some example in Xamarin.iOS?Thankyou Davide.

Hi am using ST25R3911B DISCOVERY Board, and I am using ISO15693 Single read and write function.but this function not work properly and i found an err code after execution the code.the value not to be read and write properly. but  st25r3911WriteTestRegister(res,value);this function work properly for read and write.Do u have any suggestion regarding this . 

I was trying to fabricate a flexible NFC antenna for m24lr chip. Initially, I fabricated my design on a copper PCB. It worked perfectly fine with my NFC chip and facilitated NFC communication. I observed its S11 curve using a NanoVNA with a loop probe, and it showed the minimum of the curve within the expected frequency range (around 13.6 MHz).When I fabricated it on a flexible substrate (PET,) using silver nanoparticle ink, I found that the minimum of the S11 curve was lost. The antenna still worked fine with the NFC communication, but I got a flat curve everywhere, from 5 MHz to 50 MHz (I did not observe beyond that range.)I measured the resistance of the flexible antenna and found that it has nearly 600 ohms of internal resistance, whereas my PCB antenna had about 2 ohms of resistance. Then, I connected my PCB antenna in series with a variable resistor and observed the S11 curve while varying the resistance of the variable resistor. I noticed that as the resistance increased, the mi

We use ST25NFC_Embedded_Lib_ST25R3911B_1.5.0 for our current project.There are some example inside.In all example in stm32l4xx_hal_msp.c are the following code:/* Configure all GPIO port pins in Analog Input mode (floating input trigger OFF) except debug pins */GPIO_InitStruct.Pin = GPIO_PIN_All & (!(GPIO_PIN_13|GPIO_PIN_14));GPIO_InitStruct.Mode = GPIO_MODE_ANALOG;GPIO_InitStruct.Pull = GPIO_NOPULL;HAL_GPIO_Init(GPIOA, &GPIO_InitStruct);GPIO_InitStruct.Pin = GPIO_PIN_All & (!(GPIO_PIN_3));But & (!(GPIO_PIN_ should be & (~(GPIO_PIN_Please fix this in next release.

Hi @Brian TIDAL  @Rene Lenerve  @JL. Lebon Can you please help me understand how antenna size in st25dv64kc tag effect the reading range and another question is like in iso15693 tag reading range is 60cm but practically working with tag my experience  the effective range of communication  between  tag and nfc enabled phone is 6cm why is this?

 we are attempting to read wristband mifare classic tag using NFC03A1NFC03A1 is able to detect the tag UID.when we execute ndefPollerReadBytes().. directly, we get ret = 04 (ERR_TIMEOUT)need some sample code to read this tag...from your forum i understood that we need to perform authentication before we can read/writehttps://community.st.com/t5/st25-nfc-rfid-tags-and-readers/st25r3917-mifare-license/m-p/232467we prefer ndefPollerReadBytes/ndefPollerWriteBytes() to store data directlykindly suggest the rfal call sequence with examples.. PS: used android nfctool application to read the tag.