-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide NFC Library #5703
Comments
Guys, any progress on that? We will need NFC for a project. I am available to help on that if you can support me (information and help) on creating it. The first I will focus initially on the driver for nRF52832 device. |
@nashif any progress on that? Can I start to work to create the API/Driver? |
@rodrigopex I would suggest just get going on it if you have the cycles |
What do you mean with cycles?
…On Tue, 7 Aug 2018 at 09:51 Peter Robinson ***@***.***> wrote:
@rodrigopex <https://github.com/rodrigopex> I would suggest just get
going on it if you have the cycles
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5703 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACJ0GtmyYfWjlBwzrfM7EiJ-gCPm8OSks5uOY1ugaJpZM4Rg7Wk>
.
|
If you have the time to work on it (the cycles) I'd probably just do so, maybe check on IRC |
We are working on adding an NFC driver supporting nRF52832 and nRF52840 chips to the NRFX driver package (and consequently to Zephyr). The timeline is around end of September - beginning of October. |
Great! If you need help to test it when ready, let me know.
Best regards,
Rodrigo Peixoto
…On Tue, 28 Aug 2018 at 06:59 Michał Grochala ***@***.***> wrote:
Guys, any progress on that? We will need NFC for a project. I am available
to help on that if you can support me (information and help) on creating
it. The first I will focus initially on the driver for nRF52832 device.
We are working on adding an NFC driver supporting nRF52832 and nRF52840
chips to the NRFX driver package (and consequently to Zephyr). The timeline
is around end of September - beginning of October.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5703 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACJ0LNUy7xOpzxdksofn026Tff7WYwgks5uVRSSgaJpZM4Rg7Wk>
.
|
Might be worth sharing the API once you have something ready. The sooner the API is discussed the better IMHO. |
Agree, we can start discussing the API once it gets stable, but let me clarify 2 things already:
|
@grochu is proposing/developing a general NFC driver API for Zephyr in your guy's plan for the future? This issue is something I'm very interested in and was hoping to develop and be apart of in providing a general NFC driver API for Zephyr! |
@aaronhshi yes, we are planning to propose a general NFC API for Zephyr as well. We will come up with an API-only pull request to start the discussion. |
Any updates regarding the status of NFC support for NRF52 SoCs? There's a pull-request #10117 which has since last been touched on April the 30th. It's been marked stale since. |
Any update on this? |
@grochu Is there any snippet yet? |
There is an NFCT driver in the hal/nordic repo: modules/hal/nordic/nrfx/drivers/src/nrfx_nfct.c which supports nRF52 and nRF53 families (devices which have NFCT). At the moment there are no plans of adding a generic Zephyr NFC driver or upper-layer libraries, but we are open to support such activity. |
Happy to see the Nordic nRF52 and 53 supported. Wanted to flag that this may be needed by the Herald Project for Digital Contact Tracing wearable checking-in, or out of band pairing for bluetooth smartphone with wearable (if possible... not sure if any SOCs have readers...), or by a number of covid credentials projects. Our project uses nRF52 and 53 chips as our reference hardware platform so with the comment from @grochu I think we are fine for now. |
any update for generic NFC library? could we steal from MBed? |
you are welcome to submit a PR to support this. |
Is anyone working on this, I could really use it |
I'm working on a driver for the NXP CLRC661 and CLRC663 and ISO15693 and NXP slix protocol layers. All of that is still in work or internal review. I'll try to open a PR around mit october. |
Hi @marcel-ithinx, I've also worked on an NFC proposal (which is far from complete), but maybe can help out for more ideas: I've added the NXP PN5180 driver and ISO14443A subsystem, and tested both reader mode and HCE (Host Card Emulation). You (or anyone) can ping me if desired :) |
(switching to proper account, oops) @pdgendt Uh, that looks great! I didn't implement the NFC driver API abstraction (nfc.h) yet (which you already did). I'm on vacation the next two weeks but after that will have a closer look and probably will try to adapt my stuff to use your nfc.h. Thanks for your response :) |
Hi all! Last year I've been working with NFC on both nRF and NXP platforms. Part of our zephyr port to the qn9090 I actually made a NFC (tag) subsystem, supporting the nRF-NFCT drivers and the nth3x-nfc tag (which is internally located within the qn9090 die). I never bothered making it public, but as part of the qn9090 zephyr 3.4 port, i moved it to public space.
The approach/interface is largely based on the approach nordic took. |
Hi all, An update: I've patches bugs, cleaned the branch/commit and upgraded all nRF drivers. I've included a sample which should run on every nordic device with NFC and devices using the nt3h2 driver. Hessel. |
This is still interesting, any movement on this? |
Today I tried to fix some comments on the PR I created a while ago (#64142). The approach I took is pretty much a proposal, which does work with the nfc-libs of the Nordic MCUs and a different one. Both are used in projectes we develop. |
|
I do still feel this is essentially a necessary addition, why can't we just adopt Nordics NFC implementation they wrote for supporting the NFC-A peripherals on their chips, I understand the current files have a Nordic license on, are they actually opposed to allowing its use on non Nordic platforms? Is there a wider issue at play? |
NFC is a important part of IoT ecosystem and now part of some basic use cases that should be supported by Zephyr.
It is also available on some boards and ICs supported by Zephyr.
A NFC library ported onto Zephyr would allow to extend Zephyr offer and provide more complete use cases.
First priority would be NFC Tag functionality would be sufficient. NFC reader capability would be a lesser prio considering targeted use case by Zephyr devices.
First step of the study would be to establish requested services level (from basic memory write to full NDEF support).
The text was updated successfully, but these errors were encountered: