nRF52 NFC record_text example

RE: nRF52 NFC record_text example

michaeld — Thu, 06 Jul 2017 12:32:46 GMT

Yes BLE works fine and no errors on the NFC Lib functions.

Please take a look at my code: nfc_type2.c

RE: nRF52 NFC record_text example

Jørgen Holmefjord — Thu, 29 Jun 2017 08:17:33 GMT

Is BLE still working on the device after reading using NFC? Have you tried debugging, to see if any error codes are returned?

RE: nRF52 NFC record_text example

michaeld — Wed, 28 Jun 2017 14:40:01 GMT

I tried doing this in my code with softdevice but I can only read the NFC ones and then I cannot read it again. Any idea why this would be the case?

RE: nRF52 NFC record_text example

Arepa — Fri, 17 Mar 2017 14:26:55 GMT

Thanks a lot Jørgen

Sorry for make it an answer too late

RE: nRF52 NFC record_text example

Jørgen Holmefjord — Tue, 14 Feb 2017 13:26:32 GMT

Hi,

This should be possible. The reason that the member of the record descriptor is declared as const is that it must be consistent for the time the encode function works, to avoid that the data get corrupted.

As long as you make sure that the variable does not change during the time the encoder function work, you should be able to ignore the warning or typecast your variable to a constant.

Note that you need to stop and reinitialize the NFC tag emulation when updating the value, by calling nfc_t2t_emulation_stop() and nfc_t2t_emulation_start().

I have attached an example that output a count value on the NFC interface once every second: nfc_record_variable.zip

Best regards,

Jørgen