• State Not Answered
  • Replies 14 replies
  • Subscribers 69 subscribers
  • Views 3022 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 273110
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

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.

Parents Reply Children
  • 0 in reply to ovrebekk

    It does work with the record_text example. The nfc tag is coming up as a mifare tag which I dont think that nfc tools can write to. However, I dont believe the nfc tag was always coming up as a mifare tag. I debugged with someone else who has the board and in there case the tag came up as a different type which nfc tools can write to. The issue seems to be that somewhere in the debugging process when I tested the custom board both the tags I was using all the sudden came up as types that nfc tools can not write to when before the antenna was a type that nfc tools supported. 

  • 0 in reply to peterg0313

    Is there a way that the type of an nfc tag can all of the sudden change in code somehow because it doesnt seem likely?

  • 0 in reply to peterg0313

    Hi

    I guess what you refer to as the tag is just the external antenna that is provided with the DK. 

    All the NFC configuration and data is controlled by the nRF52832 chip, and whatever software you put into it, so it is very odd that you can not get it to behave like before if you erase the nRF52832 flash content and reprogram it with the original example. 

    Have you double checked that the NFC antenna is securely mounted to the connector, and that it didn't get loose?

    Best regards
    Torbjørn

  • 0 in reply to ovrebekk

    Yes I am referring to the external antenna. And as far as I have checked the antenna is in there properly. When I go to read the tag it identifies and reads it so I am not sure why I can't write to it.  I have checked with multiple similar antennas. One another person's board the the firmware still works all together. However, another person who has the development board and the same firmware I wrote has their stuff still working. They did not go through the process of erasing the chip. I did. That's when issues began to arise because I never had these issues before erasing the chip.

    Does the erasing process corrupt the data in some register that is important for nfc wite to work? A third person I tested with had their dev board and erased the chip before uploading code. Then when they tested, they got the same error as I did. It seems to be linked to the erasing of the chip. The error is typically in the form of "this tag type is not supported" when I test with nfc tools, however, when I tested with the other person who faced similar issues their board came up as a ISO 7816 while mine came up as something else, something in the class of mifare tag. I believe ISO 7816 is supported by NFC tools and mifare is not. Yet errors persist. 

  • 0 in reply to peterg0313

    I am seeing that there is a way to reset the cpu of the device completely on the development board. I think it is called NVIC System Reset. How do I do this exactly for the nrf52 implementing sdk 17, or is it a sdk independent process? Do you suggest such a reset for trying to debug this issue? Is there any risk involved?

Related