ST25 NFC/RFID tags and readers

Hi I am evaluating NFC function on your STEVAL 25R3916B board, but I would like to see how it works with the I2C interface. Currently, the default configuration is SPI.I have downloaded STM32CubeIDE and STEVAL-25R3916B_V2.1.0 project code, but am not sure where should I put this definition "RFAL_USE_I2C", could you help me check where this macro needs to be placed?Thanks Leo

Dear  STMicroelectronics TeamI am currently developing a wearable board (WB) that integrates NFC communication and wireless charging features. For this design, I am considering using the ST25DV64KC as the NFC Dynamic Tag and the ST25R3916B as the NFC Reader/Transmitter.I work for a design company based in Colombia, with mass production planned in China and Taiwan. I have reviewed the document AN5918, which appears to be focused on NFC-based wireless charging designs.I would like to request kindly:Access to the full AN5918 application note, andDetailed guidelines or parameters for implementing the DC r

Questions about the Transparent mode.The ST25R200 is cheaper then discrete components for a non-standard RFID interface ( at 848 KHz subcarrier )Questions about the transparent mode:I am struggling with the receiver in this mode.( An example with signal values from an oscilloscope, to just send a command and get the response would be enough.I assume the reponse being 10% modulation from the tag using the 848KHz subcarrier, for 102Kb/s standard bitrate. )Could someone give an indication about the signals coming out of the transparant mode.Is there a document?Just showing the TX being used to 'send a command' and the response on the receive channel would be really helpfulIn the picture in the datasheet, the receiver does have a 848KHz ( fs/16 ) receiver, followed by a dual ADC.( Is this a real ADC or just a comparator ? )( I and Q , I assume what is their sample rate ? 848 Khz, are these one bitter ? See questions fur

Hello, I have a problem after updating the system to Android 16. Before, everything was great. I have a custom application to work with ST25DV04KC. Now, the NFC service crashes before connection, and the system app opens NDEEF. Only on the first "tap," after turning NFC on/off, the connection is correct. Is there any workaround before they change it in Android? Thanks for any help.

Hi Team,I am working with the STEVAL-D25R16B kit and have encountered a critical discrepancy in detection range between the embedded "Reader/Writer" demonstration and the PC-based USB mode.Here are the test results using ISO15693 tags:The Setup:Tag A: Placed at 2 cm (Near)Tag B: Placed at 10 cm (Far)1. Testing in USB Mode (PC GUI):Result: SUCCESS.The reader successfully detects both Tag A (2cm) and Tag B (10cm).2. Testing in Standalone "Reader/Writer" Demo:Result: FAILURE.The reader detects Tag A, but fails to detect Tag B at 10cm.Tag B is only detected if moved closer to 5 cm.

HelloI want to emulate NTAG215, but I don't think the CE corresponding to T2t is in RFAL. I'm not sure if I understand it correctly, but,First of all, the status of my code is as follows.FreeRTOS-based ListenerCylce pollingEmulate nfc contextUID, SAK, ATQA are read, but RFAL_NFC_STATE_ACTIVATED does not seem to receive T2t commands from the reader without a single turnIf necessary, I will upload a portion of the code I am working on.Help me!

I'm attempting MIFARE communication using the ST25R3916 microcontroller, but the NT does not return during the AUTH communication. I successfully obtained the UID, and after tag selection, the SAK returned as 0x08. However, after sending 06, 01, the CRC error in the 0x1C register is set. The NT should then return from the tag, but not a single byte is returned.The AUTH sequence is described below.DIRECT_COMMAND_SEND(0xDB); //Clear FIFOREG_WRITE(0x22,0b00000000); //TX BYTE Number(MSB)REG_WRITE(0x23,0b00010000); //TX BYTE Number(LSB)BSS=0; //SS=0__delay_us(10);SPI_send(0b10000000); //FIFO write commandSPI_send(0x60); //FIFO data1SPI_send(0x01); //FIFO data2BSS=1; //SS=1__delay_us(10);DIRECT_COM(0xC4); //FIFO Transmit With CRCAfter this, a CRC error occurs, and NT doesn't return a single byte.Does anyone know why?  

Hello @all, I've downloaded ST25DVCryptoDemo for iOS from here, in order to take a look into the demo code for a new project.Once I've tried to build the Demo app I've got a big amount of errors. In fact the console gave me this message "too many errors emitted, stopping now"Could someone please help me to fix those issues and make everything works properly?I've also download the ST25SDK

Hello,I am using the ST25R3916B reader on a custom board to read NFC-A cards. I first experimented on the X-Nucleo-nfc08a1 expansion board connected to esp32-s3 devkit. I modified the RFAL library a bit to fit my needs and kept most registers at their default values. With this setup I was able to communicate with an NFC-A card perfectly.On my custom board, which is powered by 3V, I am able to communicate with the reader: read IC ID, read/write registers, receive interrupts. But I still haven't been able to communicate with the card. I receive no ATQA for my REQA. In fact no rxs or rxe interrupts are being raised (txe interrupt is being raised after sending direct command Send REQA). Code used on X-nucleo-nfc08a1 and custom board are exactly the same, except they have different SDA and IRQ pins.I am still checking out the hardware design to check for any issues, especially with the antenna matching circuit. In the mean time I wanted to check a few other thin

To realize carkey function, what conditions do card readers need and what aspects of hardware will be measured?

Hello everyone,I just received the STEVAL-25R200A evaluation kit and I have a few doubts.1. Can I connect this board directly to another MCU?2. If yes, are the SPI pins available on the PCB?3. I found that the board uses an STM32G0B1KEU. Should I develop and test the firmware for this MCU using STM32CubeIDE first, and then later port it to my custom board?Thank you! 

Hi,The ST25DV supports I2C speeds upto 1MHz, for which the datasheet has mentioned the rise and fall time using the RC time constant of <150ns according to I2C standards.We are using it at 100kHz only but there is no mention of rise and fall time for 100kHz ( acc to I2C standard it should be <1000ns), and the following point is mentioned in datasheet as attached.Does this mean that ST25DV supports only <150ns rise and fall time even if it used only at 100kHz? 

I am using ST25DV04KC tag and using the V_EH pin to power the VCC of the tag only( It will generate around 3.3V which is enough to power up the tag in I2C mode I believe) . I am looking for guidance on the maximum pullup voltage on the I2C and GPO line from an external rail of around 3.6V, if it is okay? what can be the max voltage on the I2C and GPO pins? is it independent of VCC or dependent on VCC?

 Hi,I need to write the same kind of NDEF data to ~20 different NFC stickers placed on a panel. The idea is to have ~20 small antennas, select one at a time, and write to the sticker sitting above that antenna.Questions:Can I do this with X-NUCLEO-NFC12A1 + STM32 by multiplexing the RF path (switches/decoder → select 1-of-20 antennas)?Any recommended switch/multiplexer parts or reference designs for 13.56 MHz?What are the practical limits on antenna count and cable/trace length when switching like this?Do I need individual tuning (matching caps) per antenna position?Is there a better Nucleo shield for this use-case (e.g., higher RF drive) or is NFC12A1 enough?Goal: operator chooses pad 1…20, we write an NDEF, verify, then move to the next pad.Kindly advise—exampl

Hello,I hope this is not a duplicate but I didn't find a similar issue.I'm developing for my company an Android app using the STSW-ST25SDK001 - Software Development Kit for ST25 Tags and Dynamic Tags (https://www.st.com/en/embedded-software/stsw-st25sdk001.html).To use your SDK i have to include two artifacts:st25sdk-1.13.0.jarst25_android_reader_interface-1.0.12-release.aar, specific for AndroidI see that the AAR includes an "application" tag in its AndroidManifest.xml, even if it's only a library and does not provide an Application class:<application android:allowBackup="true" android:label="@string/app_name" android:supportsRtl="true" >

Hello ST Community,I am using a STEVAL-25R200A to do tests with the ST25TV02KC.I am trying to rfalST25xVPollerPresentPassword, with a pwdNumber of 0x00 to enter Configuration Session (As described in the nfc tag datasheet), But keep getting error 5, even though I am passing the default 32-bit password.I am using this function:ReturnCode ST25TAGS_TVC_OpenSecuritySession(const uint8_t * uid, ST25TAG_TVC_SecuritySession_t sessionType, const uint8_t * pPassword) { uint8_t pwdNumber; uint8_t pwdLengthInBytes = 4; ReturnCode errCode; uint8_t rxBuf[ 1 + 2 + 2 ]; /* Flags + Random Number Data + CRC */; uint16_t rcvLen; uint8_t updatedPassword[8]; switch (sessionType) { case CONFIGURATION_SECURITY_SESSION: pwdNumber = 0; break; case USER_AREA1_SECURITY_SESSION: pwdNumber = 1; break; case USER_AREA2_SECURITY_SESSION: pwdNumber = 2; break; case SINGLE_USER_AREA_SECURITY_SESSIO

Hello ST Community, I am currently working on an in-house NFC anti-counterfeiting authentication platform for my clothing brand. The system is being built using the ST25TV02KC tag, and we are now in the stage where access to AN5580 – “TruST25 digital signature for ST25TV512C and ST25TV02KC devices” is required to complete our provisioning and backend integration. I have already submitted a request via ols.st.com, but after checking the forums I noticed that many users were informed that access to AN5580 must be coordinated through a local ST sales representative. However, the official contact listed for Mexico appears to be outdated (phone number no longer active, and the physical office shows as permanently closed on Google Maps). Because of this, I am unsure how to proceed or who to contact for this restricted document. Thank you very much for your support.

Hello  Can someone help with locating software documentation for the implementation of Anti Cloning Verification using the TruST Digital Signature with STTV25-02KC chips. I've found plenty of sales & marketing materials describing it on the ST website. However there seems to be nothing that is Specifically Code Related existing that can assist our developers in actually employing it.  ( I am told that documentation for this is absent within both Apple and Android SDKs.) Additionally, we may be retaining an experienced advisory, so please say "Hello" if you're a match.  Regards ,Andrew Rae&nb

Hello,I developing a board with ST25R3911B and STM32F103RFT6. Im trying to read Chip ID, but it always reads 255. On the scope i can see CS pin driven low, clock and MOSI line outputing signals, but no response on the MISO line. The solder joints look ok. Im attaching schematics, board project, soldering under the microscope and scope traces. The communication works in loopback (when i physically short MISO and MOSI).

Hi I am planning to evaluate the ST25R3920B for NFC reader applicaiotn in automotive.I only find STEVAL-25R3916B kit on your website, based on your presentation file, this kit is also valid for ST25R3920B, it is right?if not, where can I find the suitable evaluation kit for ST25R3920B?Thanks,Leo

I am finding it difficult to get clear direction on best practices for how to do the layout for CSI and CSO.  App note AN4985 says that "parasitic capacitance to ground should be made as small as possible", and then recommends using a coupling capacitor up to 2.7pF (C_COUP, between the 2 electrodes, I think... not sure).  But, on the other hand, the reference design (Discovery Kit ST25R3911B-DISCO) has no C_COUP shown in the schematic -- maybe because there is enough capacitance already between the electrodes? --  and it has an RC of 1k and 12pF on both CSI and CSO, without explanation.  It is not clear why we want to minimize parasitic capacitance to ground, but then we deliberately add 12pF of capacitance to GND.  Some clarity on the design goals for CSI and SCO would really be appreciated.  thanks! 

 Hello, the NFC reader I use is ST25R100. My card is Mifare Desfire EV2. Does it support it?My configs are like this, but it doesn't read the uid. It reads the NFCA type correctly. 

Hi,   I am currently working on a use case involving the ST25DV16K NFC and Phytec Pollux board for Wi-Fi credentials sharing and connectivity. I came across the following Arduino library for ST25DV:https://github.com/stm32duino/ST25DV   I would like to clarify the following points: Can this library be used for I²C communication between the ST25DV16K NFC and the Phytec Pollux board? The stm32duino/ST25DV library lists supported architectures — would it be compatible with the Pollux board, which is based on an ARM 64-bit architecture? If not compatible, could you please share if there are any supported libraries or APIs for ARM64 platforms? Looking forward to your guidance

Hello,We want to implement the new ST25100 or ST25R200 in our project. There we need to have 8 RFID antennae to read and write to 8 NFC Tags as fast as possible. The NFC Tags will be placed on a drawer, so all 8 Tags are in the range of the antennae at the same time.We already did a prototype 1 years ago with ST25R95 (CR95HF). There we had one stm microcontroller and 8 ST25R95 connected by the same SPI. The used RFAL firmare has only one instance of ST25R95 and we had to startup and initialize every chip one by one to read out the tags. This setup needs time to start every chip and reading the tag. At problems with initializing, resetting this chip was very bad, but the new chips have a reset line.The 8 RFID antennae and ST25R95 have a distance of 80mm next to each other, so we have a large distance from the first to last chip and antennae. The antenna is not an integrated PCB antenna. Every antenna is connected by a 200mm cable to the PCB.

The subject line says it all - any help will be appreciated