ST25 NFC/RFID tags and readers

Posted on May 04, 2015 at 10:15HiI need to store a single file on the board from a PC (with ST application via USB) then I need to be able to read the file back to the PC (with ST application via USB). In addition, I need to be able to transfer the same file (via NFC) to any reader (i.e. smart phone)I have only the ''RF transceiver board'' that is connected to the PC with USB.I downloaded the demo application for it (stsw-m24lr011) but I can't make it communicate with the board via USB. Is there a way to store file on this board at all and if so, hot to accomplish this task?Thanks a lot. #nfc

Posted on May 19, 2014 at 19:38Hi ST community ! :)For a projet I�m working on, I need to save some informations coming from a �C (time, date and pressure) into a memory that must be read without any wired connections. So the NFC/RFID protocol seems to be the most appropriate way to do the trick.On the internet I could find the M24SR64 and it seems to match well with my application. Indeed, the �C will write data into the M24SR64 memory using I�C protocol and a NFC/RFID reader will ask the device to receive data when the system will be turned off.However, I have some questions� I don�t want to use a smartphone to receive data from memory but I would prefer an NFC/RFID reader. Is it possible? If yes, can you give me some reader references?Then, I guess there are special commands the reader should ask to receive the memory content. Is it possible to do it with standard RFID/NF

Posted on November 07, 2014 at 15:31Dear All,I'm using in one of my products a M24LR NFC memory.Now I would like to indicate in the external case the correct position of the NFC memory with a NFC logo.Which logo could I use?Are there some restrictions on using some kind of logo?Best Regards #nfc-logo #m24lr

Posted on June 12, 2014 at 18:55Hi I am using an Arduino UNO board to make an application to read the data of my M24SR64 antenna using I2C protocol. The problem is that I don't know if I am already communicating with it. I know from the datasheet that the address to read from a M24SR64 is 0xAD.Here is the code of the Arduino UNO so I can read the data&sharpinclude <Wire.h>void setup(){    Serial.begin(9600);     Wire.begin();        Serial.println(eepromRead());   }void loop(){}byte eepromRead(){  Wire.beginTransmission(0xAD); // Opens I2C communication with M24SR64  Wire.write(0);  Wire.endTransmission();    Wire.requestFrom(0xAD, 1);    while(!W

Posted on March 11, 2015 at 16:23Hi, I'm trying to set up a NDEF with multiple records.     // write NDEF message (command C-APDU - datasheet 5.2.1 p32)     ndef[0] = 0x02;                // PCB:     ndef[1] = 0x00;                // CLA: class byte     ndef[2] = 0xD6;                // INS: instruction byte     ndef[3] = 0x00;                // P1: param byte 1     ndef[4] = 0x02;                // P2: param byte 2     ndef[5] = 5 + 5 + 7 + 5 + 1;     &nbs

Posted on May 27, 2015 at 15:39When I read my M24SR02-Y tag from the Android app ''NFC Tools v3.8'', NDEF is no longer listed as available technologies.Any suggestions as to how this can be?I do need NDEF for my application.EDIT: The official Android NFC Reader app from ST cannot read my tag. and the other app is only capable of reading it when my device is disconnected from the power supply. #android-app #m24sr02-y #ndef-technology #m24sr

Posted on January 30, 2015 at 12:06Hi everybody, I would like to know if it is possibile to interface two CR95HF so that one acts as a tag reader and the other acts as a passive tag, and vice versa. Is this a P2P communication? If so... I know that CR95HF cannot acts as P2P player. Any other solution? Thanks in advance Stefano #p2p #cr95hf

Posted on November 04, 2014 at 18:04Hello everyone,i have a problem to manage sector secure status by I2C.My step are here described:- presentation of I2C password, like described in datasheet (needed only at boot)- write the SSS byte of the desired sector.As a double check I'm going to read the value of the byte just written, and I find that the value has not changed.I miss some step?Best RegardsAlberto #m24lr #secure-sector

Posted on February 16, 2015 at 07:45Microsoft in Windows phone 8.1 has added new Nfc related features including low level access(Non NDEF). I have Nokia Lumia 830 (PN547 NFC chipset is present in this device).Im not able to detect Nfc tag (ANT-7M24LR-A ,ISO15693) through Lumia 830, which im able to read/write using Nfc-V(ISO15693) in Android. I also have a Lumia 720 (old NFC hardware) but atleast it is able to detect the tag. Has anyone encountered this ? Whats the workaround ? #m24lr #lumia

Posted on February 24, 2015 at 12:04Hi,For a project I use the M24LR64E-R as memory and power supply. Everything works very well if I want to read or write the M24LR64E-R. But as soon as I read another sensor, this sensor value cannot write to the M24LR64E-R. For this application I use the MCU MSP430FR of TI.Following ANs I've read:AN1471 (http://www.st.com/web/en/resource/technical/document/application_note/CD00004295.pdf )AN3057(http://www.st.com/st-web-ui/static/active/en/resource/technical/document/application_note/CD00247968.pdf )Errata sheet for M24LRXXE-R(

Posted on May 25, 2015 at 08:58Good day,  I have a rquirement where I need to use EUI-64 address.  The M24LR04E has a unique 64bit address.  Can I use this as an EUI-64 address? #uid #m24lr #eui

Posted on June 23, 2015 at 09:05Microsoft in Windows phone 8.1 has added new Nfc related features including low level access(Non NDEF). I have Nokia Lumia 830 (PN547 NFC chipset is present in this device).Im not able to detect Nfc tag (ANT-7M24LR-A ,ISO15693) through Lumia 830, which im able to read/write using Nfc-V(ISO15693) in Android. I also have a Lumia 720 (old NFC hardware) but atleast it is able to detect the tag. Has anyone encountered this ? Whats the workaround ? #iso-15693 #m24lr #lumia

Posted on July 25, 2014 at 16:21We would like to use the MB1054A ''wand'' from a Linux box, to interrogate a M24LR04E tag embedded in our product, but the available software from ST is based only on Windows. Does anyone know of Open Source drivers and library code to support this wand? Many thanks in advance, Jon #cr95hf #linux #mb1054a-cr95hf-linux-open-source

Posted on February 17, 2015 at 09:49Hello, I can't get either read or write (over I2C) to work correct. If I write the text ''Hello World!!'' from the phone (S3) and then read it over the I2C I get the following error. When I read the length it says 0x14, but if I try to read anything over 0x10 it will fail (only sending FF...), but if I read only 0x10 (or less) it will work?! Same when I try to write (over the I2C), then I will get the error code 67 00, but I can't see what's wrong. If I read it with the phone it says it's empty, but if I read it over the I2C I can find it there. Below is a summery over what I send (and get back) over the I2C. Anyone that can tell me what I'm doing wrong? Grateful for help!void InitNFC(){   //Send ''Kill RF and open I2C   Send AC 52   //Select NFC-T4   AC 02 00 A4

Posted on January 19, 2015 at 06:55Dear Sirs: We are using M24SR64. Now we met a problem with NDEF File Length in 36 bytes. Problem: 1. If the NDEF File Length is 36 bytes, it can not be a successful data in Android OS or NXP TagInfo app or NFC TagInfo app. Only the app of ST ''M24SR Demo'' can show the payload we wrote. 2. If the NDEF File Length is 35 or 37 bytes, it is a successful Tag data. At first, we used I2C to write the data and we met this strange behavior. Then we used the M24SR Demo app to test it, it also fail in 36 bytes (35 or 37 are OK). Here is a simple way to reproduce the stange behavior: - Tested in Samsung S3 (Android 4.3, may PN544) and Nexus7 generation1 (Android 4.4.3, may 65N04) - Use the app M24SR Demo (download from Google Play)   -> Choose the NDEF editor and TEXT mode   -> Key in the data (payloa

Posted on October 06, 2014 at 17:34Hello,I'm having trouble writing an NDEF message to the M24SR (with 8KB EEPROM) via i2c.I am able to correctly write an NDEF Text Message via the official M24SR Android app.I am able to correctly read the NDEF File via i2c.However, when I try to write ''hello world'' via i2c to the NDEF file, the M24SR Android app reads an empty NDEF.Here is the i2c sequence of what I've tried:            (kill RF)AC 52            (select NFC)AC 02 00 A4 00 0C 02 E1 03 D2 AF            (5 reply bytes read)02 90 00 F1 09            (select C

Posted on January 23, 2014 at 15:38Hello Everyone,I have the same request than ramirez_prieto.valen, I'm looking for an I2C routine in order to write an NDEF message in a M24LR04 tag, but I haven't foud anything about that. Obviously the AN3408 is important for understand NDEF MESSAGE structure, however It's would be very interesting to have an I2C routine. I've tried to write this routine but It seems to be wrong and since 3 days I have tried to debug it. I don't know  for example if the CC field his automatically set or if it's defined by the user, furthermore I don't know how to manage user memory area when there is already a previous NDEF message. there are not informations concerning these issues.An example would be very nice #nfc-phone-support #ndef #m24lr

Posted on February 24, 2014 at 17:02Hi all,I can see in the documentation the command ''Lock Sector'' and used in the android demo application but I cannot figure how to unlock a sector. Using the application, I have changed the first password and locked the first sector and now I cannot write it and unlockit. Can Anybody help me?Thanks a lot. #lock-sector #m24lr #password

Posted on August 29, 2014 at 16:55Hello,I'm having trouble calculating the CRC when sending and receiving bytes via i2c from the M24SR.I've tried following the example on page 29 from the application note on storing data in the NDEF memory(http://www.st.com/web/en/resource/technical/document/application_note/DM00105043.pdf)When I follow the CRC algorithm from wikipedia (http://en.wikipedia.org/wiki/Cyclic_redundancy_check&sharpComputation)The calculated CRC does not match the expected CRC from the example.Can someone please show step by step how to calculate the CRC?For inst

Posted on July 01, 2013 at 12:10Hej! I just bought a DEMO-CR95HF board to sort out EMI problems that I have with my own design with the CR95HF chip. To my disappointment the DEMO board generates more harmonics than my own design. My measurements can be found at http://milvus.nothagen.se/pub/strfid/rfid.htm Also, when I checked the resonance frequency of the antenna I found that it was tuned to 15.2MHz and not 13.56. The resonance frequency was measured using a spectrum analyser with tracking output. Therefore I wonder: Is DEMO-CR95HF designed for optimal performance? Is there any known optimization can can be done to the board to improve performance? I was planning to use the layout for the circuit between the chip and the antenna. As a consequence of my measurement above I r

Posted on July 09, 2014 at 20:43I want to work with the RF transceiver Demonstration Board code and I have found it at this link:http://www.st.com/web/en/catalog/tools/PF257512 However, as far as I can tell, there is only a version of the project built in Keil, which I do not have and am not familiar with. Is there a version out there for the IAR Embedded Workbench IDE as well as there is for many of the other ST demo board example projects? Thanks! #iar #keil #m24lr-discovery #m24lr-discovery-cr95hf-firmware

Posted on July 02, 2014 at 16:29Hello I want to build a reader to communicate with ISO14443A and ISO15693 tags using the CR95HF transceiver IC. I build a 2 turn PCB antenna and calculated the matching of the PCB antenna according to AN4327 and the excel tool. With VPS_TX = 3,3V I get performance equal to the PLUG_CR95HF demo board. I tried also to match the antenna for VPS_TX = 5V (assuming better read range) and with this setup it is possible to power tags over a greater distance but I cannot communicate (receive) with the tags. I get little improvement by tweaking the Timer Window and Receiver Gain (5.8.1 and 5.8.2 CR95HF datasheet). But the only way to determine these values I found was �try and see�. So my question is how to measure or determine the right values for these parameters. With best regards Marco #cr95hf #cr95hf #5v

Posted on June 19, 2014 at 15:01Hi,I have two applications one for the Calibration of CR95HF and one for Tag detection. Before running the Tag detection application Calibration is done and the DAC ref value obtained is saved in a file. The Tag detection application uses the DAC ref value and puts the CR95HF device into IDLE mode with the wakeup event configured as Tag Detection. When a TAG is placed in the proximity area, device wakes up and the application reads the UID. Most of the time everything is working fine. But sometimes, the device is not waking up from IDLE mode, even if TAG is placed in the vicinity area. It may work after some time after some board resets and all. I couldnt find the issue as its not coming regularly. But the issue is a repeating one. One thing I observed is I am getting different DAC Ref value for the same board with antenna connected and without antenna connected. say 0x03 and 0x0

Posted on April 08, 2014 at 15:49Hello everybody, I have my M24SR working with my MCU :) I can read the contents of the tag. However, after a read from MCU, I cannot write the tag if I do not remove power from it. I have performed the DESELECT command and also DE_INIT my I2C. All the communication procedure takes place perfectly. The tag is connected to MCU by means of the two I2C wires, one VCC and one GND. I do not have GPO since to save one pin I work by polling. Have a nice day and let me know your opinions about this subject! :) #m24sr #deselect #m24sr #m24sr #nack #m24sr #gpo #ack

Posted on May 30, 2014 at 15:33Hi Guys,We are trying to build a multi-disapline access control reader terminal. The CR95HF was chosen for the design. The reader is not an OEM reader and is required to read a number of cards from Various Suppliers.We have opted to run the RF Supply from 5V in the hope. We used the spreadsheet ''CR95HF EMI Filter Calculation.xls'' for the front end matching calculation and component selection. When compared against other designs we have done, we are experiencing quite poor range with a range of Mifare tags. Our antenna design is approx 70mm x 70mm (2 turns)We matched 2 designs, one with an emi filter and one without. Both failed CE compliance testing even though they were well matched. The one without failed badly. The one with emi filter failed on harmonics 13 and 15. We stopped design at that point and worked on another design but we are picki