ST25 NFC/RFID tags and readers

Hi everyone,I'm currently working on reading and writing the registers of the ST25R3916 chip, which is mounted on the NFC08A1 board. However, I'm running into some issues with the I2C read and write operations.Below is the code I'm using to attempt reading from the chip: while (1) { uint8_t value = 0; HAL_StatusTypeDef status; status = HAL_I2C_Mem_Read(&hi2c1, ST25R_ADDR, 0x000C, I2C_MEMADD_SIZE_16BIT, &value, 1, 1000); switch(status){ case HAL_OK: UART1_WriteString("HAL_OK I2C\r\n"); break; case HAL_ERROR: UART1_WriteString("HAL_ERROR I2C\r\n"); break; case HAL_BUSY: UART1_WriteString("HAL_BUSY I2C\r\n"); break; case HAL_TIMEOUT: UART1_WriteString("HAL_TIMEOUT I2C\r\n"); break; } } For reference, "ST25R_ADDR" = 0x50.When I flash the micro (NUCLEO-U575IQ), the code keeps printing HAL_ERROR on the serial monitor, and I can't figure out why.From the ST25R3916 datasheet, I see that the I2C address is supposed to be 0x50, and I'm simply trying to re

Hello everyone, in a project we are using the ST25R3916 chip to read RFID cards. To do this we are using the sources of the STSW-ST25R-LIB library. If the ST25R3916 sets its IRQ output, the routine st25r3916isr() is called. In this ISR the interrupt registers are read via SPI. void st25r3916Isr( void ) { st25r3916CheckForReceivedInterrupts(); ... } void st25r3916CheckForReceivedInterrupts( void ) { ... /* In case the IRQ is Edge (not Level) triggered read IRQs until done */ while( platformGpioIsHigh( ST25R_INT_PORT, ST25R_INT_PIN ) ) { st25r3916ReadMultipleRegisters( ST25R3916_REG_IRQ_MAIN, iregs, ST25R3916_INT_REGS_LEN ); ... } ... }As other components can be connected to this SPI bus, no SPI communication is alowed in the context of an interrupt, as otherwise 2 SPI operations can overlap and this can lead to undesirable effects. How can I get around this problem? Is there some kind of polling mode or how can I move the SPI operation into the context of the main l

Hi,Is there any NFC chip that is capable of emulation NFC-V Tags (ISO 15693)?Thanks. 

I connected a Raspberry Pi 3 to the ST25R3911B-DISCO and used the Linux driver suggested by ST.   However, I haven't been able to successfully detect the IRQ despite following the setup.   Any suggestions on troubleshooting this issue?

I'm working on emulating a T2T with my device. It successfully makes it through automatic anticollision, then starts looking for commands. When I see 0x30 0x00, I go ahead and send the first 16 bytes, but the reader does not react or show the read data.Right now I'm thinking that I'm transmitting wrong while in Listen Mode. The RFAL never does T2T emulation, so I don't have an example there. Right now, when I see a 0x30 command, I do the following:Send command CLEAR FIFOSet Num Tx Bytes 1 to the MSBSet Num Tx Bytes 2 mask 0xF8 to the LSBWrite the data to the FIFOSend command TX WITH CRCIs there a different way to do it in Listen Mode? With T2T Emulation the chip's field will never be on, but I don't see a way to explicitly modulate a response. The first 16 bytes are shown above, with the CC 0xE1 0x10 0x3F 0x0F. I do also have an empty NDEF TLV and the Terminator TLV, but no memory regions beyond the first 4 blocks are attempted to be read.Also - I couldn't find any information on the I

Hi I am in the the process of trying to replicate the STEVAL-SMARTAG1 board but with different sensors. I am new to making PCBs so I don't know if I've overlooked important considerations. A goal of my project is to remove the battery to reduce the bulk of the final PCB. I replaced the battery power with a connector pin to provide power during programming. I have been using an STM32 Nucleo board with a STLink adapter to power and program. At this point in time I am having trouble communicating with my PCB despite having all the components populated. I have checked the soldering and connectivity.  I am receiving the following error: "The interface firmware FAILED to reset/halt the target MCU". I observed the same error when no battery was inserted for the SMARTAG1 but I believe I am supplying sufficient power through the supplementary connector pin on my design. Could I please get some help for what I should try to resolve this problem.  I have attached the Kicad schematic and

I am designing a custom board using your ST25R95 chip. To design the matching network given the antenna parameters, which I show in the following picture:   The tool you recommend (ST25R95_EMI_FILTER_CALCULATION) for the matching network returns me negative capacitance values. To overcome this problem I chose to reduce the value of the resistors on the receiving path. This is something I have not seen done in any other example so I was wondering if it is permissible to do this (changing RRx from 330 Ohm to 1 Ohm). I attach the screenshot of the output of the matching tool: Thanks for your attention, Luigi 

Hello, I’m working on a project with an X-NUCLEO-NFC08A1 board to use it as an NFC Reader. Specifically, I have an NFC TAG, and I want to use the NFC08A1 board to read and write to this TAG.I’m currently looking for some example code to help me use the NFC08A1 board as a reader.Do you have any code suggestions or any links where I can find reference examples for this?Many thanks in advance!!Best Regards

I am working with the ST25DV tags.  I have generated a capability container, TLV Header and Terminator and construct a well-formed NDEF message with 5 records.  I am able to read/write single/multiple blocks and perform most actions that i need in interacting or editing the NDEF records themselves.I am now trying to split the user memory into different sections so that I can lock down RF write of the first 3 records and leave the last 2 records open for both RF read/write.I am currently testing on Android and attempting to open a configuration security session.  I am using the react-native-nfc-manager to help me handle some of the lower level aspects of working with these tags.Here is a simplified version of my function:async function openSecuritySessionAndroid() { if (promptRef.current) { await NfcManager.cancelTechnologyRequest(); await sleep(100); promptRef.current.show('Ready to Scan'); await NfcManager.requestTechnology([NfcTech.NfcV]); } try { const iso156

Hi ST team, We are going to use the ST25R3916B chip in our project to design NFC reader. Due to mechanical design constraints, I have to place the antenna in separate PCBA near NFC tag. I would like to know how should i connect my RF output from reader board to antenna. Distance from reader PCBA to antenna required around 30-40 cm. Can you pls suggest will this solution work and what type of cable is required. Also what specific design considerations i have to take care?

Hi,I am using the ST25R3916 (NFC06A1 board) to perform NFC read/write operations with passive tags and Android-based devices (essentially used as passive tags without any background apps). Recently, I tried to use an iPhone, but I can't get it to work.Do you have any ideas or suggestions?Thanks  

Hi, I was just wondering if someone knew what n.m. meant on the schematic of the SMARTAG1. I assume do not populate but if so what purpose do these components serve if populated? Thanks.

I'm fairly new in NFC technology and was trying to implement a simple project that uses the ST25R3916 to write a message in a specific memory location of the ST25DV04K and then locks write access to that specific memory location. I'm using an adapted version of the library "en.x-cube-nfc6". I can read/write messages without any problem, but when I can't seem to find any function in the library to block the write access that works. I'm using  "ndefPollerWriteBytes(ndefContext *ctx, uint32_t offset, const uint8_t *buf, uint32_t len)" to write, which works fine, butif I try to use "ndefPollerSetReadOnly(ndefContext *ctx)", it returns error 33 "Wrong State". Am I doing something wrong? Should I use different functions? I'll append a picture of my code, which stems from the demo usage of the library. The purpuse of the code was to write 4 bytes, lock access then try to write again (which sould fail, I guess).

Hi, We are attempting to use the ST25R3916 and the RFAL middleware (NFC08A1 demo board) to read Picopass cards using the ISO14443B standards - however the cards we have (that we know work with older Picopass readers) are not detected. I understand the pico cards operate in a non standard way however I could do with some pointers as to where to look to be able to support reading these cards as well as more standard ISO11443 A/B cards.Using the demo software NFC08A1 Polling Tag Detect - the software simply doesnt recognise these cards at all.

Hello everyone,I'm experiencing issues with the "Write Multiple Blocks" command on the RF side using the ST25DV64KC.I’ve tried using this command through the ST25 Android app, specifically using the "Send Custom Command" feature. Here’s how I configured the command:Option Flag: EnabledAddressed Mode: EnabledSelect Mode: DisabledHigh Data Rate: EnabledFormat Extension: Disabled"CMD" Code: 0x24Data: 00 01 11 11 11 11 22 22 22 2200 indicates the First Block Number field in the request (Block 00).01 indicates the Number of Blocks (01 = 2 blocks).11 11 11 11 22 22 22 22 is the data to be written into the memory blocks.However, when I send this command, the Android app returns an "ERROR CMD" message.I’ve also tried different configurations (e.g., disabling High Data Rate, using different data values, etc.), but I get the same result each time.I want to note that the single block write command works perfectly and allows me to write one block at a time without any issues.Does anyone know what

what is A/D register for? when i bring the st25r tag(sticker one) near the st25 nfc its value changes. And how is interrupt generated? what are the values of registers to be set in order to read a NfC tag?pseudo code for it. 

Hi,For our project we are trying to read out the first 100 bytes of a ST25DV tag. This tag is inside our products which are tested in production line. The test results of these test are written inside the tag by I2C. We are building an end of line test to make sure every piece is tested and collect test results.We are using MB1054B demonstration board as our reader. We program directly in the STM32F103 MCU which is on board and we altered the board so we can talk UART to the CR95HF board.For our first try we use a ST25DV_Discovery_ANT_C5 board to make sure we have working hardware and proper reading distance. We can properly reset the the CR95HF by toggling the IRQ pin.After that we send the 0x55 command to see if the CR95HF is responding.uint8_t commandECHO[] = {0x55};After that we send the IDN command to check if everything is functional as expected.uint8_t commandIDN[] = {0x01, 0x00};Then we set the command protocol to ISO/IEC 15693 because our tag (ST25DV) is ISO/IEC

Hi ST CommunityI have a ST25TV tag,The UID is E0 02 08 03 8F 65 C9 F5(8bytes)I use the board of NUCLE0-NFC08A1 and the demo in NFC6 generated by Cube MX.I can read the relevant information of the card through the SPI provided in the demo and  than print the UID of the card to the serial port（Figure1）,but I am unable to see the waveform related to the tag's UID on the logic analyzer. Could it be because the UID is encoded during transmission?I cannot find the corresponding UID in the waveform diagram.How can I obtain the UID by analyzing the waveform? Figure1：FIFO data:waveform：   

At the beginning of the program, I first performed a write-then-read operation on register 00 using I²C timing. I wrote 0x04 to register 00, and this worked correctly. However, when I used the same method to perform a write-then-read operation on register 03, I wrote 0x07 to register 03,but when I read register 03, the returned value was 0x08.  Can you tell me why this problem might occur?What are the possible reasons?

As we've been integrating the ST25R3916 into our final hardware, there's been an issue with the Adjust Regulators command. On external supply power, the command works without any problems. On some (not all) of our battery-powered units, as tested in the field, the Adjust Regulators command never returns, so NFC is unable to initialize. The weird part is that when a tag is held inside the field during initialization, the command completes without any issues and NFC initializes. I assume this is because the tag increases impedance while it pulls power, but this should not be necessary and our system is able to handle the current. The two traces below show initialization with a tag in the field (first), and failure without a tag in the field (second). At no point does the 2.8V rail dip, so I don't see this as an issue with the power supply.VDD_2.8 (green)VDD_D (red)VDD_AM (blue)VDD_RF (yellow)I tried with every value of RFO driver resistance, and none worked. Setting the regulated voltage

I've been working on implementing tag emulation on my device with an ST25R3916 and have run into a problem. First - the code is currently completely separate from the tag reader code, including init, so it's not a matter of not changing modes properly. And this is with my own codebase, not the RFAL. I'm using a Flipper Zero (which actually uses an ST25R3916) to test with since I read other posts about a phone being too fast, and it is specifically in the ISO-14443-4A mode. The Flipper Zero works with the NUCLEO-L476RG + X-NUCLEO-NFC08A1 tag emulation.I have been closely following the RFAL as I implement my own version, and it only gets part of the way through anticollision. When I put a reader over the antenna, I see EON and RXE_PTA without any issues, but I never get a WU_A interrupt. I have PT_MEM populated with the same values as the RFAL (see pic 1), and follow all the same configurations except for the repeats since the RFAL is doing a lot of mode switching. When I do get an RXE_P

Hi AllI am developing a simple app for a bespoke board using the ST25R3911B, that just has to poll for an ST25DV04KC Type 5 tag, and read/write using NDEF. I'm using STM32CubeIDE, adding NFC to an existing project that uses FreeRTOS, and already has the basic hardware init, debug logging etc.Just checking which is the quickest way to get started?I think my options are:-X-CUBE-NFC6 - easy to add to my project using cube, but not clear if it supports ST25R3911B (my understanding is the ST25R3911B is a cut down version of ST25R3916?).X-CUBE-NFC5 - clearly supports ST25R3911B but doesn't appear in cube, is it superceded by NFC6?STSW‑ST25R015 - again clearly supports ST25R3911B, but I've not used this style of ST library before, looks like a lot more work to get started, compared to X-CUBE packagesI must admit I get fairly confused by these various ST software packages, and the best/easiest way to add them to an existing STM32CubeIDE project. For example, if using X-CUBE, should I use (and

We make a credit-card size Data Acquisition device which transfers data over Bluetooth to our iOS or Android App running on a phone which can be optionally attached to the phone.  The device has a PIC Microcontroller with an I2C interface and is powered by a 700 mAh Li-ion battery. We want to replace or supplement the device's Power Button so the device can be powered-on with an NFC tap to the phone that is running our App.  We can add a Dynamic NFC Tag with loop antenna to do this.Do you have a reference design showing how to do this?Is there a demo board (perhaps with Arduino) that supports Power-on Reset using a Dynamic NFC Tag?

We are using the NFC Tag Chip ST25DV04K & ST25DV64K for a customer project. The NFC Antenna is on the same PCB as the Tag Chip. Variant with ST25DV64K, Antenna Size approx 19x44.5mm Variant with ST25DV04K, Antenna Size approx 66.75x24.5mm The antenna is well matched to the center of 13.56Mhz (measured in the plastic housing and final installation situation). There is a grounded metal plate around 20mm below the PCB. Our goal is to reach a reading distance of about 40 – 50mm with commercial Smartphone readers, because the closest distance can be 35mm (the PCB is deep in the housing placed).With iPhone SE we get a reading distance up to 50mm with smaller Antenna and up to 70mm with the larger Antenna.We tested with another Smartphone like Samsung Galaxy A14 and A15. With A15 we never get a successful communication at the minimum distance of 35mm. We have to place the Smartphone inside the housing with a distance of approx 10-20mm to get a successful communication.

Hello,I am trying to use RF with iOS and Android to write into the memory of the ST25DV04KC. Reading is not a problem, but the difficulty is the protection. There are two areas: Area 1 is only used for the NDEF message and is locked with Password 1. Area 2 is the data area, which is also protected with Password 1. So, reading does not require a password, but writing with RF into the area does.I studied the datasheet, and it looks very confusing. I can't figure out how to handle writing multiple blocks into an area that is password-protected.Here is more information: I initially used the Req_Flag, which is 0x62 or 0x22, with the ID of the chip. The command for multiple block writes is 0x24, and the starting block is 0x0A (which is Block 11). To write two blocks, I use 0x01 (because the number of blocks is -1). I also saw that the maximum number of blocks is 4, so the maximum number of blocks to write in the data area is 0x03. When I issue these commands with the NFC Tag app, it says tha