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
The `NFCEEPROM` class derives from `NFCTarget` and shares the same API.
296
+
A pointer to a `NFCEEPROMDriver` instance (see below) must be passed in the constructor.
296
297
297
298
#### NFC Remote Target
298
299
@@ -491,33 +492,38 @@ in an object oriented fashion.
491
492
492
493
### NFC EEPROM API
493
494
494
-
The one HAL API that will have to be implemented by vendors to make use of the `NFCEEPROM` class are the following virtual methods.
495
+
The one HAL API that will have to be implemented by vendors to implement a `NFCEEPROMDriver` driver are the following virtual methods.
495
496
496
497
From the upper layer's point of view, the EEPROM is a byte array that can be read from/written to. Long operations (reads, writes, erasures) must happen asynchronously. Booleans indicate whether a particular operation was succesful. Encoding is handled by the upper layer.
497
498
498
499
Address 0 means the start of the NDEF buffer (not necessarily at address 0 in the EEPROM).
499
500
500
501
When a buffer is passed to the backend, the reference remains valid till the corresponding event is called.
501
502
502
-
The `backend_set_size()` command is called to change the size of the buffer (within the limits set by `backend_get_max_size()`). Inversely that buffer size can be read by `backend_get_size()`.
503
+
The `set_size()` command is called to change the size of the buffer (within the limits set by `get_max_size()`). Inversely that buffer size can be read using `get_size()`.
504
+
505
+
`start_session()` and `end_session()` are used before a series of memory operations to allow the driver to lock/un-lock the RF interface during these operations to avoid having concurrent access to the memory.
0 commit comments