OVMS3-idf/components/spi_flash/CMakeLists.txt

set(priv_requires bootloader_support soc)

if(BOOTLOADER_BUILD)
    if (CONFIG_IDF_TARGET_ESP32)
        # ESP32 Bootloader needs SPIUnlock from this file, but doesn't
        # need other parts of this component
        set(srcs "esp32/spi_flash_rom_patch.c")
    elseif (CONFIG_IDF_TARGET_ESP32S2)
        set(srcs "esp32s2/spi_flash_rom_patch.c")
    else()
        # but on other platforms no source files are needed for bootloader
        set(srcs)
    endif()
    set(cache_srcs "")
else()
    set(cache_srcs
        "cache_utils.c"
        "flash_mmap.c"
        "flash_ops.c"
    )
    set(srcs
        "partition.c")

    if (CONFIG_IDF_TARGET_ESP32)
        list(APPEND srcs
            "esp32/spi_flash_rom_patch.c")
    elseif (CONFIG_IDF_TARGET_ESP32S2)
        list(APPEND srcs 
            "esp32s2/spi_flash_rom_patch.c")
    endif()

    # New implementation after IDF v4.0
    list(APPEND srcs
        "spi_flash_chip_drivers.c"
        "spi_flash_chip_generic.c"
        "spi_flash_chip_issi.c"
        "spi_flash_chip_gd.c"
        "memspi_host_driver.c")

    list(APPEND cache_srcs
        "esp_flash_api.c"
        "esp_flash_spi_init.c"
        "spi_flash_os_func_app.c"
        "spi_flash_os_func_noos.c")

    list(APPEND srcs ${cache_srcs})
    set(priv_requires bootloader_support app_update soc)
endif()

idf_component_register(SRCS "${srcs}"
                    PRIV_REQUIRES "${priv_requires}"
                    INCLUDE_DIRS include
                    PRIV_INCLUDE_DIRS private_include
                    LDFRAGMENTS linker.lf)

# Avoid cache miss by unexpected inlineing when built by -Os
set_source_files_properties(${cache_srcs} PROPERTIES COMPILE_FLAGS
    "-fno-inline-functions -fno-inline-small-functions -fno-inline-functions-called-once")
components: use new component registration api 2019-04-28 07:38:23 +00:00			`set(priv_requires bootloader_support soc)`
ble_mesh_wifi_coexist example: Disable Wi-Fi RX IRAM optimisation Otherwise IRAM usage is too high in this example. 2019-11-28 01:20:00 +00:00
build system: Initial cmake support, work in progress 2018-01-12 02:49:13 +00:00			`if(BOOTLOADER_BUILD)`
Merge branch 'master' into feature/esp32s2beta_merge 2019-10-22 02:51:49 +00:00			`if (CONFIG_IDF_TARGET_ESP32)`
			`# ESP32 Bootloader needs SPIUnlock from this file, but doesn't`
			`# need other parts of this component`
fix dummy issue in spi mem and make some spiflash api called from idf 2019-11-05 05:10:03 +00:00			`set(srcs "esp32/spi_flash_rom_patch.c")`
global: rename esp32s2beta to esp32s2 2020-01-17 03:47:08 +00:00			`elseif (CONFIG_IDF_TARGET_ESP32S2)`
			`set(srcs "esp32s2/spi_flash_rom_patch.c")`
Merge branch 'master' into feature/esp32s2beta_merge 2019-10-22 02:51:49 +00:00			`else()`
			`# but on other platforms no source files are needed for bootloader`
			`set(srcs)`
			`endif()`
esp_flash: fix set qe bit and write command issues There used to be dummy phase before out phase in common command transactions. This corrupts the data. The code before never actually operate (clear) the QE bit, once it finds the QE bit is set. It's hard to check whether the QE set/disable functions work well. This commit: 1. Cancel the dummy phase 2. Set and clear the QE bit according to chip settings, allowing tests for QE bits. However for some chips (Winbond for example), it's not forced to clear the QE bit if not able to. 3. Also refactor to allow chip_generic and other chips to share the same code to read and write qe bit; let common command and read command share configure_host_io_mode. 4. Rename read mode to io mode since maybe we will write data with quad mode one day. 2019-09-05 05:11:36 +00:00			`set(cache_srcs "")`
build system: Initial cmake support, work in progress 2018-01-12 02:49:13 +00:00			`else()`
esp_flash: fix set qe bit and write command issues There used to be dummy phase before out phase in common command transactions. This corrupts the data. The code before never actually operate (clear) the QE bit, once it finds the QE bit is set. It's hard to check whether the QE set/disable functions work well. This commit: 1. Cancel the dummy phase 2. Set and clear the QE bit according to chip settings, allowing tests for QE bits. However for some chips (Winbond for example), it's not forced to clear the QE bit if not able to. 3. Also refactor to allow chip_generic and other chips to share the same code to read and write qe bit; let common command and read command share configure_host_io_mode. 4. Rename read mode to io mode since maybe we will write data with quad mode one day. 2019-09-05 05:11:36 +00:00			`set(cache_srcs`
cmake: some formatting fixes Do not include bootloader in flash target when secure boot is enabled. Emit signing warning on all cases where signed apps are enabled (secure boot and signed images) Follow convention of capital letters for SECURE_BOOT_SIGNING_KEY variable, since it is relevant to other components, not just bootloader. Pass signing key and verification key via config, not requiring bootloader to know parent app dir. Misc. variables name corrections 2019-06-21 06:29:32 +00:00			`"cache_utils.c"`
			`"flash_mmap.c"`
			`"flash_ops.c"`
esp_flash: fix set qe bit and write command issues There used to be dummy phase before out phase in common command transactions. This corrupts the data. The code before never actually operate (clear) the QE bit, once it finds the QE bit is set. It's hard to check whether the QE set/disable functions work well. This commit: 1. Cancel the dummy phase 2. Set and clear the QE bit according to chip settings, allowing tests for QE bits. However for some chips (Winbond for example), it's not forced to clear the QE bit if not able to. 3. Also refactor to allow chip_generic and other chips to share the same code to read and write qe bit; let common command and read command share configure_host_io_mode. 4. Rename read mode to io mode since maybe we will write data with quad mode one day. 2019-09-05 05:11:36 +00:00			`)`
			`set(srcs`
Merge branch 'master' into feature/esp32s2beta_merge 2019-10-22 02:51:49 +00:00			`"partition.c")`

			`if (CONFIG_IDF_TARGET_ESP32)`
			`list(APPEND srcs`
fix dummy issue in spi mem and make some spiflash api called from idf 2019-11-05 05:10:03 +00:00			`"esp32/spi_flash_rom_patch.c")`
global: rename esp32s2beta to esp32s2 2020-01-17 03:47:08 +00:00			`elseif (CONFIG_IDF_TARGET_ESP32S2)`
fix dummy issue in spi mem and make some spiflash api called from idf 2019-11-05 05:10:03 +00:00			`list(APPEND srcs`
global: rename esp32s2beta to esp32s2 2020-01-17 03:47:08 +00:00			`"esp32s2/spi_flash_rom_patch.c")`
Merge branch 'master' into feature/esp32s2beta_merge 2019-10-22 02:51:49 +00:00			`endif()`

esp_flash: fix the quad issue for some GD flash chips The GD flash with product ID 40H, is already used in Wrover-nosufix modules. 2019-09-09 16:56:46 +00:00			`# New implementation after IDF v4.0`
esp_flash: fix coredump for legacy spi flash API When legacy mode is used, the coredump still fails during linking because "esp_flash_init_default_chip", "esp_flash_app_init" and "esp_flash_default_chip " are not compiled and linked. Instead of using ``if`` macros in callers, these functions are protected by ``if`` macros in the header, and also not compiled in the sources. "esp_flash_default_chip" variable is compiled with safe default value. 2019-09-10 06:34:06 +00:00			`list(APPEND srcs`
cmake: some formatting fixes Do not include bootloader in flash target when secure boot is enabled. Emit signing warning on all cases where signed apps are enabled (secure boot and signed images) Follow convention of capital letters for SECURE_BOOT_SIGNING_KEY variable, since it is relevant to other components, not just bootloader. Pass signing key and verification key via config, not requiring bootloader to know parent app dir. Misc. variables name corrections 2019-06-21 06:29:32 +00:00			`"spi_flash_chip_drivers.c"`
			`"spi_flash_chip_generic.c"`
			`"spi_flash_chip_issi.c"`
ble_mesh_wifi_coexist example: Disable Wi-Fi RX IRAM optimisation Otherwise IRAM usage is too high in this example. 2019-11-28 01:20:00 +00:00			`"spi_flash_chip_gd.c"`
			`"memspi_host_driver.c")`
Merge branch 'master' into feature/esp32s2beta_merge 2019-10-22 02:51:49 +00:00
ble_mesh_wifi_coexist example: Disable Wi-Fi RX IRAM optimisation Otherwise IRAM usage is too high in this example. 2019-11-28 01:20:00 +00:00			`list(APPEND cache_srcs`
Merge branch 'master' into feature/esp32s2beta_merge 2019-10-22 02:51:49 +00:00			`"esp_flash_api.c"`
			`"esp_flash_spi_init.c"`
			`"spi_flash_os_func_app.c"`
			`"spi_flash_os_func_noos.c")`
ble_mesh_wifi_coexist example: Disable Wi-Fi RX IRAM optimisation Otherwise IRAM usage is too high in this example. 2019-11-28 01:20:00 +00:00
esp_flash: fix set qe bit and write command issues There used to be dummy phase before out phase in common command transactions. This corrupts the data. The code before never actually operate (clear) the QE bit, once it finds the QE bit is set. It's hard to check whether the QE set/disable functions work well. This commit: 1. Cancel the dummy phase 2. Set and clear the QE bit according to chip settings, allowing tests for QE bits. However for some chips (Winbond for example), it's not forced to clear the QE bit if not able to. 3. Also refactor to allow chip_generic and other chips to share the same code to read and write qe bit; let common command and read command share configure_host_io_mode. 4. Rename read mode to io mode since maybe we will write data with quad mode one day. 2019-09-05 05:11:36 +00:00			`list(APPEND srcs ${cache_srcs})`
components: use new component registration api 2019-04-28 07:38:23 +00:00			`set(priv_requires bootloader_support app_update soc)`
build system: Initial cmake support, work in progress 2018-01-12 02:49:13 +00:00			`endif()`

components: use new component registration api 2019-04-28 07:38:23 +00:00			`idf_component_register(SRCS "${srcs}"`
			`PRIV_REQUIRES "${priv_requires}"`
			`INCLUDE_DIRS include`
			`PRIV_INCLUDE_DIRS private_include`
			`LDFRAGMENTS linker.lf)`
tools: implement linker script generation 2018-04-18 02:57:45 +00:00
esp_flash: fix set qe bit and write command issues There used to be dummy phase before out phase in common command transactions. This corrupts the data. The code before never actually operate (clear) the QE bit, once it finds the QE bit is set. It's hard to check whether the QE set/disable functions work well. This commit: 1. Cancel the dummy phase 2. Set and clear the QE bit according to chip settings, allowing tests for QE bits. However for some chips (Winbond for example), it's not forced to clear the QE bit if not able to. 3. Also refactor to allow chip_generic and other chips to share the same code to read and write qe bit; let common command and read command share configure_host_io_mode. 4. Rename read mode to io mode since maybe we will write data with quad mode one day. 2019-09-05 05:11:36 +00:00			`# Avoid cache miss by unexpected inlineing when built by -Os`
			`set_source_files_properties(${cache_srcs} PROPERTIES COMPILE_FLAGS`
			`"-fno-inline-functions -fno-inline-small-functions -fno-inline-functions-called-once")`