For tag_1:
Payload Len
3B = 59 bytes, from ( [00d] byte:0 ) to ( [01b] byte:2 ), byte:3=0xfe
FOUND INCORRECT COUNT HERE
______________________________________________________________
For tag_2:
NDEF
Tlv tLv
03 89 NDEF length = 137 bytes ( NOT counting 0xfe terminator )
FOUND INCORRECT COUNT HERE
--------------
RECORD 2
payload LENGTH
19 = 25 bytes, from ([020] byte:2 ) to ([026] byte:2 )
FOUND INCORRECT COUNT HERE
_________________________________________________________________
Length errors have been corrected per your advise.
In testing I noticed (with no app running) when the phone scans the
NXP-NFC-Explorer board, an app picker opens. The tag in the Explorer
board uses a Smart Poster configuration, and it appears the last
record is an AAR for com.nxp.ntagi2cdemo... but it never opens automatically,
I thought that was the purpose of the AAR ((or was this left as an exercise?? ))
and this leads me to question the validity of my RTD, AAR and TYPE names.
The FORMAT of tag_2.png AAR and that of the Explorer board Smart Poster
AAR seem to match (at least to me, they do).
I am doing something incorrectly with the AAR, or the RTD/TYPE names??
Your example uses only a single character for the RTD, I did try to follow
the NFC Forum spec document for tag_1.png EXTERNAL type, length = 26 : 0x1a
--> blackfeathersystems.com:pr though it is not explained on HOW to
use it, only this is how it is intended for it to appear.
thanks! I do appreciate your assistance.