Mike

> We then don't need the custom sming choco scripts: we should remove those from documentation. >> Lets keep it for this release, and announce that choco is deprecated. We...

See also https://sming.readthedocs.io/en/latest/information/tips-n-tricks.html#reading-vcc-on-esp8266 which would be affected.

Comparing build logs between IDF 4.4 and IDF 5.2: ``` tests/HostTests log data rodata bss iram_text text Total Used RAM Free RAM Free IRam ----------------- ----- ------ ----- --------- -------...

IDF 5 adds `esp_newlib_init_global_stdio` which results in various I/O code from newlib being linked. Not a lot though.

Building with WPA3 disabled reduces size: **IDF 4.4** ``` ESP_WIFI_ENABLE_WPA3_SAE=n ``` app.bin: 1,017,424 bytes ``` HostTests: Linking out/Esp32/esp32/debug/build/app.out Section| Description| Start (hex)| End (hex)|Used space ------------------------------------------------------------------------------ data| Initialized Data (RAM)|...

Release builds are very similar between IDF 4.4 and 5.2. Conclusion: More debug code/text in IDF 5.2. IDF 4.4 ``` HostTests: Linking out/Esp32/esp32/release/build/app.out Section| Description| Start (hex)| End (hex)|Used space...

You could try mucking around with some of the IDF settings, see if that makes a difference. Also try reducing debug verbosity as debug messages take up space. For example:...

The esp32 series have better virtual memory management hardware and aren't limited to 1MByte AFAIK.

See issue #2758. 1. Build with `STRICT=1` to allow compilation to continue 2. Fix the problem. i.e. you're using an old IDF version (4.3 or 4.4)

Ah, I see. The default IDF installed is version 4.4, we should probably update that to 5.2.