Bug fix: NDEF not detected.
The NFC Forum Type 4 specifications mention that values 0x80 to 0xFE for
the NDEF file
write access condition byte are proprietary. In the current Android
stack those values are considered
incorrect. Being considered incorrect when the Tag value is different
from 0x00 or 0xFF, the stack
returns an error leading to a non detection of an NDEF message.
Here below the logcat:
12-17 03:37:01.157 3321 3628 E BrcmNfcNfa: rw_t4t_validate_cc_file ():
Write Access (0x80) is invalid
12-17 03:37:01.157 3321 3628 E BrcmNfcNfa: rw_t4t_handle_error ():
status:0xE7, sw1:0x00, sw2:0x00, state:0x2
According Type 4 specifications 0x80 is valid.
Test: Nexus 6P native tag detection on ST25TA (Type 4) from ST
Microelectronics
Change-Id: I87e9b63d6e78dd19273103373924b1a207e48a1a
Signed-off-by: Raphael Collado <raphael.collado@st.com>
diff --git a/src/nfc/include/tags_defs.h b/src/nfc/include/tags_defs.h
index 66b2875..c53b82b 100644
--- a/src/nfc/include/tags_defs.h
+++ b/src/nfc/include/tags_defs.h
@@ -514,6 +514,8 @@
#define T4T_FC_READ_ACCESS 0x00
/* write access granted without any security */
#define T4T_FC_WRITE_ACCESS 0x00
+/* proprietary write access range start */
+#define T4T_FC_WRITE_ACCESS_PROP_START 0x80
/* no write access granted at all (read-only) */
#define T4T_FC_NO_WRITE_ACCESS 0xFF