ST25DV 0xb3 custom command

[fmevoli]

I'm developing an ios app and a need to present a password to write a protected block. I use the custom command 0XB3 that i allready used in the equivalent android app. Unfortunately without success. So I tried with the custom command menu of the NFC tap st app, The custom command, with android work and with ios NO. see the attached pictures. I hope someone can Help me.

.

[victor laraison]

Hi,

I have retested the iOS NFC Tap functionality and confirmed that there is a discrepancy between the UI and the low-level command executed by the app.

To make it work, you must select Addressed Mode and switch off the Manufacturer option, as shown in your screenshot. Although the UI displays both Addressed Mode and UID in the executed command, the actual low-level command operates in Non-Addressed Mode.

When using the customCommand in iOSCoreNFC, the ICMfgcode (for example, 0x02) is automatically appended by iOSCoreNFC itself. Therefore, you should not include this parameter within the customRequestParameters.

Additionally, please note that currently only the Non-Addressed Mode (flag 0x02) seems to be supported. I have not been able to successfully send custom commands in Addressed Mode using iOSCoreNFC, and the reason for this limitation remains unclear.

Hope it helps. Let us know.

[fmevoli]

Dear Victor

I tried as you suggest without success see the attached picture.

From the side of my app in develoopement I tried to send address+Area1+password with the flag address mode disable and the flag high data rate enable and i got the error code 2.

I'm worry because I don't find "present password" in the NFC tap app. seems you don't find a solution and for me is a big problem because our product is allready on the market. Any solutions?

[victor laraison · Accepted solution]

Hi fmevoli,

Apologies for the delayed response. I have conducted additional tests on my side.

I realized I made a mistake in my previous email: you need to select both Addressed mode and Manufacturer in the UI, even though at the lower level (iOS CoreNFC call) they are not utilized.

I tested with the password (01 02 03 04 05 06 07 08), and it works perfectly.

However, we have identified a bug in the "Area security status" menu of the DV when changing the password — the byte order is reversed. We are working on a fix and will resolve it promptly.

Please be assured that the present password has been thoroughly tested during our development and is extensively used in our iOS app.

Sorry for any inconvenience caused.

 

[fmevoli]

Hi Victor Thank you for your help works for me also.

On my app's side, the password was accepted by coreNFC by passing the 0x02 (high data rate) flag and the password composed as follows: 01 (area) + 0102030405060708 (password). I hope this can help other developers.