Open dhalbert opened 2 years ago
Those logs are likely coming from the boot rom and there behavior is controlled by permanent setting of eFuse bit(s). From: https://docs.espressif.com/projects/esp-idf/en/v5.0/esp32s2/api-reference/kconfig.html#config-boot-rom-log-scheme
CONFIG_BOOT_ROM_LOG_SCHEME Permanently change Boot ROM output
Found in: Boot ROM Behavior
Controls the Boot ROM log behavior. The rom log behavior can only be changed for once, specific eFuse bit(s) will be burned at app boot stage.
Available options: Always Log (BOOT_ROM_LOG_ALWAYS_ON)
Always print ROM logs, this is the default behavior.
Permanently disable logging (BOOT_ROM_LOG_ALWAYS_OFF)
Don’t print ROM logs.
Log on GPIO High (BOOT_ROM_LOG_ON_GPIO_HIGH)
Print ROM logs when GPIO level is high during start up. The GPIO number is chip dependent, e.g. on ESP32-S2, the control GPIO is GPIO46.
Log on GPIO Low (BOOT_ROM_LOG_ON_GPIO_LOW)
Print ROM logs when GPIO level is low during start up. The GPIO number is chip dependent, e.g. on ESP32-S2, the control GPIO is GPIO46.
At least some Espressif boards print out bootloader startup info on hard reset. We can turn this off, but I wasn't sure if it had been turned on deliberately at some point.
I am not sure if it confuses Thonny sometimes. Thonny sometimes crashes hard the first time I try to connect to an ESP32 board.
It does help you see that the board is boot-looping if it resets before CircuitPython prints anything.
@MicroDev1 @UnexpectedMaker and anyone else -- do you have an opinion?