:orphan:

.. title:: SOC_FLASH_RV32M1

.. option:: CONFIG_SOC_FLASH_RV32M1

*RV32M1 flash shim driver*

Type: ``bool``

Help
====

.. code-block:: none

    Enables the RV32M1 flash shim driver.
    WARNING: This driver will disable the system interrupts for
    the duration of the flash erase/write operations. This will
    have an impact on the overall system performance - whether
    this is acceptable or not will depend on the use case.

Direct dependencies
===================

(\ :option:`FLASH <CONFIG_FLASH>` && \ :option:`SOC_OPENISA_RV32M1_RISCV32 <CONFIG_SOC_OPENISA_RV32M1_RISCV32>`) || (\ :option:`HAS_RV32M1_FTFX <CONFIG_HAS_RV32M1_FTFX>` && \ :option:`FLASH <CONFIG_FLASH>`)

*(Includes any dependencies from ifs and menus.)*

Default
=======

- y

Symbols selected by this symbol
===============================

- \ :option:`FLASH_HAS_PAGE_LAYOUT <CONFIG_FLASH_HAS_PAGE_LAYOUT>`
- \ :option:`FLASH_HAS_DRIVER_ENABLED <CONFIG_FLASH_HAS_DRIVER_ENABLED>`

Kconfig definitions
===================



At ``<Zephyr SoC>/riscv/openisa_rv32m1/Kconfig.defconfig:150``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:19`` → ``<BuildDir>/kconfig/Kconfig.soc.defconfig:1``

Menu path: (Top)

.. code-block:: kconfig

    config SOC_FLASH_RV32M1
    	bool
    	default y
    	depends on FLASH && SOC_OPENISA_RV32M1_RISCV32

----

At ``<Zephyr Driver>/flash/Kconfig.rv32m1:4``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:32`` → ``<Zephyr Driver>/Kconfig:60`` → ``<Zephyr Driver>/flash/Kconfig:87``

Menu path: (Top) → Device Drivers → Flash hardware support

.. code-block:: kconfig

    config SOC_FLASH_RV32M1
    	bool "RV32M1 flash shim driver"
    	select FLASH_HAS_PAGE_LAYOUT
    	select FLASH_HAS_DRIVER_ENABLED
    	depends on HAS_RV32M1_FTFX && FLASH
    	help
    	  Enables the RV32M1 flash shim driver.
    	  WARNING: This driver will disable the system interrupts for
    	  the duration of the flash erase/write operations. This will
    	  have an impact on the overall system performance - whether
    	  this is acceptable or not will depend on the use case.

*(The 'depends on' condition includes propagated dependencies from ifs and menus.)*