8000 esp32: CMake not recognizing menuconfig output · Issue #6950 · micropython/micropython · GitHub
[go: up one dir, main page]

Skip to content
esp32: CMake not recognizing menuconfig output #6950
Open
@bertelschmitt

Description

@bertelschmitt

I am compiling for GENERIC_SPIRAM. The new CMake version requires (among other things) the size of the flash memory to be set via menuconfig. However, on running make, the settings written to …/build/sdkconfig are not reflected in .../build-GENERIC_SPIRAM/sdkconfig or .../build-GENERIC_SPIRAM/sdkconfig.combined.
For instance, setting the flash size to 16MB in menuconfig produces this in …/build/sdkconfig

# CONFIG_ESPTOOLPY_FLASHSIZE_1MB is not set
# CONFIG_ESPTOOLPY_FLASHSIZE_2MB is not set
# CONFIG_ESPTOOLPY_FLASHSIZE_4MB is not set
# CONFIG_ESPTOOLPY_FLASHSIZE_8MB is not set
CONFIG_ESPTOOLPY_FLASHSIZE_16MB=y
CONFIG_ESPTOOLPY_FLASHSIZE="16MB"

However, the pertinent entries in …/build-GENERIC_SPIRAM/sdkconfig read like this:

# CONFIG_ESPTOOLPY_FLASHSIZE_1MB is not set
# CONFIG_ESPTOOLPY_FLASHSIZE_2MB is not set
CONFIG_ESPTOOLPY_FLASHSIZE_4MB=y
# CONFIG_ESPTOOLPY_FLASHSIZE_8MB is not set
# CONFIG_ESPTOOLPY_FLASHSIZE_16MB is not set
CONFIG_ESPTOOLPY_FLASHSIZE="4MB"
CONFIG_ESPTOOLPY_FLASHSIZE_DETECT=y

This causes compilation of code for 4MB, which is not desired.
Apparently, make picks up defaults from /esp32/boards/sdkconfig.base while ignoring the settings produced by menuconfig.

If I make the following edit in /esp32/boards/sdkconfig.base, the compile finishes successfully:

#CONFIG_ESPTOOLPY_FLASHSIZE_4MB=y
CONFIG_ESPTOOLPY_FLASHSIZE_16MB=y

However, this is not the desired solution

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0