• State Verified Answer
  • Replies 7 replies
  • Subscribers 73 subscribers
  • Views 5541 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 116697
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Using NFC with SDK12 on nRF52832

Jarmo

The NFC example (launch app) on SDK12 does work on my device. However, when I copy exactly the same code into my own project, the NFC does not work. The difference is that I have S132 soft device flashed, but that does not explain the problem, because I was able to add soft device into the SDK example, and it continued working.

My question is: what are the critical things for NFC to work? For example, do I need to set some specific flags into sdk_config.h? In an earlier question here, concerning SDK11, there was a conclusion that CLOCK_ENABLED must be set for NFC to work. But this is already set on my project, so maybe there is some other hidden thing missing? Wrong clock frequency somewhere? I/O configuration flags? Any ideas what I could try?

Parents
  • 0

    It was some of the Makefile CFLAGS definitions. I copied the flags from the NFC example into my project, and removed the ones that were in my project previously, and got it finally working. I don't know exactly the flag(s) that really did it.

    What are those strange PAN-flags, such as NRF52_PAN_4? Is there a list of them somewhere? I guess PAN does not mean Personal Area Network in this case... :P

    (Apologies, but I am once again so frustrated that I have to say you at Nordic Semiconductor have made a very nice minefields into your SDK. And all those drv_, app_, hal_* and what-not code groups seem to make little or no sense for me, I feel like there's no clear system ideas behind.)

  • 0 in reply to Jarmo

    Thanks for commenting! Okay, hal-drv-app -hierarchy sounds nice, but the problem is that for an application programmer it is not so clear which API should be used for a particular purpose. Yes, lack of intuitivity, lack of self-descriptiveness, that is true. For example, using clear descriptive words instead of three-letter acronyms, starting from files naming would make things a bit better. First days with nRF SDK I just spent wondering what the heck are those bas, dis, hrs etc. things. Luckily some development seem to be happened since then, many of your new files have almost understandable names.

Reply
  • 0 in reply to Jarmo

    Thanks for commenting! Okay, hal-drv-app -hierarchy sounds nice, but the problem is that for an application programmer it is not so clear which API should be used for a particular purpose. Yes, lack of intuitivity, lack of self-descriptiveness, that is true. For example, using clear descriptive words instead of three-letter acronyms, starting from files naming would make things a bit better. First days with nRF SDK I just spent wondering what the heck are those bas, dis, hrs etc. things. Luckily some development seem to be happened since then, many of your new files have almost understandable names.

Children
No Data
Related
Terms of service