a282872c78
Add spi flash erase boundary check. The erase boundary must be 4K-aligned. So, the flash chip will round down an non-4K aligned address to the nearest 4K boundary automatically. As a result of this, the erase area will start from a different address (if the API caller specifies an non-4K alighed address), even though the size of the erased area is the same as what is specified by the API caller. Let's add a boundary check to make sure the starting address (from the API caller) is 4K aligned. Correct an error in the highest address check. Because of the error, the erase api call will fail if the flash's highest address byte is involved. Jira: ZEP-1277 ZEP-1278 Change-Id: I8b6be57cc8f636f94e5fe67d5a492841a8555005 Signed-off-by: Baohong Liu <baohong.liu@intel.com> |
||
|---|---|---|
| .. | ||
| Kconfig | ||
| Makefile | ||
| soc_flash_ksdk.c | ||
| soc_flash_nrf5.c | ||
| soc_flash_qmsi.c | ||
| spi_flash_w25qxxdv.c | ||
| spi_flash_w25qxxdv.h | ||
| spi_flash_w25qxxdv_defs.h | ||