Hello,
Thank you for your response.
Yes, our application is able to generate and store log data greater than 200 bytes.
We are attaching our current implementation (log_data.zip) based on the t4t-ndef-emulation_example for your reference.
On the reader side, we are using nfcDemoApp poll, which is also based on the linux_libnfc-nci stack.
Our requirement is to retrieve log data (< 8 KB) from a device acting as a Type-4 Tag, using another NFC reader running the same stack.
Currently, even after attempting to construct a larger NDEF message, the reader always reports:
NDEF Content Max size : 134 bytes
and does not read beyond this size.
We understand that for NDEF payloads larger than 255 bytes, the appropriate flags must be configured as per the NDEF specification. However, with the current example and stack, we are unable to read NDEF data larger than this limit.
Could you please help clarify:
Whether the t4t-ndef-emulation_example officially supports large NDEF files (>255 bytes)
Whether nfcDemoApp poll supports reading large NDEF records created by the emulation example
If any additional configuration or stack-level changes are required when using linux_libnfc-nci for this use case
Please let us know if any specific changes are needed in the example code. We would appreciate your guidance.
Best regards,
Niranjan