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: README.md
+2-16Lines changed: 2 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,27 +6,13 @@ This driver is **EXPERIMENTAL** and improper usage could kill your board's flash
6
6
This driver should only be used on platforms where the FlashIAP implementation is using external flash or in conjunction with a filesystem with wear leveling, that can operate on a page size granularity.
7
7
8
8
Additional concerns:
9
-
- The BlockDevice API assumes a uniform erase size so the underlying flash must also have uniform sectors.
10
9
- The FlashIAP may freeze code execution for a long period of time while writing to flash. Not even high-priority irqs will be allowed to run, which may interrupt background processes.
11
10
12
11
13
12
## Configuration
14
-
15
-
The driver must be configured with the starting address for the internal flash area reserved for the block device and it's size in bytes. In the application's `mbed_app.json`, add the following lines:
16
-
17
-
```json
18
-
{
19
-
"target_overrides": {
20
-
"K64F": {
21
-
"flashiap-block-device.base-address": "<internal flash address where the block device starts>",
22
-
"flashiap-block-device.size": "<number of bytes allocated to the internal flash block device>"
0 commit comments