I use std::map, std::string, std::vector, find and iterators. The error messages are not nice and some things need just as much care for memory management as malloc/free because you can easily run out of PSRAM, it comes down to design and algorithm, and appropriate use and I would not criticise C++ ...

Anyone?

Is that loop ever going to be blocked/yield or just burn up CPU cycles?

I've been reading the documentation and include files on Bluetooth classic and looking at examples, but am new to Bluetooth and struggling. My desired use case is to get an ESP32 to become a Bluetooth source to be able to send track/artist strings/metadata to a bluetooth sink device that is a media ...

I got into the habit of only adding the encryption tags in the partition table only when flash encryption was enabled. It was not mentioned in docs, but it solved a few problems if I recall switching between flash encryption on or off.

Update: despite the smaller size, the toolchain and applications built with it do work.

Even if I rename the original toolchain, builds still work, but the new toolchain is 300MB smaller!!?? I guess I just don't understand these symbolic links and where they point to.

Toolchain path: /opt/xtensa-esp32-elf-new/bin/xtensa-esp32-elf-gcc WARNING: Toolchain version is not supported: crosstool-ng-1.22.0-98-g4638c4f6 Expected to see version: crosstool-ng-1.22.0-80-g6c4433a Please check ESP-IDF setup instructions and update the toolchain, or proceed at your own risk. Co...

# Automatically download precompiled toolchain, unpack at /opt/xtensa-esp32-elf/ TOOLCHAIN_ZIP=xtensa-esp32-elf-win32-1.22.0-80-g6c4433a-5.2.0.zip echo "Downloading precompiled toolchain ${TOOLCHAIN_ZIP}..." cd ~ curl -LO --retry 10 http://dl.espressif.com/dl/${TOOLCHAIN_ZIP} cd /opt rm -rf /opt/xt...

I used 7zip in administrator mode (so it was able to create symbolic links) to unpack the tar in a new directory.