You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/technology/connectivity/NFC.md
+4-7Lines changed: 4 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
-
## NFC
1
+
## NFC
2
2
3
-
NFC stands for Near-Field Communication and is a short-range radio technology. You can use it to enable use cases such as contactless payments, access control or device pairing.
3
+
NFC stands for Near-Field Communication and is a short-range radio technology. You can use it to enable use cases such as contactless payments, access control and device pairing.
You can find more details on NFC about the [NFC Forum's website](https://nfc-forum.org/what-is-nfc/).
8
8
@@ -42,7 +42,7 @@ NFC EEPROMs behave like NFC tags whose memory can either be addressed through a
42
42
43
43
NFC examples are available on [GitHub](https://github.com/ARMmbed/mbed-os-example-nfc) and demonstrate how to create NFC tags that you can be read from and write to using a phone.
44
44
45
-
![An Explore-NFC board attached to a Nucleo board][explorenfc_nucleo]
45
+
<spanclass="images"><span>An Explore-NFC board attached to a Nucleo board</span></span>
46
46
47
47
### API
48
48
@@ -53,6 +53,3 @@ You must initiate either entry point with a driver instance, an event queue and
53
53
### Design
54
54
55
55
A detailed design document is available [within the Mbed OS source tree](https://github.com/ARMmbed/mbed-os/docs/design-documents/nfc/nfc_design.md). It details the rationale behind the API design.
0 commit comments