How To Troubleshoot In Esp32 Boot Mode; When Debugging With Esp32 Jlink, An Error Occurs As: No Symbols For Freertos; How Can I Resolve Such Issue; How To Monitor The Free Space Of The Task Stack - Espressif Systems ESP Faq

Chapter 2. Development environment
2.2.5 How to troubleshoot in ESP32 Boot mode？
• The ESP32-WROVER uses 1.8 V flash and PSRAM, which is 0x33 by default in boot status and
0x23 in download mode.
• Other modules use 3.3 V flash and PSRAM, which are 0x13 by default in boot status and 0x03
in download mode.
• For detailed information, please refer to Section Strapping Pins in
0x13 as an example, the pins are as follows:
Pins
Level
You can also refer to the
2.2.6 When debugging with ESP32 JLINK, an ERROR occurs as: No Symbols For
Freertos. How can I resolve such issue?
This issue will not affect actual operations. For solutions, please go to the

2.2.7 How to monitor the free space of the task stack?

The function vTaskList() can be used to print the available space of the task stack regularly. For
detailed information, please refer to
2.2.8 Is it possible to use JTAG to debug with ESP32-S2？
Yes. For detailed information, please refer to
2.2.9 How to modify the log output without changing the output level of menuconfig？
To modify the log output without changing the output level of menuconfig, you can use the
esp_log_level_set() function. This function allows you to set the log level for a specific module
or subsystem, rather than changing the global log level.
For example, to set the log level for the network module to ESP_LOG_DEBUG, you can use the following
code:
esp_log_level_set("network", ESP_LOG_DEBUG);
For more information about this functinality, please refer to
Espressif Systems
GPIO12 GPIO0 GPIO2
0 1 0
Boot Mode Selection documentation
CSDN Blog.
ESP32-S2 JTAG
Submit Document Feedback
ESP32 Series
GPIO4 GPIO15
0 1
directly.
ST
Debugging.
Logging library.
11
Datasheet. Taking
GPIO5
1
Community.
Release master