[jira] [Created] (MYNEWT-771) HAL for NRF52 NFCT

["Jeff Chan (JIRA)" <ji...@apache.org>]

Jeff Chan created MYNEWT-771:
--------------------------------

             Summary: HAL for NRF52 NFCT
                 Key: MYNEWT-771
                 URL: https://issues.apache.org/jira/browse/MYNEWT-771
             Project: Mynewt
          Issue Type: Wish
      Security Level: Public (Viewable by anyone)
          Components: HAL
    Affects Versions: WISHLIST
         Environment: NRF52
            Reporter: Jeff Chan
            Assignee: Marko Kiiskila
            Priority: Minor


I would like to use the NFC Tag feature of the NRF52 Chip.

The Nordic SDK supplies a number of .h/.c files to wrap the hardware registers and provide Type 2/Type 4 and NDEF features; Related peripherals such as clock/power control as well as a number of hardware bug fixes.

There's a certain degree of difficulty in just copying in/linking in files because of NRF SDK specific logging commands such as NRF_LOG_INFO.

I suspect that NFC will become a larger part of our lives at some point, so is it something that can be integrated into mynewt? Or should NFC be in a sideline repo?

To what point must we abstract each layer?  For example, should we create a new agnostic NFC Tag layer HAL?  What about read/writes, NDEF or type 2/4 tag layers?  

What I'm aiming at is that there are several layers that all could get their own "mynewt-ified" data structures.  Is it worth the effort?  Can such an effort be effective since the only chips I know of that really integrates NFCT is so far the NRF5 series.  Not as clear as a HAL for i2c for example.

If we decide to pull in such logic "on the side", what's the 'right way' to reuse as much of the Nordic supplied .c/.h files?  Is there a standard way of stripping out proprietary logging while preserving as much of the Hardware Eratta fixes?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)