2014-06-05 08:47 PM
Hi all,
I am using a ST NFC chip : M24LR16E in my products and I noticed some incompatibility with Smartphones of the market (Samsung S4, S5, Nexus 4)I have made some research and I found that these phones were using a Broadcom NFC chip (BC20794) which is not compatible with some NFC chips in the product. It depends on the type of NFC tag used. (Most of existing products has Mifare Classic 1k tag and it is just compatible with NXP chip equiped phones). In fact the M24LR16E has ISO15693 standard, which is the same standard as in the NXP NFC chips of the Smartphones (PN544, PN65N...). Whereas the ISO standards in the Broadcom chips are ISO 18092, ISO14443 (from NFC Forum type 1-4 tags)...So the problems comes from this different type of NFC tags technology (Mifare Classic 1k vs NFC Forum Type 1-4)? Or is it coming from the application?Do someone has the same problems? Do we need to change the M24LR16E chips?Thank you for your answersRegards #nfc #compatible #mifare #iso15693 #m24lr16e #m24sr #m24lr #nfcSolved! Go to Solution.
2015-06-30 06:29 AM
Hi,
I suppose you are using M24LR-Discovery and want to read the temperature value (displayed on LCD screen) with RF path. Unfortunately, the temperature value is not stored in the M24LR04E by the firmware and so, cannot be read by RF. The temperature value is directly read and displayed at screen by the microcontroler. To be able to read temperature through RF, you should modify the firmware code in order to read the temperature via microcontroler , then write temperature value in the M24LR04E. After this modifications, the temperature value will be available via RF. This is source code of the M24LR-Discovery STM8L microcontroler: To read M24LR04E through CR95HF, you can use M24LR_Application_Software . Best regards, NFC/RFID ST support2014-08-28 06:22 AM
Hello,
M24LR16E is a dynamic tag ISO 15693, that can be support per
- All ISO 15693 reader/writer (from ST and competition) - Most NFC smartphone (Android +BB10)The M24LR embeds also specific functions that is not defined as standard (this is also the case of most ISO 15693 tags market offering differentiating functions) . For M24LR : high density addressing mode, energy harvesting, password…
And through the embedded software of the industrial reader, it will be possible to handle specific functions of each tag (need firmware update)And we have in our portfolio also the M24SR dynamic tag : ISO 14443 , compliant with all NFC smartphone.
M24LR & M24SR are pin to pin compatible.
Have a nice day,
ST NFC RFID dynamic tag support2015-04-28 03:22 AM
Sorry,i am trying to get the temperature of M24LR04E tag. How can i get the current temperature via CR95HFDLL?
2015-06-30 06:29 AM
Hi,
I suppose you are using M24LR-Discovery and want to read the temperature value (displayed on LCD screen) with RF path. Unfortunately, the temperature value is not stored in the M24LR04E by the firmware and so, cannot be read by RF. The temperature value is directly read and displayed at screen by the microcontroler. To be able to read temperature through RF, you should modify the firmware code in order to read the temperature via microcontroler , then write temperature value in the M24LR04E. After this modifications, the temperature value will be available via RF. This is source code of the M24LR-Discovery STM8L microcontroler: To read M24LR04E through CR95HF, you can use M24LR_Application_Software . Best regards, NFC/RFID ST support2016-04-20 10:10 AM
Hi,
I too plan to use the M24LR to interface with an NFC enabled android phone (thought the M24LR Discovery) . The main appeal being the device will not require batteries. however I am now concerned about compatibility issues outlined here. Can the M24SR simply be soldered inplace of the M24LR on the discovery board whiles maintaining all functionality (particularly the energy harvesting and bidirectional data flow)Alternately does ST have an M24SR discovery board available which utilises energy harvesting