Unable to build esp-idf 5.4.. (i2c)

[petermm]

Recent esp32-camera versions hardcodes next-gen i2c driver usage for idf 5.4: https://github.com/espressif/esp32-camera/blob/4467667b71f22a4c7db226f24105a9350abe7a05/CMakeLists.txt#L88
(which conflicts with AtomVMs current legacy driver usage)

this upstream PR resolves issue: espressif/esp32-camera#746

[UncleGrumpy]

Shoot (pun intended 😉)! I hope they don’t sunset the old interface in future esp-idf releases before 5.3 is EOL, otherwise we will have to update AtomVM to support both. Something tells me we won’t get that lucky.

[petermm]

upstream PR was merged and a new release cut. so we can build on 5.4 now using this sdkconfig:

# use legacy i2c driver, as it's currently used by AtomVM
CONFIG_SCCB_HARDWARE_I2C_DRIVER_LEGACY=y

# CPU runs full speed
CONFIG_ESP_DEFAULT_CPU_FREQ_MHZ_80=
CONFIG_ESP_DEFAULT_CPU_FREQ_MHZ_160=
CONFIG_ESP_DEFAULT_CPU_FREQ_MHZ_240=y

# Flash is in fastest mode
CONFIG_ESPTOOLPY_FLASHMODE_QIO=y
CONFIG_ESPTOOLPY_FLASHFREQ_80M=y

# Enable PSRAM and in fastest mode
CONFIG_SPIRAM=y
CONFIG_SPIRAM_SPEED_80M=y

# Free up some IRAM, so we are within limits
CONFIG_ESP_WIFI_RX_IRAM_OPT=n

[petermm]

For future reference I discovered CONFIG_ESP_SYSTEM_ESP32_SRAM1_REGION_AS_IRAM, which may solve IRAM exhaustion without degrading wifi..