Espressif ESP32-S2 Programming Manual page 1229

Chapter 2. API Reference
• Aborts (SPI_FLASH_DANGEROUS_WRITE_ABORTS)
• Fails (SPI_FLASH_DANGEROUS_WRITE_FAILS)
• Allowed (SPI_FLASH_DANGEROUS_WRITE_ALLOWED)
CONFIG_SPI_FLASH_USE_LEGACY_IMPL
Use the legacy implementation before IDF v4.0
Found in: Component config
The implementation of SPI flash has been greatly changed in IDF v4.0. Enable this option to use the
legacy implementation.
Default value:
• No (disabled)
CONFIG_SPI_FLASH_BYPASS_BLOCK_ERASE
Bypass a block erase and always do sector erase
Found in: Component config
Some flash chips can have very high "max"erase times, especially for block erase (32KB or 64KB).
This option allows to bypass "block erase"and always do sector erase commands. This will be much
slower overall in most cases, but improves latency for other code to run.
Default value:
• No (disabled)
CONFIG_SPI_FLASH_YIELD_DURING_ERASE
Enables yield operation during flash erase
Found in: Component config
This allows to yield the CPUs between erase commands. Prevents starvation of other tasks.
Default value:
• Yes (enabled)
CONFIG_SPI_FLASH_ERASE_YIELD_DURATION_MS
Duration of erasing to yield CPUs (ms)
Found in: Component config
If a duration of one erase command is large then it will yield CPUs after finishing a current command.
Default value:
• 20
CONFIG_SPI_FLASH_ERASE_YIELD_TICKS
CPU release time (tick) for an erase operation
Found in: Component config
Defines how many ticks will be before returning to continue a erasing.
Default value:
• 1
Espressif Systems
> SPI Flash driver
> SPI Flash driver
> SPI Flash driver
> SPI Flash driver > CONFIG_SPI_FLASH_YIELD_DURING_ERASE
> SPI Flash driver > CONFIG_SPI_FLASH_YIELD_DURING_ERASE
1218
Submit Document Feedback
Release v4.4