nRF52832 + PN532 Write

RE: nRF52832 + PN532 Write

Simonr — Tue, 28 Jun 2022 11:40:57 GMT

The three parameters that are used in an NDEF Update procedure are the following. and twith the following description:

 * @param[in]     p_cc_file          Pointer to the Capability Container descriptor.
 * @param[in]     p_ndef_file_buff   Pointer to the buffer with NDEF file.
 * @param[in]     ndef_file_buff_len Length of the provided NDEF file.

When you get an INVALID_LENGTH error, the length of the provided NLEN value is not coherent with the NDEF file buffer length, or the buffer length is bigger than maximal file size.

Best regards,

Simon

RE: nRF52832 + PN532 Write

Sunil vignesh — Wed, 22 Jun 2022 14:02:54 GMT

Still I have this same problem

why this error 0x09 invalid length come

how to set the length properly

RE: nRF52832 + PN532 Write

Susheel Nuguru — Wed, 22 Jun 2022 06:47:02 GMT

Sorry for the late response, Most likely you have already fixed this. we do not have an example to show this but I do not see why this could not work. The error says that it is an invalid length with the parameters,

tag_data_read should be returning errors that should be handled in nfc_tag_process and in our examples it seems that this invalid length should not be returned from the tag_data_read. Can you tract the call stack from where this error is returned?