ST25 NFC/RFID tags and readers

Our application is not related to payment but more around NFC charging and tagging, we'll be using the X-NUCLEO-NFC06A1 (+ NUCLEO-L476RG) combination for the poller.Regarding the listener, we saw that the ST25DVxxKC lineup would be compatible. I'm not too familiar, but what would be the main differences between the ST25DV04KC, ST25DV16KC, or ST25DV64KC models? It seems the EEPROM is the main differentiator, but what implications does the capacity of this memory have on NFC performance? Are there cost/benefit tradeoffs?Also regarding a development board for the listener (for example the ST25DV64KC), what would be the appropriate choice? I see that there are three options: STEVAL-SMARTAG2, ST25DV64KC-DISCO, and ANT7-T-25DV64KC. Could you briefly explain what the differences would be and what the best choice for NFC charging/tagging development would be?Also, would the poller (ST25R3916) and listener (ST25DVxxKC) combination be WLC 2.0 compliant?

Hello, I am trying to open a project that can turn on the low power MCU stm32l031 with ANT7-T-25DV64KC while turning high and low periodically for GPO pin of the MCU. I tried many different ways but still not done with any of them (steval code and using NFC4 and 7 provided by stm32cubeide).Would you please suggest me for any reference or sample for St25DV-i2c?

I'm trying to open a security session with an st25DV tag. I followed the manual and I am sending a message to present the default password (8 x 00h + 09h command + 8 x 00h) using HAL_I2C_Mem_Write. I already looked at the signal with a logic analyzer and all the bytes are being acknowledged, however, when I try to read the I2C_SSO_Dyn register right after I get a zero.Does anyone know what the problem could be? The password has never been changed before, is it possible that the default password is different? Or maybe I'm not reading the register correctly?The present password code I am using is as follows:int32_t PresentI2CPassword(const ST25DV_Object_t *const pObj, const ST25DV_PASSWD PassWord) { uint8_t ai2c_message[17] = {0}; uint8_t i;   /* Build I2C Message with Password + Validation code 0x09 + Password */ ai2c_message[8] = 0x09; for(i = 0; i < 4; i++) { ai2c_message[i] = (PassWord.MsbPasswd >> ((3 - i) * 8)) & 0xFF; ai2c_message[i + 4] = (PassWord.LsbPa

Am in the infancy of a proof-of-concept investigation with ST25DV64. I have been able to do some read/writes with NFC without issue - and am working on the i2c side.We are working with a custom/proprietary system/i2c stack so I don't have much off-the-shelf code to fall back on, but I've written what seems to be a proper implementation of the basic register read/write protocols outlined in ST25DV64 datasheet - and they MOSTLY work. I can read the NFC NDEF data via i2c from registers at i2c address 0x53, device addresses 0 - 32.I am also getting what appears to be valid Dynamic Configuration registers via device 0x53 register addresses 0x2000-2007 as such:2000: 88 ff 08 00 00 00 00 00Which seem to be a valid representation of the initial state of these registers. I can also write and modify one of the GPO bits and read it back But here's where things get weird:If I write like an 0x08 to location 2000 - it seems to turn off the high 8 bit. But If I write a 0xff I read back an 0x88. If I

Hello,We are now entering the stage of PCB editing and I wanted to ask for your help in the needed calculations and outcome of a printed antenna to be used with the ST25DV04K IC.I have read the app note titled "an2866-how-to-design-a-1356-mhz-customized-antenna-for-st25-nfc" but I find it hard to understand and so I turn to your professional help since I do not want to make any mistakes with this.Attached is an image of our PCB. As you can see it is a round PCB with a diameter of 34mm and a thickness of 0.8mm. I can see from the ST25DV datasheet that the Ctun internal capacitor value of the ST25DV is 28.5pF but from this point I am lost. Can you please assist me?Thank you,Nir.

I'm looking for a dev board for the ST25R3916 and I see two options: what would be the difference between the ST25R3916-EMVCO and X-NUCLEO-NFC06A1?I see that the X-NUCLEO-NFC06A1 requires a separate MCU board to connect to, but is that the only difference? In terms of functionality and testing the ST25R3916, would they be equivalent? In that case, what would be the use case for the ST25R3916-EMVCO?

Hi,Do you have cad for the ST25R3911_MB1325 reference design?

Im trying to get the Pollerexample with the ST25R911b-DISCO working i attached a Picture that shows where.It just stared the programm an had no connection to NFC devices befor.How can i get out of ERR=BUSY ?

Hello, I have an application where we are using a couple of the ST25R3916B in a design but with a different processor. I've looked through the forum posts and gleaned some information here and there, but is there a guide on how to port this library to a different processor? It is the MSP430F5xx series. Or I don't suppose you have any example code that is already ported for this processor?We will be reading either the ISO15693 or ISO 14443 tags; that hasn't been decided yet.I'm using ST25NFC_Embedded_Lib_ST25R3916_1.4. I will be using the basic polling example.Ideally the porting guide would include:How to set up the directory tree so that everything is foundWhich files I will need to port to my own hardwareHow to test that we are communicating with the ST253916 successfully.Which middleware I need to includeAny "gotchas" or information that is important to know when portingThank you,Derek

Hi, we are evaluating the ST25R3916 NFC card emulation solution but we cant find any card emulation related info in the ST25SDK. Please advice.Thanks, Best Regards.

..

Is there a list someplace of pre-certified NFC modules which use ST25 chips?Thanks,Scott

I would like to ask if someone has a code for the implementation of the RFAL and NDEF libs for X-NUCLEO-NFC05A1 NFC Card Reader? Hope you can send me the sample code because it is really hard to port the Middleware to Mbed Studio.

I am building a mobile application with react native using ST25DV04KC. I am trying to read 900 blocks with ISO15693 technology, but the readmultipleblocks method does not read more than 255 blocks. Which function can I use related to the subject or how ca var count = Math.floor((endBlock - beginBlock) / 62); console.log('/62'); for (let i = 0; i < count; i++) { var _tmp; var deger; _tmp = await NfcManager.iso15693HandlerIOS.readMultipleBlocks({ flags: Nfc15693RequestFlagIOS.HighDataRate, blockNumber: i * 62 + beginBlock + i, blockCount: 62, });Here are the codes I use. Can you help with the subject?

Hello all,I am developing a small reader with ST25R3912 and I can't use the RFAL library because I want to control it in the final application MCU STM8L. I was inspired by this discussion (https://community.st.com/s/question/0D50X00009XkWIfSAN/register-settings-for-st25r3911b-for-iso-15693) and based on it I wrote a short test program that will try to read the UID from Tag (I only use tag 15693 - inside the ICODE SLIX chip). RF IC using 3.3V power supply and antenna is single sided (components recommended by STM25 Antenna Matching Tools)My ST25R3912 initialization looks like:WriteToSPI (0x00,0x8B);                  //IO configuration register 1 - address 0x00             // single side antenna, use RFO1, RFI1, 64 water level for recieve, 32 water level for transmit, 27.12 MHz Xtal, MCU CLK set 6.78MHz, no MCU

I am attempting to write to a ST25DV16KC part using a Feig LR1002. I first send the inventory command (0x01) then the write multiple blocks command (0x24).I am getting error 0x12 "The specified block is locked and its content cannot be changed "01/11/23 10:27:46.827 >> 02 00 09 FF B0 01 00 18 43 01/11/23 10:27:46.991 << 02 00 1D 00 B0 00 02 03 00 E0 02 51 00 02 56 4A A4 03 00 E0 02 23 00 18 89 2B 09 E3 00  OK01/11/23 10:29:26.068 >> 02 00 34 FF B0 24 01 E0 02 51 00 02 56 4A A4 00 08 04 04 03 02 01 70 60 00 05 0B A0 90 80 0F 0E 0D 0C 13 12 11 10 00 16 15 14 00 00 00 00 00 00 00 00 18 18 01/11/23 10:29:26.077 << 02 00 0A 00 B0 95 12 00 94 29  Reader: ISO-Error

Would like to use the ST25PC GUI to test a tag (ST25DV04K) ( in ST25FTM mode specifically)As i have difficulties finding a ST25R3916, I would like to know if I could use a X-NUCLEO-NFC06A1 on P-NUCLEO WB55 development board to communicate with ST25PC.Could I in a simple way change the ST25R3916-DISCO proj and adjust it to my board?if not can you recommend for my type of use what will be better: ST25R3911B-DISCO or CR95HF .Thanks!

Hello,I'd like to get access to P2RAM to generate some sort of "Unique ID" between multiple ST25R3916 communicating with a single stm32 host Mcu.How to get Access & Read this memory ? i saw it was mentioned in the Datasheet but not elsewhere. Thank you,

Hi sirs,I have a ST25R3911B-Disco (NFC board) on hand, and my platform is STM32F767IGT6.My question is how to integrate the X-CUBE-NFC5 code to my existed project (Keil uVision5), I simply copy the major .c and .h files from RFAL and BSP folder to the project but got many errors. Is there any tutorial shows on how to add the code to a project or which software I need to use to build a new project with X-CUBE-NFC5?Best regards,Joe

Hi,I have M24LR16E-R product. I am reading UID and I see the IC ref product version 4Ch I was reading the IC ref value as 4Eh in the old versions I have. Looking at the ST documentation, I noticed that the value should be 4Eh. So is there any difference between eeproms with different 4Ch and 4Eh IC ref product numbers, and if so what is it?

Can you explain why there are Near Field Communication antennas on both sides of this device? I'm designing Circuit for M24LR04E-R6MNT/2 I would like to follow the circuit diagram of X-NUCLEO-NFC02A1. But there are both side antennas. It would be very helpful if you could explain why they are available on both sides. It is very helpful if you can send me the both top and bottom assembly views of that.(optional)

Setup in use:P-NUCLEO-STM32WB development board.X-NUCLEO-NFC04A1 expansion board with software pack ( NFC 4.2.05) Added : DMA support for I2C , .ioc cubeMX image attached.The issue is that I cannot read the ST25DV ID via I2C DMA read. I simply do not get an answer. While the I2C blocking read works fine.Simple test code I made: // main.c   MX_NFC_Init();   /* USER CODE BEGIN 2 */ uint8_t pData = 0u;   // WORKS! if ( HAL_OK != HAL_I2C_Mem_Read(&hi2c1, 0x00AE, 0x0017, 0x0002, &pData, 0x0001, 0x1000) ) { __NOP(); assert_param(false); return 0u; } pData = 0u; // DOES NOT WORK. if ( HAL_OK != HAL_I2C_Mem_Read_DMA(&hi2c1, 0x00AE, 0x0017, 0x0002, &pData, 0x0001) ) { assert_param(false); return 0u; } //STUCK HERE! while(!pData) { }   /* USER CODE END 2 */   /* Infinite loop */ /* USER CODE BEGIN WHILE */ while (1) { /* USER CODE END WHILE */   MX_NFC_Process(); /* USER CODE BEGIN 3 */ } /* USER CODE END 3

Hello Can NFC tag be used to transmit audioif yes , which type can be used from ST and what reader would be appropriate.not the physical proximity tags but other thanks

Hello, sorry for the inconvenience but I really can't understand why I can't write/read new cards (the ones he has work) from my customer reader. What am I doing wrong?I enclose the photos, his card (working and writable / readable) and the one I created for him.Thanks again,Andrew

We have used your ST25 NFC Tap app to read NFC tags emitted by a device with an ST25 chip. That has worked quite well up to a point when certain smartphones got their Android 12 update. Now the app displays an error.The phones are a minority but they are delivered by leading brands like Nokia or Motorola. Android 11 works fine in all cases. Also, ST24 has no problem connecting with Android 12. Is there any known issue about this combination (chip + OS)? If yes, can it be worked around?