RF Writing is not working on ST25DV64

[HABIJ.1]

Hi,

I am working with a ST25DV64. I succeeded reading and writing via I2C. I can also read via RF interface. But I have not succeeded writing via RF interface.

I checked the static registers and there is no write protection,  I have one area and RFA1SS = 0.

Do I miss something? Thanks for your help

[Brian TIDAL]

Hi,

can you show which command is being sent to write?

Rgds

BT

[HABIJ.1]

Thanks for the reply.

Well, to give all the context : I suspect RF write problem in a bluetooth NFC pairing I am trying to implement.

For that,  I have a standalone ST25DV64 IC connected on a custom board with a bluetooth module. I would like to do a bluetooth pairing between the bluetooth module and a smartphone via NFC. For that, I am storing the address of the bluetooth module in the NFC EEPROM.

In this setup, the pairing process is unsuccessful (no message on the smartphone asking for pairing confirmation and no auto-connection).

For further understanding :

• I tested the procedure on the ANT7-T-ST25DV64KC evaluation board and the pairing is successful.
• I put the ST25DV64KC IC of the evaluation board on my custom board (with the bluetooth module) and the pairing is successful.
• I put back the standalone ST25DV64 IC on the evaluation board, and the pairing is unsuccessful.
• I tested on other same-series standalone ST25DV64 ICs and the pairing is unsuccessful.

So there is problem (configuration, hardware, ..) on the standalone ST25DV64  ICs that I have.

I compared the 2 ICs static configuration registers and there is no difference (no protection on user memory, same GPO management, ...).

I see a difference on what is marked on the IC. For the standalone IC, I have DV6DERBK134U and the IC on the evaluation board, I have DV6DERC237U. Are the 2 ICs different?

I futher investigated the basic RF operations on the 2 ICs using a NFC Tools application : I can read on both IC types, I can write on IC that was initially on the evaluation board but I can't write on the standalone IC.

 

Regards

[Brian TIDAL]

Hi,

if I understand well, you would like to use the tag to store a bluetooth paring information (such as an NDEF pairing record) but you fail to populate this paring information into the tag and thus you cannot use it to pair your bluetooth equipment. 

Can you dump the content of the tag memory? Is your pairing information using NDEF format and is the tag NDEF formatted? When sending the WRITE SINGLE BLOCK command, what is the error code returned by the tag if any? 

Rgds

BT

[HABIJ.1]

Thank you @Brian TIDAL and @Ulysses HERNIOSUS for the explanations and indications.