cancel
Showing results for 
Search instead for 
Did you mean: 

X-NUCLEO-NFC09A1 read Tag data error

sami_josi
Associate II

Hi,

I am using the X-NUCLEO-NFC09A1 with the demo project “ST25R200_v3.0.0_Linux_demo_v1.0”.
The code is running on a Raspberry Pi 3B and communicates with the reader via SPI.

When I run the demo and place an NFC tag near the reader, the application reports “READ Fail”.

Could someone please explain what this error means and what might cause it?

Thank you.Skärmbild 2026-01-29 151630.png

This discussion is locked. Please start a new topic to ask your question.
1 ACCEPTED SOLUTION

Accepted Solutions

Hello Sami,

shown tag is of type Mifare Classic which uses a proprietary crypto. 

Our demos are not built in a way that they know how to read/write data from arbitrary tags. By default we have an implementation of NDEF reader/writer which can read and write NDEF formatted Tags T2T, T3T, T4T and T5T.

If you are building an application you will need to first define which tags you want to handle. Then you can define the which actions you want to perform.

BR, Ulysses

 

View solution in original post

8 REPLIES 8
Ulysses HERNIOSUS
ST Employee

Hello sami_josi,

the demo is just basic polling plus sending one single command to demonstrate how to read data. The used commands should work on NFC Forum Tag types (T2T, T3T, T4T, T5T)

I assume the first card to be a Mifare Classic card which gets treated as a T2T and does not answer the un-encrypted Read BLOCK command.

The second card I am not sure, why, but the card seems to not support the reading of single block. So not being a T5T.

Please check the details of the cards and which commands they are actually supporting.

Best Regards, Ulysses

sami_josi
Associate II

Hi  Ulysses

Thank you for the replay.

my second ntag is "NTAG5 Boost" from xnp "https://www.nxp.com/docs/en/quick-reference-guide/OM2NTA5332-QSG.pdf". I have uncommented and added some debug to the st25r200 demo this is why it is failing to read.  Skärmbild 2026-02-06 134337.png

Best Regards sami

 

Hello sami,

not sure where exactly you placed your debug code and what "2124326112 2" should mean. The 2 might indicate RFAL_ERR_BUSY which would mean operation not yet completed. You should not see such return code on the outer levels.

Alternatively, you can also share logic analyzer traces (SPI+IRQ) which should give most complete insights.

Ulysses

sami_josi
Associate II

Hi Ulysses

Thank you for the replay. the 2 is part of the rxbuff which was cut because of the print buff was full. 

maybe i shoud have asked this befor. i am using   "ST25R100" " X-NUCLEO-NFC09A1 NFC card reader expansion board" and the demo "en.ST25R200_v3.0.0_Linux_demo_v1.0" does the demo work with ST25R100?

my tag is "Ntag5 boost"

 

Skärmbild 2026-02-06 162904.png

my rxbuff was 05050505050505 befor i reading block 1 then after trying to read failed the it changed 010F.  the 01 is RFAL_NFCV_FLAG_POSand the bit RFAL_NFCV_RES_FLAG_ERROR is set. what does this mean? 

is there specific programable TAG wich can be used with st25r100?

best regurds Sami

Hello,

the response 010f is a response returned by the tag. This seems to be the generic error according to its data sheet for various commands. 

Maybe the tag has some protection configured - preventing read of block 1. I guess you need to look at the tag side.

BR, Ulysses

 

sami_josi
Associate II

Hej Ulysses

i have tested the reader with other tags it fails to read block. 

"ISO14443A/NFC-A card found. UID: FBC47506
Read Block: FAIL
ISO14443A/NFC-A card found. UID: FBC47506
Read Block: FAIL"

the reader succesfully reads the UID but fails to read block data. how does that relate? how is it trying the read a block? i have connected the ST25R100 directly to my raspberry pi via SPI bus and vcc 5V, and gnd. is there smothing i missed that can cause the read fail?

 

It only successfully read a digital ncf from mobile.

"NFCA Passive ISO-DEP device found. UID: 0837924D
Select NDEF Application: OK Data: 6A82
NFCA Passive ISO-DEP device found. UID: 08848202
Select NDEF Application: OK Data: 6A82"

here is the tag info failing to read block.

UIDFBC47506.jpeg

 

best regards Sami

Hello Sami,

shown tag is of type Mifare Classic which uses a proprietary crypto. 

Our demos are not built in a way that they know how to read/write data from arbitrary tags. By default we have an implementation of NDEF reader/writer which can read and write NDEF formatted Tags T2T, T3T, T4T and T5T.

If you are building an application you will need to first define which tags you want to handle. Then you can define the which actions you want to perform.

BR, Ulysses

 

sami_josi
Associate II

Hello Ulysses

Thank you for the replay. I am now using a new tag with Type 5 and it is working fine.

 

regards sami