| /Zephyr-latest/tests/subsys/storage/flash_map/src/ |
| D | main.c | 160 bool erased = true; in ZTEST() local
186 while (erased && i < fa->fa_size) { in ZTEST()
194 erased = false; in ZTEST()
199 zassert_true(erased, "Erase failed at dev abosolute offset index %d", in ZTEST()
207 erased = true; in ZTEST()
209 while (erased && i < fa->fa_size) { in ZTEST()
217 erased = false; in ZTEST()
222 zassert_true(erased, "Flatten/Erase failed at dev absolute offset %d", in ZTEST()
|
| /Zephyr-latest/drivers/flash/ |
| D | Kconfig.nrf_mram | 18 Note that MRAM words are auto-erased when written to, but writing to a
19 pre-erased area is faster. Hence, the erase API is not required, but
|
| D | Kconfig.nxp_s32 | 50 bool "Verify memory after erased"
52 Verify contents of memory after erased.
|
| D | Kconfig.simulator | 45 …If selected, writing to a non-erased program unit will succeed, otherwise, it will return an error.
|
| D | Kconfig.mcux | 31 devices will crash when reading an erased or wrongly programmed area.
|
| D | Kconfig | 26 some other value, as program can only change bits from erased-value
|
| /Zephyr-latest/samples/drivers/spi_flash/src/ |
| D | main.c | 51 const uint8_t erased[] = { 0xff, 0xff, 0xff, 0xff }; variable
83 if (memcmp(erased, buf, len) != 0) { in single_sector_test()
159 if (memcmp(erased, buf, len) != 0) { in multi_sector_test()
|
| /Zephyr-latest/doc/services/storage/nvs/ |
| D | nvs.rst | 9 new sector in the flash area is prepared for use (erased). Before erasing the
76 limited life which is determined by the number of times flash can be erased.
77 Flash is erased one page at a time and the pagesize is determined by the
79 page can be erased about 20,000 times.
92 only two sectors, the first sector will be used for storage and will be erased
102 - ``PAGE_ERASES`` as the number of times the page can be erased,
|
| /Zephyr-latest/samples/tfm_integration/psa_protected_storage/ |
| D | README.rst | 37 Note that the board needs to be completely erased before programming the sample, as the flash area
38 used might contain data from before. The board must also be erased between each time the sample is
|
| /Zephyr-latest/samples/drivers/espi/src/ |
| D | main.c | 657 bool erased; in espi_saf_test1() local
672 erased = false; in espi_saf_test1()
674 while (!erased && (retries-- > 0)) { in espi_saf_test1()
695 erased = true; in espi_saf_test1()
710 if (!erased) { in espi_saf_test1()
|
| /Zephyr-latest/boards/nxp/ucans32k1sic/support/ |
| D | startup.cmm | 17 ; erased before the application is downloaded to either Flash *
|
| /Zephyr-latest/subsys/dfu/ |
| D | Kconfig | 74 If enabled, flash is erased as necessary when receiving new firmware,
|
| /Zephyr-latest/boards/nxp/mr_canhubk3/support/ |
| D | startup.cmm | 16 ; erased before the application is downloaded to either Flash *
|
| /Zephyr-latest/samples/net/lwm2m_client/ |
| D | README.rst | 193 Note: If not provisioned (fully erased before flash), device will form
|
| /Zephyr-latest/doc/services/storage/zms/ |
| D | zms.rst | 289 erased/written.
290 Flash devices are erased one page at a time as part of their functional behavior (otherwise
|
| /Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_1.rst | 520 image has been marked for next boot already and may not be erased.
|
| /Zephyr-latest/doc/security/standards/ |
| D | etsi-303645.rst | 634 - The user shall be provided with functionality such that user data can be erased from
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.12.rst | 527 * :github:`6893` - http_client: Struct data is erased for no apparent reason
756 * :github:`8015` - Driver:spi_flash_w25qxxdv.c init mistake and can not be erased
|
| D | release-notes-4.1.rst | 149 data lost from stream flash. There are only two situations where device should be erased
|
| D | release-notes-3.6.rst | 991 * Fixed an issue in MCUmgr image management whereby erasing an already erased slot would return
1027 sent to erase the slot which was already erased.
|
| D | release-notes-2.0.rst | 946 * :github:`16899` - fs/nvs: might loop-up if storage was not erased before first run
|
| D | release-notes-2.5.rst | 872 * flash_map: Added API to get the value of an erased byte in the flash_area,
|
| D | release-notes-2.4.rst | 1716 * :github:`22063` - fs/NVS: NVS is not compatible with flash memories which have 0x00 as erased
|
| D | release-notes-3.2.rst | 1404 to select which image will be erased, using the ``slot`` input
|
