Skip to main content
Visitor II
August 8, 2023
Solved

I am getting error while typing password to st25dv64k encrypted tag

  • August 8, 2023
  • 2 replies
  • 1371 views

Hello,

I want to write the password value to the st25dv64k tag and write data to the blocks. I get an error when I want to write data in the mobile iOS operating system. Here I am using ISO15693 technology. I'm trying to write the password as follows using the customCommand function. Here is the function I use:

 

NfcManager.iso15693HandlerIOS.customCommand(
flags = numbers,
customCommandCode = number,
customRequestParameters= number[] );

 

The codes generated according to this function are as follows:

 

try {
const idBytes=[7,6,5,4,3,2,1,0];
const passwordBytes= [0,0,0,0,0,0,0,0,0]
resp = await NfcManager.iso15693HandlerIOS.customCommand({
flags=0x02,
custom Command Code = 0xb3,
custom Request Parameters = [
0x02, //IC Mfg code
...idBytes, // device id =[7,6,5,4,3,2,1,0]
0x02, // Passwordnumber
...passwordBytes, // Password =[0,0,0,0,0,0,0,0]
],
});
}
catch(ex) {
console.log('error',ex.message);
} finally {
console.log("Finally..");
}

 

I'm getting an error like the one I tried above:

Error [error].

I tried many changes in the above codes, but I could not come to a conclusion. What should I do accordingly? Can you help me ?

    This topic has been closed for replies.
    Best answer by victor laraison

    hello Kamilsever,

    I answered your colleague in the post https://community.st.com/t5/st25-nfc-rfid-tags-and-readers/i-had-a-problem-sending-the-0xb3-custom-command-using-the/td-p/576646

    Problem comes the fact that this command works only in NON-ADDRESSED mode. So, you must use flags = 0x02 and remove the IC + UID paramaters from the data passed. 

    Hope it helps.
    Br,

     

    2 replies

    ST Employee
    August 16, 2023

    Hello

    I see that you use @ mode, i suggest that you use 0x22 for Flags

    For information:

    In addressed mode (i.e. with UID parameter in the request), the Address_flag (bit 6) shall be set to 1. Usually Data_rate_flag (b2) is also set to 1 (High data rate shall be used):

    b8 b7 b6 b5 b4 b3 b2 b1
     0 0 1 0 0 0 1 0
     0 Sub-carrier_flag: A single sub-carrier frequency shall be used by the VICC
     1 Data_rate_flag: High data rate shall be used
     0 Inventory_flag: Flags 5 to 8 meaning is according to table 4
     0 Protocol Extension_flag: No protocol format extension
     0 Select_flag
     1 Address_flag Request is addressed. UID field is included
     0 Option_flag
     0 RFU

    For further information on request flags, see ISO/IEC 15693-3.

    Hope this will help

    BR,FB

    Visitor II
    August 18, 2023

    Hello, I tried the flag address 0x22 in this way, but I still get the same error. Is there any other solution?

    I downloaded your application on iOS, where you do most of the password operations. I would be very happy if you could get information about this issue from the friends working on the mobile application side.

    Thank you for your attention

    ST Employee
    September 14, 2023

    hello Kamilsever,

    I answered your colleague in the post https://community.st.com/t5/st25-nfc-rfid-tags-and-readers/i-had-a-problem-sending-the-0xb3-custom-command-using-the/td-p/576646

    Problem comes the fact that this command works only in NON-ADDRESSED mode. So, you must use flags = 0x02 and remove the IC + UID paramaters from the data passed. 

    Hope it helps.
    Br,