Associate

Solved

Can anyone confirm that STM32L476RG-Nucleo binary located in C:\...\STM32CubeExpansion_NFC3_V2.0.0\Projects\STM32L476RG-Nucleo\Applications\Polling\Binary DOES support CR95HF ?

5 replies
1334 views

When I look at source code I can only see bsp driver for ST25r95???

It looks like it can detect tag of type ISO14443 or 15693 but the IDs read is not correct and sometimes it is and board reset randomly.

My board is NUCLEO-L476RG.

This topic has been closed for replies.

Brian TIDALBest answer

ST Technical Moderator

Hi,

both ST25R95 and CR95HF will properly do the job of reading the UID. For new project, ST25R95 is recommended. Customers using CR95HF in already existing products will continue to be served with CR95HF to avoid them to redo product qualification. I would suggest you contact your local ST sales representative for a quote for ST25R95.

Regarding the field detection, it can be used either through the PollField command or through the Idle command. The main use case is for Card Emulation: you can enter low power sleep mode thanks to the Idle command and then as soon as the field is detected, the device exits the sleep mode and can be set to card emulation mode.

Rgds

BT

In order to give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

FVincAuthor

Associate

Looking more deeply in code and datasheet, both ST25r95 and CR95HF responds to the same chip ID "NFC FS2JAST4" to the IDN command 0x1.

Looks like CR95HF has an additional UART interface available

ST25r95 supports Card emulation (ISO/IEC 14443-3 Type A) and others stuffs

They both belong to ST25 familly and they are polled and configure the same way.

Brian TIDAL

ST Technical Moderator

See next post

In order to give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Brian TIDAL

ST Technical Moderator

Hi,

The X-CUBE-NFC3 sofware (STM32CubeExpansion_NFC3_V2.0.0) includes the driver for ST25R95 and CR95HF. Both ST25R95 and CR95HF have the same Chip ID and the common driver is located in STM32CubeExpansion_NFC3_V2.0.0\Drivers\BSP\Components\ST25R95.

Note: ST25R95 is recommended for any new development.

X-NUCLEO-NFC03A1 can be used for developmment on both ST25R95 and CR95HF.

STM32CubeExpansion_NFC3_V2.0.0 is based on the RFAL which encapsulates the different RF ICs (ST25R3911, ST25R3916, ST25R95/CR95HF and future ST25R devices) into a common and easy to use interface.

The supported NFC technologies in this demo are:

NFC-A \ ISO14443A (***, T2T, T4TA)
NFC-B \ ISO14443B (T4TB)
NFC-F \ FeliCa (T3T)
NFC-V \ ISO15693 (T5T)
ST25TB (ISO14443-2 Type B with proprietary protocol)

Would you please share more details about

ID is not correct (beware that ISO15693 stores the UID in reverse bytes format): would you please dump the UID and share what is displayed by the demo
board reset randomly: what are the symptoms? What makes you believe the board has reset?

On my side the NUCLEO-L476RF + X-NUCLEO-NFC03A1 are very stable. Can you check the X-NUCLEO-NFC03A1 is properly plugged in the Nucleo board and that the USB supply is correct (check USB cable and USB connector)?

On my side, I have the following traces:

ISO15693/NFC-V card found. UID: E00402005108B6F6
 Read Block: OK Data: 035DD217

I've checked the internal UID in reverse byte order : F6B60851000204E0 ==> E0 04 02 00 51 08 B6 F6 which is correct

For ISO14443A/NFC-A:

ISO14443A/NFC-A card found. UID: 02A2003AE83081
ISO14443-4/ISO-DEP layer activated.
 ISO-DEP TxRx OK: - Tx: 00A4040007D276000085010100 Rx: 9000
 Select NDEF App successfully
 ISO-DEP TxRx OK: - Tx: 00A4000C02E103 Rx: 9000
 ISO-DEP TxRx OK: - Tx: 00B000000F Rx: 000F2000FF003604060001010000009000

and the internal UID fromthe system file is 02 A2 00 3A E8 30 81 which is correct

Rgds

BT

In order to give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

FVincAuthor

Associate

Thanks Brian for the answer.

I have ended up to same conclusion investigating a little bit more the source code and tesing a few modified firmware.

Now I can read all Tag of type 14443A/B and 15693, firmware seems quite stable.

I have going to start a new project and I have a quote for the CR95HF and not ST25r95.

Do you have any concern that CR95HF might not be longer supported within coming years ?

My need is quite basic as I just need to read UID and not modified card content, the CR95HF seems to do the job.

I have seen that ST25r95 is also able to do some field detection (CR95HF does the card detection), could you give me more details about field detection ?

Thanks for your support.

Brian TIDALBest answer

ST Technical Moderator

Hi,

both ST25R95 and CR95HF will properly do the job of reading the UID. For new project, ST25R95 is recommended. Customers using CR95HF in already existing products will continue to be served with CR95HF to avoid them to redo product qualification. I would suggest you contact your local ST sales representative for a quote for ST25R95.

Regarding the field detection, it can be used either through the PollField command or through the Idle command. The main use case is for Card Emulation: you can enter low power sleep mode thanks to the Idle command and then as soon as the field is detected, the device exits the sleep mode and can be set to card emulation mode.

Rgds

BT

In order to give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Sign up

Click below to sign in

Login to the community

Click below to sign in