ST25 NFC/RFID tags and readers

Hi,I'm working with a ST25R3911B RFID chip associated to a STM32L072 uC.I use the "STM32CubeExpansion_NFC5_V1.2.0" project, ported from STM32F401 to STM32L072.This project enables to set the ST25R3911B  in wake-up low power mode.Now I'm trying to set the STM32L072 in standby mode with the ST25R3911B  using the IRQ.I can wake-up the STM32 with IRQ generated by ST25R3911B  when a badge is passed but I cannot read the badge.So my question is : is the "STM32CubeExpansion_NFC5_V1.2.0" project compliant with uC low power mode like standby ?Regards,Matthieu

Hello everyone,i have gone through ST25RU3992 it has written that it will support ISO18000-6C fully and ISO18000-6A/B in Direct Mode. will it support ISO18000 6D some how or else any other option that we can configure it in ISO18000 6D protocol ? "thanks"

..

I have a microcircuit M24SR04-Y, on which I recorded information using the NFC.I need to read this information using i2c.I read the datasheet and understood the circuit of communication with the microcircuit.But I am a novice and without an example it is very difficult to understand.Tell me how and in what form to send commands. If you show an example of communication with the chip, it will be great.Thanks!

@

I'm designing the NFC antenna, the EMC filter and the matching circuit, for an industrial NFC application. I'm looking for a good value of the matching impedance that provide the right tradeoff between performance and efficiency

I use pc software(ST25R3911B Discovery GUI) linking with ST25R3911B in usb.the tag is st25dv04k.My order of operations is | ST25 Tag Editor model | > | ISO15693 model | > | DYNAMIC NFC TAGS| > | ST25DV04K|.I use file transfer model,choice LOAD FILE TO MEMORY command,load a bin file to memory ,BUT why don't have any information about the bin file in the EEPROM. I write bin file in memory but it is different with bin file .The bin file is follow.

Hallo!With ST25RU3993 UHF RFID reader, reading and writing to an RFID tag via the ST commands CMD_WRITE_TO_TAG and CMD_READ_FROM_TAG at a word address greater than 0x7F fails. Using CMD_GENERIC_CMD, I could successfully read from the tag even beyond word address 0x7F (by manually providing the address in the EBV format).But write to tag using CMD_GENERIC_CMD is still a problem  According to EPC Class1 Gen2 spec, Writing to a tag involves two steps :       1. Random Number Request (Gen2 command - Req_RN)      2. Write to tag (Gen2 command - Write) -- actual data to be written into tag has to be ex-ored with the random number received But, the actual value written into the tag is different from the requested value.As a means to use CMD_GENERIC_CMD for writing to tag, I first want to succeed with a word address below 0x7F.An example, where I try to use CMD_GENERIC_CMD to write FF FF to a tag at word

:megaphone: ST25PC-NFC v2.1.0 is available for download! :megaphone: https://www.st.com/en/embedded-software/stsw-st25pc001.htmlNew in ST25PC-NFC version 2.1.0:New Features:M24LR GPO & Energy Harvesting specific screens addedST Type4A GPO user interface ST Type4A Access Rights managementImprovements:Area Configuration:Adjusted byte sizes of Area1 for ST25TV and ST25DV-PWMInventory:Protocols are enabled/disabled according to reader capabilitiesAdded right-click context menu for ST25TA and M24SR tagsType4A Unitary command expert interface:Bug fix and improvements (NDEF file number, Stop sequence when Error code, Signature management on ST25TA02KB)Help menu:Reworked + added link to ST CommunityPassword management:Now supports Type4 ST tagsST25DV-PWM also supportedBug Fixes:Removes warning message when reader's firmware version is more recent than the expected oneBug Fix in User Memory File Writing OperationModified SelectTag process for Type4A CC file & Type4A System file UIs

Reference is to ST25R3911B data sheet, page 16, section 1.2.3Concern is is the SS25R3911B damaged or just fails to operate properly?

..

This is the same question that I posted on the NXP Community "Problems doing updateBinary"I send 16 bytes using the NDEF updateBinary command after the NDEF Select file0x2 0x0 0xd6 0x0 0x4 0x10 0x54, 0x77 0x61 0x73 0x62 0x72 0x69 0x6c 0x6c 0x69, 0x67 0x61 0x6e 0x64 0x74 0x68 And get back 0xf2, 0x2

Posted on July 13, 2018 at 12:01Hi, I'm trying to run EVAL-ST95HF_FW_V3.7.0 source code on STM32L4 processor but unfortunately I can't link the compiled objects because of undefined reference to 'PICCNFCDEP_ReplyCommand' and 'PICCNFCDEP_Init'. The definition of these functions is missing in EVAL-ST95HF_FW_V3.7.0 source code, I can find only the declaration of these functions in 'lib_nfcdeptarget.h'. Thanks for the help in advance. Kind regards,Maciej #piccnfcdep_replycommand #st95hf #undefined-reference #eval-st95hf_fw_v3.7.0 #eval-st95hf #piccnfcdep_init

As I understand it, NXP's NTAG family (NTAG 210u, NTAG 21x) are fully compliant NFC Forum Type 2 and ISO/IEC14443 Type A devices, and as such, they should work with the CR95HF. However, these tags have additional features, like an originality signature, that areoutside the scope of the standards. Are these additional features compatible as well, or are they only supported by NXP readers?

HELLO DaLao，​​​May I ask you a question about how can I shoud use clrc663 to read 14443a tag (m24sr64) by a wireless way?​​​Now,I can read and write MIFARE tag succesful, but can't do with 14443A tag?​​​This do sucessful:​status = phpalI14443p3a_ActivateCard(&I14443p3a, NULL, 0x00, bUid, &bLength, bSak, &bMoreCardsAvailable);​​​This failed:​​​PH_CHECK_SUCCESS_FCT(status, phKeyStore_SetKey(&Rc663keyStore, 0, 0,PH_KEYSTORE_KEY_TYPE_AES128, &Key[0], 0)); this function return 0x201.​​​And I find that PH_KEYSTORE_KEY_TYPE_AES128 is not supported by this software lib, in that function the case of "PH_KEYSTORE_KEY_TYPE_AES128" is EMPTY!​​​Finally, may I ask if the clrc663 can read/write with 14443a tag produced by other company?​And, wether the software lib is complete to support to read/write with 14443a tag?​​​Tanks a lot,​have a nice day! ​我现在就是读出�?�TAG的UID，但是无法匹�?密�?密钥。�?知�?�RC633对支�?的NFC芯片厂家有没有�?制。现在读写NXP公�?�的MIFARE�?�没有问题，但是我现在想用的TAG是ST公�?�的M24SR，读出UID之�?�始终�?能读

While developing a driver for the ST25RU3993, I have encountered a problem where the MISO line appears to stop working. I had previously been able to read out the version ID register, oscillator status, etc. but now everything reads back as zero. There have been no hardware changes to the board, and this has happened on two separate (otherwise identical) boards.Even though MOSI is always zero, it appears that the ST25RU3993 is at least partially functional. The power consumption increases when I toggle the enable pin high, and it increases again when I command it (via SPI) to enable the RF field. The PLL is also running (I can see a 50kHz waveform on the loop filter pin).I believe that I first started having problems when trying to write the PLL Main registers. I found a bug here where PLL Main register 1 was being written incorrectly, and I know that getting PLL divisors wrong can cause problems e.g. in microcontrollers (basically overclocking the core which can cause damage) but sinc

Hello,When we use the APB1 clock 2MHz for peripherals I don't see any problem with communications between memory and MCU. However I would like to increase the APB1 clock to around 16MHz for my final application do the the fact that other devices needed it. However when I increase the APB1 clock rate to i.e 4MHz I already see data line corrupted on I2C bus. I am using 10k pull-up resistors to drive on SDA and SCL lines. I would like to ask you if you have faced with the similar problem and if yes do you have any suggestion to resolve it?Thank you in advanceJacek Pieczaba

I'm currently writing a custom application using the STM32CubeExpansion_NFC4_V1.2.0 as inspiration. I'm trying to enable the mailbox operation however when I go to write the enable bit in the ST25DV_MB_MODE_REG I get a NACK and the bit is not set in the register. I'm using the Mailbox example from the above firmware expansion pack. I'm using X-NUCLEO-NFC04A1 and NULCEO-F746G development boards. All functions previous to writing in to the dynamic register work and are verified with reads.In the datasheet for the device it says a byte write maybe inhibited in the following conditions: • Byte is in user memory and is write protected with LOCK_CCFILE register. • Byte is in user memory and is write protected with I2CSS register, and I2C security session is closed. • Byte is in user memory and fast transfer mode is activated. • Byte is in system memory and is a Read Only register. • Byte is in system memory and I2C security session is closed.• Byte is in fast transfer mode’s mailbox and is n

Hello all,for test purposes I want to realize a communication of small data amount with the ST25R3911B-Disc​o board.yet I already:installed the gui and updated firmwaretested nfcip with my smartphone (so the board is working)tried to use integrated script tool for sending (didn't work yet)Im not sure which standard is apropriate to realize the project and how to define it in the script tool.For testing I use an ST25TA64K Tag.Regards, Ben

Hi ,Using FedmIscReader im tring to read / write to the M24LR04-R sector block .Before write operation i need to present the password for each sector.I found Data sheet for M24LR04-R , It has some custom command for present password for M24LR04-R.can you guide me how to sent those command through FedmIscReader or present password through FedmIscReader . because using M24LRxx_Application_Software can able to present the password.In that application , has OBID USB-Driver files . same SDK only im using for my application for comminucating the M24LR04-R.I'm using .net c# for delevelopment

I have successfully communicated with CR95HF using usb to uart bridge using uart communication. I can read my nfc tag(BL654- type 2) UID using command send from terminal by selecting ISO14443-A protocol.But I have problem with reading data from tag how to read data.For infomation: when i read NFC tag(BL654) from mobile "NFC Tools" andoid application it displays my data wrote on nfc tag.Thanks,Jignesh Patel

I need to set cr95hf to 14443A, but unfortunately I have a problem with that.Where is the problem?0x01 0x00   0x07 0x0e 0x03 0xa1 0x00 0xf8 0x01 0x18 0x00 0x20 0x60 0x60 0x00 0x00 0x3f 0x01 0x07 0x0e 0x03 0xa1 0x00 0xf8 0x01 0x18 0x00 0x20 0x60 0x60 0x00 0xfc 0x3f 0x01 0x07 0x0e 0x03 0xa1 0x00 0xf8 0x01 0x18 0x00 0x20 0x60 0x60 0x00 0x7c 0x3f 0x01 0x07 0x0e 0x03 0xa1 0x00 0xf8 0x01 0x18 0x00 0x20 0x60 0x60 0x00 0x3c 0x3f 0x01 0x07 0x0e 0x03 0xa1 0x00 0xf8 0x01 0x18 0x00 0x20 0x60 0x60 0x00 0x5c 0x3f 0x01 0x07 0x0e 0x03 0xa1 0x00 0xf8 0x01 0x18 0x00 0x20 0x60 0x60 0x00 0x6c 0x3f 0x01 0x07 0x0e 0x03 0xa1 0x00 0xf8 0x01 0x18 0x00 0x20 0x60 0x60 0x00 0x74 0x3f 0x01 0x07 0x0e 0x03 0xa1 0x00 0xf8 0x01 0x18 0x00 0x20 0x60 0x60 0x00 0x70 0x3f 0x01   0x09 0x06 0x09 0x04 0x68 0x01 0x01 0x50   0x09 0x06 0x09 0x04 0x0A 0x01 0x02 0xA1   0x02 0x02 0x02 0x00

Dear My friends, I got a ST25R3911B-EMVCO kit and want to test it but there is no software inside the kit. How to work with it?Regards,Albert

..

Posted on February 20, 2018 at 02:22The ST25R3911B datasheet, page 14 Figure 3, shows a minimum configuration of antenna connection components. There are provided schematics and layouts for the differential antenna configuration, however are there any recommended component values/layout available for the single ended configuration?Datasheet: http://www.st.com/content/ccc/resource/technical/document/datasheet/group3/ba/60/79/5c/bb/a9/41/76/DM00321525/files/DM00321525.pdf/jcr:content/translations/en.DM00321525.pdf Application note: http://www.st.com/resource/en/application_note/dm00347152.pdf #st25r391x #st25r3911b