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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
bertelschmitt opened this issue Feb 23, 2021 · 3 comments
Open

esp32: CMake not recognizing menuconfig output #6950

bertelschmitt opened this issue Feb 23, 2021 · 3 comments
Labels
port-esp32

Comments

@bertelschmitt
Copy link

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
@bertelschmitt
Copy link
Author

My current workaround is to replace .../esp32/boards.skdconfig.base with the output of menuconfig, which seems to work, but I'm not sure how well.

@wangshujun-tj
Copy link

Modify config. Base and partition table can be compiled successfully
However, after burning, the startup will report the following error:
entry 0x4008063c
�[0;31mE (57) flash_parts: partition 3 invalid - offset 0x200000 size 0xe00000 exceeds flash chip size 0x400000�[0m
�[0;31mE (57) boot: Failed to verify partition table�[0m

@dpgeorge
Copy link
Member

If you have a custom board then the idea is that you would create a custom board definition (eg copy boards/GENERIC to boards/MYBOARD and change as needed). That way you can use the output of menuconfig to create the custom sdkconfig for your board.

@street-grease-coder street-grease-coder mentioned this issue Apr 3, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
port-esp32
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dpgeorge @wangshujun-tj @bertelschmitt
0