CR95HF

[Ntuye.1]

- hello, i am use cr95hf to read, write block with is014443A tag 

- SEND: 02 02 00 00, RECEIVE: 00 00

- SEND: 02 07 02 00 00 00 00 02 02, RECEIVE: 00 00

- SEND: 09 04 3A 00 5A 04, RECEIVE: 00 00

- SEND: 09 04 68 01 01 DF, RECEIVE: 00 00

- SEND: 04 02 26 07, RECEIVE: 80 05 04 00 28 00 00

- SEND: 04 03 93 20 08, RECEIVE: 80 08 4B F3 A7 05 1A 28 00 00

- SEND: 04 08 93 70 4B F3 A7 05 1A 28, RECEIVE: 80 06 08 B6 DD 08 00 00

- after how to authentication with key A, read/write block?

- I send: 04 0D 60 01 FF FF FF FF FF FF 4B F3 A7 05 28, recieve: 87 00?

[Brian TIDAL]

Hi,

can you share more information :

• about your software setup: do you use X-CUBE-NFC3 library to send those commands or do you have your own driver?
• about the tag manufacturer and model

87 00 reply means timeout (i.e. the tag has not replied to the command). This is due to Auth A command having a wrong format. Check the tag datasheet for proper Auth A command format.

Anyway, Authentication with key A refers to tags having proprietary Authentication and encryption  before any memory operation (see datasheet from the manufacturer of these tags). If you want to use such tags with the CR95HF reader, you will have to implement this proprietary authentication and the ciphering. See other posts on this topic in this forum https://community.st.com/s/question/0D50X0000BQNakcSQD/nfc0541-read-mifare-classic-1k.

But I would rather recommend to use fully compliant tags from the ST25 family such as ST25TA (Type 4A Tags) or fully compliant Type 2 Tags (i.e. tags not requiring proprietary stuff).

Rgds

BT

[Ntuye.1]

How correctly formatted Auth with key A command?

[Brian TIDAL]

Hi,

the Auth with key A command is described in the tag datasheet from the manufacturer of the tag.

As this is a proprietary command from another manufacturer, I cannot give more details.

Rgds

BT