ST25 NFC/RFID tags and readers

Hello, everyone,I have a problem with setting the GPO of M24SR64-Y as an INTERRUPT. The micro needs to come out of Sleep condition through an Interrupt sent from smartphone via RF, I saw that you have to set the GPO with 0x4X, but I don't know how to send this packet to set the GPO as INTERRUPT.The bytes I send and receive are:SYSTEM Select and UpdateBin with the GPO Field at 0x4X (can be seen in the attached figure).(BLUE-SCL / RED-SDA / GREEN-GPO)I receive as a response (R-APDU) from the module bytes 6A 82.Could you please help me out? Do I also need to implement the Capability Container to set GPO as INT? Also, the packet I send as SendInterrupt is as follows:0x56, 0x02, 0xA2, 0xD6, 0x00, 0x1E, 0x00 + CRC (0xCA,0x7F)wanted to know if this is correct as a structure or if something is missing Thank you very much

Hi,Can anybody tell me whether the X-NUCLEO-NFC07A1 works with an Arduno Uno ?In other words, can I just plug an Arduno Uno onto this unit, or do I need to buy a STM32 development board ?When plugging it onto a normal Arduno Uno I am unable to read an NFC tag (13.56 Mhz).Please help.Thanks

Hello ST Community!I am using the M24SR64-Y NFC front-end in my system where the microcontroller is always in a SLEEP state and it is woken up by a SendInterrupt from the Smartphone.The microcontroller is used to perform weight measurements.I would like to know if there is a specific RF command that not only allows me to wake up the micro, but also to make it perform an action.The GPO is set as INT (0x40)Could you give me some advice?Thank you

I'm adding Power-Down mode to my Listen Mode implementation, and have come across some unexpected behavior.I keep the chip in Power-Down, with the field detector set to automatic, and then see EON when a field is detected, as expected. The first time this happens, it behaves as expected (see first screenshot): the osc_ok bit was set automatically upon EON, then I set en and rx_en, and ~1ms millisecond later, the IRQ comes in. But the next time, 100-300ms after the previous emulation, it doesn't behave the same way. The osc_ok bit is set after EON, then I set en and rx_en, but the IRQ never comes in. This all the same logic as the previous cycle - so EON is definitely not masked, and should be coming in after ~1ms. Is there some logic/behavior here I'm missing?

I'm trying to figure out some unexpected behavior (that I've posted about before) after successfully implementing alternation between T2T Card Emulation and Reader/Writer such that they seem simultaneous to the end user.During device initialization, my code goes through the following series of events:Send Set Default commandDisable overheat protectionIncrease driver power for I2CDisable all interruptsClear all interruptsStart the oscillator and wait for it to be stableMeasure the voltage and set the power supply 5V or 3V3Send Adjust Regulator command (interrupts enabled within this step)Send Stop All Activities commandI've posted before about the difficulties I've faced with Adjust Regulators; it now works reliably with several layers of fallbacks. One of these fallbacks is to enable Tx/Rx beforehand; I don't know why, but it results in Adjust Regulators succeeding more frequently. However, when I do enable Tx/Rx beforehand (setting rx_en and tx_en), it results in an interrupt. So

Hi ， we had a problem with ST25R95 NFC solution， it looks OK to detect Mifare4  card  at 10mm range， but have not any response to Mifare7 and Felica card.this is due to NFC antenna match？ 

Posted on April 21, 2014 at 05:45 Hi Everyone, I'm using the CR95HF to access the DESFire card. Everything was going fine up to RATS and PPS. However when I tried to send the GetVersion Desfire command (0x60) using the Half-duplex block transmission protocol with PCB, CID, INF...  as below:   0x04, 0x04, 0x0A, 0x00, 0x60, 0x28 header, len, PCB, CID,   INF,    control byte   I only received 0x87 0x00. The same happened with Authenticate (0x0A 0x00) command. So I think I it must be something wrong with the EDC (CRC) code.   Could anybody shed some light on this?   --------------------------------------------------   Edited: According to the datasheet, the CR95HF only supports 14443-3 not 14443-4, is that correct?   #desfire #cr95hf

I am developing an Android app to read values from the NFC-v tag (ST25DV64KC). To revalidate my implementation, I am using the ST25 TAP app and then sending a custom command to test the commands according to the data sheet (ST25DV64KC). From an Android device, I am not able to test the commands related to the fast transfer mode. Whichever command I send with the fast feature (like FastReadSingleBlock), the response is a "Tag not in the field" error. Whereas if other commands like "Read single block" or "Read configuration" execute, the command returns the value with success. The command I am using for FastReadSingleBlock is 01 C0 02 00. Could you please help me to find the proper command to execute the fast features? In the end, I would to send the text or any file via FTM.

Hey ,   I have tried a few strategies to fix my codebase. Ive now reused the same NFCTap App iOS project and customized it according to my view.   Good news is that the previous problems are gone now. But sadly I am stuck in another problem now.   Whenever I Try to enable the Mailbox and call the present password api for that purpose, it gives a crash. Im using following flow: - First I detect the NFC tag and store its info - Then I call the NFC hit again for the mailbox status fetch - Third I try to call the present password where it crashes     Can you suggest something for that?

Hi there. I came across ST54J, which is an impressive NFC SoC capable of carrying out contact-less payment applications on its own. Unfortunately, only the databrief could be found on the product page. Where can I find the complete datasheet along with the programmer's manual and other technical documents necessary for carrying our developments on this platform? Also, why am I not able to find this SoC in the STM32CubeMX? My company specialises in smart wearables, with an appreciable lineup of products. And as the next upgrade to few of our wearable product lineups, we are introducing NFC-based contact-less payment capabilities as a strong differentiator from the market competition. For our use case, the ST54J might be a little overkill as our wearables already have wireless master controllers. What would be the most cost-effective is just a secure NFC controller that can communicate with the master controller. We are looking for contactless payment solutions that are compact

Hello I am trying to use the NFC Tuning Circuit to use this anteanna (https://www.te.com/en/product-L000641-01.html) to work with ST25R200 (https://www.st.com/en/nfc/st25r200.html).Some of the parameters needed on the tool are not on the antenna datasheet. Can I still use the tool with other OK values or I need to find the real value of the parameters?Any response is greatly apriciated, thank you for your attention.

Hi, Just to confirm, if AAT is not used , AAT pins must be left open? thanks in advanced

Hey,I want to test an off the shelf Molex NFC antenna 15*15 mm using the ST25R3911B. Is it possible to connect the antenna to the discovery board as I wanna evaluate the antenna whilst connected to the ST25R3911B? If so, how can I test the setup? If not, is there any other way to test other than connecting the antenna to a standalone chip with the matching network and decoupling components? Thank you.

I am using st25r3911b with an esp32, it works fine when i use the disco board (the original stm microcontroller desoldered). But then I decided to make my own circuit as shown in the attached image. The rfalNfcInitialize() function returns errors 0, so I guess SPI is working but, rfalFieldOnAndStartGT returns error code 12 which is ERR_INTERNAL. The code runs perfectly, without a hitch if I connect the discovery board, so I guess the timers and interrupt handling is working fine in code. Can anybody help me solve this issue.

I'm trying to establish communication -  FTM between ST25R3911B and ST25DV64KC . I'm running the example program in the reader module and I have enabled the mailbox in the dynamic tag side. The reader is able to detect the dynamic tag and is trying to send data to the dynamic tag. But it is failing. What might be the issue? Do we need to initialise anything more on the dynamic tag side? "STM32L476RG_NUCLEO_FTM_NFC5" this is the program that I'm using on the reader side.

Hello, I'm having trouble reading single blocks in the M24LR64E-R tag I'm developing the app in Flutter and I'm trying to send the command in the following structure final command = [ flags, // flags 0x20, // Command: "Read Single Block" ...uid, // UID of NFC tag blockAddress // BlockAddress ]; However, it doesn't read it, I tested it with other tags in both the NfcA and NfcV standards and they read it, but this specific tag didn't Has anyone worked with this ic?

I've been seeing some unexpected failure modes while reading T2Ts with an ST25R3916. Every ~300ms, the device sends a wake request, and if a tag is detected, goes ahead with the reading process. If a tag is detected and an error occurs anywhere in the read process, from anticollision to reading block by block, the read process will reset up to 5 times. Every time a tag is detected, the retries reset. For example, if a tag is detected, anticollision complete, and read up to block 20 before a CRC error is triggered, it will then send out five more tag detects. If there's a response to the 4th tag detect, it will begin the process again.Normally, the device rapidly reads a tag quickly and smoothly. But I've been seeing the device occasionally hang while sitting on top of a tag (well within range) for 10 seconds or more without reading. When I look at the logs, it's a series of hard framing errors (typically), and sometimes CRC or parity errors, and the 5 retries almost never trigger a tag

Hello, I am trying to get the ST25PC app to connect to a FEIG-CPR30-LCN9620 which I believe should be supported; however I not able to get the correct drivers to do so(Which I believe is the problem); I downloaded the most recent drivers from Feig website and tried some alternative drivers I also tried on the most recent ST25PC download as well as an ALPHA version that supports CPR30+, I was able to get a FEIG MR102 connected to the ST25PC, This if for a project using the SDK which also works with the MR102 however has problems connecting to the CPR30, I on the most current Windows 11 update.  

Hello, I am trying to enable the Mailbox functionality on ST25DV64KC-DISCO board. I am using the NFCTap project,And inside it added my own storyboard and a View controller.This view controller first detects a tag at launch in view didload,then it fetches the mailbox status,and lastly it tries to enable mailbox with presentpassword api on which it crashes. I have also attached a screen cast.Please let me know if anyone faced a similar issue and can advice a solution.

Hello,I have a question need your help!About :MCU L431(80MHz),SPI 5M,IC ST25R3916. NFC06A1I use "rfalNfcvPollerReadMultipleBlocks()" read two blocks at a time,but I found that it takes 9 ms to read successfully. How can I shorten this time?

Hi I'm looking for a product able to perform ISO 14443 B emulation and maybe emulate a simple tag like SRI4K, do you have anything like that?#nfcThanks

Hi everyone,I have difficulty understanding in which part of the code to intervene to modify the RFAL example code in card emulation to adapt it to my hardware.The example works perfectly on the NUCLEO-F401RE with X-NUCLEO-NFC08A1. Now that I have built the prototype hardware, I need to modify the register configuration to handle a single ended antenna without AAT.from AN5592 Looking at the code, it seems to me that the file to modify is rfal_analogConfigTbl.h, but I can't figure out how to modify it.Could you give me some pointers? Thanks to all.

Hi,I'm currently using a ST25R3911B-DISCO board at work.Yesterday my laptop was running Windows 10 Enterprise (don't know the exact build version) and everything was ok. The board was being discovered by ST25PC-NFC and I was able to use it with our custom host tool.This morning my laptop got updated with Windows 11 Enterprise 2H24 26100.2605. When i plugged the reader I saw the peripheral installation message and shortly after the installation success. I tried to open ST25PC-NFC and it was not able to detect the board anymore.If i plug the board into another win10 PC it works fine and gets detected correctly by ST25PC-NFC. Is this a known problem and is there a solution to get the ST25R3911B-DISCO working on win11 or should I just downgrade my laptop back to win10? Emanuele Somma

We've slightly modified your app ST25NFC to query our ST25DV device. It sends some measured values via NFC using MailBox (FTM). From the app, we send the same query repeatedly (cca 2 sec), and the device's response varies slightly (the value, not the message format).While it works fine on older phones, Android 13 devices throw an error after about a minute: java.lang.SecurityException: Permission Denial: Tag ( ID: B9 3B 13 05 00 51 02 E0 ) is out of date.How can we prevent this error programmatically? (Is there a command to extend NFC access permissions, or how can we achieve this?) 

Hello together,I'm writing code that is supposed to write a message to the ftm mailbox. For the setup I authorize FTM in MB_MODE. Also I enable FTM via MB_EN. After that I'm writing to the mailbox. On my oscilloscope I can see that the device sends the correct data. Basically the same as in AN4910 Table 13 but my data is different. So I'm sending Start sA6 rAck s20 rAck s08 rAck sCA. The address (2008h) gets acknowledged, but the first data byte (CAh) not. After this the MCU is not sending any more data since it registers the NAck.I made sure that all the registers are in the correct state. Here is the debug pring just before writing the data:DEBUG mb_ctrl: MbCtrlDyn { mb_en: true, host_put_msg: false, rf_put_msg: false, host_miss_msg: false, rf_miss_msg: false, host_current_msg: false, rf_current_msg: false }└─ st25dv::fast_transfer_mode::{impl#1}::debug::{async_fn#0}DEBUG mb_len: MbLenDyn { mb_len: 0 }└─ st25dv::fast_transfer_mode::{impl#1}::debug::{async_fn#0}DEBUG ftm: Ftm { mb_mod