ST25 NFC/RFID tags and readers

Hello,I'm developing custom NFC modul with CR95HF and I'm having difficulties with reading ISO 14443-B card. So far I've built a hardware prototype and written a simple python class and script for controlling CR95HF protocol. With ISO 14443-A I'm able to obtain cascade level 1 and 2 UIDs but Type-B doesn't respond to REQB message.log of Type-B communication with commentaries:> 0x55 # using echo as wake puls> 0x55 # echo< 0x55 # echo back> 0x02020301 # protocol select B, 106 up, 106 down, CRC append< 0x0000 # ok> 0x0903680001 # Write the ARC_B register index at 0x01:< 0x0000 # ok> 0x0803690100 # Read from ARC_B< 0x000120 # a little weird answer, datasheet says 0x2F is default value for Type B> 0x0403050000 # REQ B - all families, param n=1 - card should send ATQB without waiting for slotmarker< 0x8700 # no cardI've also tried protocol select as:> 0x020403010180 as in dataasheet example without luck and all combinations of possible gain and modula

Hi,i'm trying to perform a communication with an ISO14443-A smart card using the X-NUCLEO-NFC06A1 expansion board. The smart card supports the following bit rate: 106, 212, 424 and 848 kbit/s according to the ATS received. If i negotiate with the smart card a 848 kbit/s bit rate both in transmission and reception and i try to send an APDU, the rfal library returns an ERROR FRAMING in reception. In particular the error is returned by rfalTransceiveRx() method implemented in rfal_rfst25r3911.c file: case RFAL_TXRX_STATE_RX_WAIT_RXE: irqs = st25r3911GetInterrupt( (ST25R3911_IRQ_MASK_RXE | ST25R3911_IRQ_MASK_FWL | ST25R3911_IRQ_MASK_EOF) ); if( irqs == ST25R3911_IRQ_MASK_NONE ) { /*******************************************************************************/ /* REMARK: Silicon workaround ST25R3911B Errata #1.1 */ /* ST25R3911 may indicate RXS without RXE afterwards, this happens rarely on */ /* corrupted frames. */ /* SW timer is used to timeout upon a missing RXE */ if( rfalT

Hello erveryone,I have a question regarding the X-NUCLEO-NFC03A1. I want to use the board with NFC Tags Type 5. The board version with the ST25R95 should be able to do that, but it seems like theres only the version with CR95HF available for sale at Mouser etc.. How can I get my hands on the ST25R95 board? And the general description says that X-NUCLEO-NFC03A1 is only able to read up to NFC Tag Type 4 is that also true for the ST25R95 version?Thanks in advance for your answers :)

I've been working successfully with the STM8 MCUs, using ST-LINK, building, debugging. But I so far can't figure out how to get started building for the STM32L4x6, which hosts the ST25R3911-DISCO board.  Can't even pin down an IDE yet.

I need to read the NFCTag ID but I haven't worked out how as yet. Can anyone point me at an example?David

Hi ST Community,I am having trouble to make a NDEF record in a ST25DV16k tag be recognized by Android 8.0, I already read both AN4910 and AN4911 and understood the limitations in Android 8.1 regarding the NDEF and CC headers, but my problem is that even when I clone the memory content from a working ST25DV04K tag into a ST25DV16K, the 16K tag is still not being recognized by the Android 8.1 smartphone, here are the memory contents of both tags:  As can be seen on the images, the whole content of the 04K tag was mirrored into the 16K tag, including the CC file and the NDEF header, so for all intents and purposes the 16K tag must be interpreted as a 512 Bytes tag, and the NDEF record (ST website) must be correctly identified, right?The Android 8.0 phone correctly identifies the 04K tag record and opens the website, but when the 16k tag is presented it only gives the option to open ST25 app, showing that the NDEF record was not recognized by the android system.In a smartphone wi

Need help!I am unable to write or read an RFID TAG using the st25ru3993-eval. I'm not finding much information!Can someone help me?

Hi all, When ST25RU3993-HPEV, what are the accessories provided along with the EVM could not find the information in the portal. Let us know any where it is specified. Specification and datasheet of antenna used in EVM (Provided along with EVM)

..

Hi,I use a X-NUCLEO-NFC06A1shield and a Nucleo-476RG to read a NFC chips ( M24LR64D-W or M24LR04).For my test I use the demo program from ST provided with the shield.I want to read 32 blocks (a block is 4 bytes) with the function rfalNfcvPollerReadMultipleBlocks.If the numOfBlocks parameter is set to 31 the function works correctly.If the numOfBlocks parameter is set to 32 the function returns ERR_REQUEST.Could you help me to resolve this issue?Thx & RegardsNigorosNote 1: The chip M24LR04 is on a red board M24LR-discovery.Note 2: To read the chip M24LR64D-W I use the function rfalST25xVPollerM24LRReadMultipleBlocks with the same issue.

Hi. I'm getting weird data when reading UID from ST25DV04K via i2c.Tag id should be 0E 02 24 00 F3 DF 43 BDWhen reading via i2c HAL_I2C_Mem_Read( nfcI2c, ST25DV_Address_E21_read, UID_ADDRESS, 2, nfcUID, 8, 0xFFFFFF );i'm getting 00 02 24 00 F3 DF 43 01 ( first and last byte are wrong )When reading via i2c byte by byte for( int k = 0; k < 8; k++ ) HAL_I2C_Mem_Read( nfcI2c, ST25DV_Address_E21_read, UID_ADDRESS + k, 2, nfcUID + k, 1, 0xFFFFFF );00 00 00 00 01 01 01 01Tried 100k and 400k speeds.Logic analyzer shows the same Android app reads UID via RF correctly

Hi ,is there any user manual " how to connect ST25RU3993 UHF module via raspberry pi " please send if any documents

I'm picking up a design from another engineer, and we've noticed the most recent hardware revision of our board has a sense range of approximately half of the previous version. We're using the same antenna and matching network, same layout and components. There is a minor change in the stackup which I'm not discounting, but I'd like to find out if the 3911 has debug facilities that would help me see what it's struggling with.What facilities does the 3911 have to diagnose read issues? I see that it has some trim pins that it presumably uses to try to maximize the power transfer, does it have any registers I can access to see if it's running out of headroom trying to read the tag? Are there any app notes or diagnostic routines I can read?

Hi,I am using the following configuration.protocol :- ISO/IEC 14443 Type A tagsTimerW value :- 0x58Modulation Index and Receiver Gain :- 0xD0Reader Antenna DimensionsL=28 mmW =28 mmNo of turns=3 turnsFind attached diagram for designator referenceC11=180pFC12=180pFC2=180pFI am also using an Low pass EMI filterL01=L02="Part number=742792042"C01=C02=180pfI have tried fine tuning with various capacitor combinations.I got slightly better range of 1.3 cm when replacing C11 and C12 with 1nF capacitor.otherwise the range is around 0.9 cm.For Tag i am using Keyfobs tokken type tag.Please help me understand how to obtain greater range?Is it by changing the modulation and gain configuration?/tag used?/capacitance values? or should i redesign the antenna.?I designed a small antenna as per edesign suite to fit CR95hF and antenna in my 30mm x 30mm PCB such that the circuits and components are in the centre of the PCB while Antenna is on the outer circling the circuit.Kindly help me out.RegardsGokula

Hello,we have developed a custom antenna and modified the reader circuit a bit to our needs, but are heavily struggling with reading performance. While we were able to read up 17cm above the MB1441-C Discovery Board using ISO15693 tags, our own circuit struggles to get even close to 5cm when using the MB1396-B, when using our own MCU it gets even worse (below 1cm). The layout and design is close to the reference one. So we found an antenna expert doing some simulations for us, while we try to find the root cause as well. In order to do a model simulation we would like to test the reading range with 14443 tags at a set bitrate of 848kbit/s inside the GUI. How can I set the bitrate to a specific value and run a continuous scan on the RF Field?What is the best place to start to measure and improve the design to find the root cause? What should we measure and what are the expected values in order to tune the antenna properly?Cheers,Philip

Posted on June 17, 2014 at 11:27Hi I'm using the M24LR04 in Harvesting Mode to supply an STM32L151. When the uC powers up, it reads data from an sensor and write them to the M24LR. This is than read from an NFC Handheld.My problem is, when the Handheld approaches, first the M24LR starts to communicate with the handheld, before the uC powers up and refreshes the Data. So i want to disable the RF communication until the STM is on. I know there is the M24SR devices which had the RF disable Pin, but unfortunately my App is ISO15693 (and not  ISO 14443).... Is there another possibility... Thanx regards otmar #vout #rf-wip-busy #m24lr #m24lr

Hi all,I put the EH_MODE to 0 to activate Energy Harvesting. The EEPROM is filled with zeros, so that the smartphone cant read a NDEF message but trying it for some time. I am measuring the voltage on EH, in parallel i added a LED to visualize the EH function. The LED fluctuates, voltage is not stable. Its a fast blinking LED. Is it because the Phone tries to read the NDEF and therefore its going up and down? How do i active continues EH then? Is there a certain App needed? how can i force continued EH for some seconds? If i am reading a message from the tag, thats very fast (this is the reason i put zeros in the storage, to extend the time reading/trying and therefore seeing the LED blinking for longer).Could someone give me some hints? I guess some basic understanding is missing ...many thanksI am using ST25DV ANT7 board (14x14mm Antenna)17.01.2021: I added a short video for explanation.I guess what i see is the "Reader to tag" modulation, please see picture attached. How can i force

We are trying to implement UART functionality in ST25R3911B-DISCO board.In firmware side we have implemented all the functionality on the board and it is working properly, we have tested it by sending data (formed using frame structure) by serial terminal to the board and receiving proper data frame from the board to the PC.But we are facing issue on the host side of the software we are trying to implement. We have ST25R3911DISCOComm.dll file which implement host side of code. All the code related to device communication is implemented inside .dll file which can't be changed without source code. Is there any way to get .dll source code?Also is the source code of QT GUI(STSW-ST25R001) of the board is also available to download?Further we have planned to implement wifi over this board using uart connectivity.@Ulysses HERNIOSUS_O​ 

HiI have discovery M24LR and CR95HF demonstration board, I read and write data by ST application software successfully but when I use DLL file and LABVIEW software according to AN3954 I read just strange data, for example when I read data from tag I read:800D00FF214A886CE15902E05C5700according to page 42 of AN3954 the main format is correct but I can't understand the read data, my goal is to read the whole data of EEPROM

I am not able to find proper examples and/or documentation on how to add RAFL to my project.Looking into the rfal.chm file in RFAL there is an example but it does not work for me ?When I am looking in X-CUBE-NFC5.chm there should 4 examples but its empty.The documentation for how to add it to a project is limited. Is there a source code for the ST25R3911B discovery GUI or even better documentation for it as well.Thanks,Noam.

Hello,Im trying to read data from a M24LR64E-R tag with password.So, Im using customCommand() function with these data :flag : 0x0acommand : 0xB3payload : bytes from password This command works on Android but on ios I receive this error :[CoreNFC] 00000002 83601300 -[NFCTagReaderSession transceive:tagUpdate:error:]:710 Error Domain=NFCError Code=100 "Tag connection lost" UserInfo={NSLocalizedDescription=Tag connection lost}It's the same with readSingleBlock command but I received the same error.Do you have an idea ?

Hi,I am receiving the wrong CRC16 value from the tag when it is answering error flags, for example:2020-12-16 14:01:18.143 writeMsg >> 02AA0200AA2020-12-16 14:01:18.148 writeMsg << 0F0F68EEI forced an error there (writing to the MB when it is off) and the tag correctly answered 0F0F, but the answered CRC (68EE) is not correct, according to the standard it should be 0x7478What am I doing wrong here? Is the tag really answering wrong CRCs for error codes or is there any other reason why this value is different?Thanks, Gustavo

For data exchange between ST25DVxx with an Android smartphone we would like to use NDEF (NFC Data Exchange Format) messages. Will it work?  NOTE: This question and answer originated from a customer support case which was handled by us. We regularly review support cases and add any helpful ones here for all to benefit from.

I have purchased "X-Nucleo-NFC03A1" NFC reader evaluation board. Can I use Arduino Uno to control the NFC board? and does anyone have a sample library?

I would appreciate any suggestions in that issue.Thank you in advance.Best regards.Piotr Olczyk