Go to file
David Saada d1b5c5e995 Change driver initialization behavior:
- Remove configuration file (base and size taken from driver).
    - Add initializtion variables (is initialized and rinit ref count).
    - Add destructor.
2018-08-07 17:04:24 +03:00
TESTS Working block device 2017-07-19 17:21:41 +01:00
util Working block device 2017-07-19 17:21:41 +01:00
.mbedignore Add default values and ignore utilities 2017-11-01 11:51:40 -07:00
FlashIAPBlockDevice.cpp Change driver initialization behavior: 2018-08-07 17:04:24 +03:00
FlashIAPBlockDevice.h Change driver initialization behavior: 2018-08-07 17:04:24 +03:00
LICENSE Working block device 2017-07-19 17:21:41 +01:00
README.md Change driver initialization behavior: 2018-08-07 17:04:24 +03:00

README.md

Block Device driver build on top of FlashIAP API

Warning

This driver is EXPERIMENTAL and improper usage could kill your board's flash.

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.

Additional concerns:

  • 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.

Configuration

None.

Tested on

  • K82F
  • K64F