NFC Write Not Working SDK 17 after working consistently for weeks

[peterg0313]

I am currently trying to test the writable ndef message example on my nrf52 development board. I have gotten it to work so many times in the past weeks but now it seems when I use NFC tools to write a message to the nfc tags I get the error on nfc tools, "write error". I am really confused as to what the issue can be hand have tried almost everything suggested in the forums to no avail. I will provide a screen shot of the appearance of this error message. 

The code is literally the exact writable ndef message example which is why I left it out. Just wondering if any one has some possible solutions or approaches to try. Thank you.

[peterg0313]

Sorry for taking so long to get back I had to travel for work. Yes I looked at Lairds website more closely and they have the following information specified. According to them, they specify that 

This would explain why as soon as I tested on BL652 boards things stopped working on NFC write, NFC read still works.

Do you think there would still be anyway to make NFC write work on the Laird boards by bypassing something with the code or do you think given this it is pretty much unlikely that BL652 will ever run nfc write?

For now, if there is no other way to bypass this on lairds BL652, we may have to design our boards without the NFC feature  since we for now are too strapped on time to change to mrf52832 mcu before sending everything to production but depending on how important the feature is to everyone else at where I work I may have to change to the actual MCU in the next design generation. 

[ovrebekk]

Hi 

In the early days we only had library support for the simpler Type 2 (read only) tags, and only added support for Type 4 tags significantly later. 

Quite possibly Laird based their SmartBASIC interface on our drivers, and as such they adopted the same limitation, without updating them later when we added support for Type 4 tags. 

In other words I am quite sure that what Laird is referring to here is a software limitation in their drivers, not a hardware limitation in the module. 

I would suggest contacting them about this to confirm, but I can't really see how the hardware would be made to support read only. If the antenna is properly tuned for reading it should support writing as well. 

Best regards
Torbjørn