How do i configure my NTAG 424 DNA using the TagXplorer and and my Macbook.
I want to be able to configure my tags in a way like described in the section 4.4.4 (https://www.nxp.com/docs/en/application-note/AN12196.pdf )
So the goal is to have 2 parameters in my URL called "e" and "c" where "e" holds the encrypted version of the UID and the CTR and "c" would hold the cmac value.
Lets say i would like to use the following URL as base "https://ntag.nxp.com/424"
What configuration settings would i need to do in the following two screens? (using default keys is sufficent for my problem at that point)
might there also be other screens where i would have to configure things to be able to achieve my goal?
Thank you :smileyhappy:
Is there a document for TagXplorer that shows the meaning of the various error codes. I have 2 brand new NTAG 424DNA, what I go in to authenticate with default settings the following error comes up: Error: 91AE
My 424 works just fine with my own web service using https:// protocol, but now I need to hand this link over to another service with a particular prefix (smth:// for example). It is on purpose that the protocol combobox does not offer an option for no prefix (0x00)? Am I able to do this somehow within the tool or do I need to modify the APDU command and send it my own way ? Thx for your time!
Sorry for all the questions.
Is there a way to reset the NDEF url after it has been set? Any attempt to change the URL results it an error 6982. I've gone through several of these tags and would like to reuse them.
Any guidance here is appreciated.
Have you figured out eventually how to get rid of that error 6982? I'm experiencing the same issue when trying to change the URL via the mirroring features setup.
Dear jonathaniglesia, please give me a similar step by step instruction for generating a plain URI as in AN12196 4.4.1 that looks like this:
I am completely lost with File settings and Mirroring features that do not match
Hi Manuel Mertl,
Hope you are doing great, all of this steps are assuming that you have a new tag, for this please follow the next steps :
I tested on my side this worked, let me know if you still have any issue or questions or if there is any error on your side.
Have a nice day !!
Thank you so much, works like a charm. I just had to adapt die values for the keys a little bit to get it working with my backend verification. So I ended up with the following configuration for the first test version:
Hey @manuel_mertl I know this conversation is a few years old but hopefully you catch this. I'm exploring how to properly encode and authenticate unique 424 tags for merchandise authentication and ticketing. Any chance you're free to share what you learned?
I'm also new to 424 chips. My company is looking to use them for authenticating goods and also to use the same chips for access control and ticketing.
Here is some background:
I have 1000 tags ready to be embedded in some merchandise for our first collection but they need to be encoded for authentication. We're looking to have authentication services provided by NXP authentication if possible but I'm waiting to hear back from NXP on getting access to that software and service.
We also need to pull the unique ID of each tag or some sort of identifier that we can integrate into our blockchain end for cross verification.
So our needs are : 1. unique ID that we can query for each tag 2. support in encoding the tags 3. authentication support on the backend for our web app and native app.
Ok something weird going on
Mu url structure is:
SDM MAC Input Offset: 66
SDM MAC Offset: 66
PICC Data Offset: 31
I've tried your example again on an additional 2 tags(now uneditable due to error 6982) and now getting the following url structure when I read from the tag
I'm not sure what I'm doing differently from the first time I used the tags. As these are fresh tags Is there some preliminary step I need to do? Do I have to write an NDEF first and then conduct the NTAG Operations?
ok, figured it out.
The application doesn't like sub paths "/1".
have to add an additional 5 to the original calculated amount of 31, 66 respectively. The 5 is the total amount of characters after the first path("/path" )
This was a tricky one. Hope it helps some people out! Cheers
Ok so although the path is correct the iPhone doesn't recognize the url stored. With an NFC reading app the stored URL is padded with what seem to be bytes. I don't think these chips like additional paths ("/") in the query strings. The urls work fine with the example, but adding another folder to the path seem to break things. I'm now all out of test chips.
Just tested on an Android Nokia phone and no issues. This seems to be related to how apple iOS nft reads the tag. I'll keep you posted.
Tested with iPhone 7, iPhone8 , (not reading)