full functionality of this site and enable such things as forum posting.
The command "esp_log_level_set("*", ESP_LOG_DEBUG); " allows to change the log level in the code when using an ESP32. However, this seems to be ignored when compiling in uecide, and only the log level set in the IDE is applied and - so it seems - cannot be changed during a run.
Can this be modified so that I can change the log level by code?
As an side, the order of entries in uecide hardware->options->Debug Level suggests a completely wrong order in the chattiness of the selections. This is the order in ESP32:
ESP_LOG_NONE No log output
ESP_LOG_ERROR Critical errors, software module can not recover on its own
ESP_LOG_WARN Error conditions from which recovery measures have been taken
ESP_LOG_INFO Information messages which describe normal flow of events
ESP_LOG_DEBUG Extra information which is not necessary for normal use (values, pointers, sizes, etc).
ESP_LOG_VERBOSE Bigger chunks of debugging information, or frequent messages which can potentially flood the output.
I wouldn't know. That sort of thing is all controlled by the ESP32 core. If you can confirm that it does work in the Arduino IDE or
arduino-cli as expected then it's a bug in UECIDE, but it doesn't sound like it. If it's in the core I can't do anything about it, you'll have to bug the maintainers of the Arduino ESP32 core - but make sure it's not a bug in UECIDE first of course.
As for the ordering, I just order things alphabetically by the key. The keys themselves are taken directly from the upstream ESP32 core configuration files. I guess I could override the ordering with my own custom keys, but that takes effort and programming.
Yeah, it all looks hard coded in the core - with things like:
#if ARDUHAL_LOG_LEVEL >= ARDUHAL_LOG_LEVEL_DEBUG
throughout the code.