-
-
Notifications
You must be signed in to change notification settings - Fork 741
-
-
Notifications
You must be signed in to change notification settings - Fork 741
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
NRF5x SDK 14.2 & NFC #1320
Comments
That would be a huge help, yes! Thanks! I had a quick look at the diffs, but it looked like a reasonably big chunk of work for me given I don't really know what goes on internally :) To be SDK14 building all you should have to do is copy in the SDK, then swap over the commented sections at the top of NRF52.make |
With 14 Nordic added almost all features I had to implement on top of 13. I anticipate a significantly cleaner look in 14. Is it sufficient if I complete a stable version by the end of February 2018? |
Yes - that'd be great! Honestly I'm just really happy that you're willing to do it at all! |
I've reworked my NFC patches so they apply on top of SDK 14.2.0. One tiny incompatibility remains Nordic defined with SDK14 0001-NFC-Removed-NDEF-frontend-prepared-raw-backend.patch.gz (Sorry about the gzips but GitHub doesn't let me upload patches.) |
That's great - thanks! Really handy to have a patch set too so hopefully it'll be a bit easier to merge in to newer SDKs. I guess from the point of view of making it easier to move to new SDKs, we could rename your HAL_NFC_PARAM_ID_UID to HAL_NFC_PARAM_ID_NFCID1? But I can do that later. |
I've prepared the backport in #1347 |
Thanks! Not sure how I missed this when I was looking :( |
Hi Gordon
I've noticed you started preparing for an bump of Nordics SDK to 14.x. Some of my NFC customisations do conflict with Nordics changes others are rendered obsolete by Nordics
own implementation.
Would it help if I would port my NFC extensions to SDK 14.2?
The text was updated successfully, but these errors were encountered: