Hello, my ntag 424 is not detectable by any NFC device, except put the NDEF message and the reading right on 0E ARE THERE Other configurations for it to be detected by a smartphone?
as you can see you have modified the write access of the CC file to the NDEF file, the capability container have data used for NDEF management, so to detect and access NFC Forum defined data, the device has this CC file.
your CC file: 001720010000FF0406E104010000FF0506E10500808283000000000000000000
new NTAG 424 cc file :001720010000FF0406E104010000000506E10500808283000000000000000000
you have modified the CC file so there is no write access,
you can see this in the NFC forum specification of T4T and in section 220.127.116.11 try to set this back to 00 and perform the NDEF storage.
Hello my tests worked on other terminals, I was also able to achieve the objective of @manuel_mertl thread (https://community.nxp.com/t5/NFC/Configuring-NTAG-424-DNA-with-Encrypted-Part-and-CMAC-Part/m-p/1049315), I will come back in another thread for the rest (ACCES CONTROL system)
can you confirm that you have done the steps I explain in the following steps ?
also please share the value of the capability container file,
to check if you have changes the read access conditions.
yes I understand the method used in this thread https://community.nxp.com/t5/NFC/Configuring-NTAG-424-DNA-with-Encrypted-Part-and-CMAC-Part/m-p/1049315 but I just want to launch the browser of the smartphone (simple url) is this config necessary?
if you dont want a SUN inside your tag, just a simple URL, it is very simple:
if you are using TagXplorer do the following:
after this the tag should be able to be read by a phone, this is done if you have not modified anything to the tag, if you have changed the access conditions of the tag or something you should first authenticate, also be sure that you have not modified the CC file, this fille will tell the phone the memory, the reading rights and write rights, and other information you can see in the DS.