Hi,
I'm trying to debug a problem were I sometimes get, "Interrupt wdt timeout on CPU0". I have now connected a Espressif JTAG debugger and got it working but have a few problems.
I want the program execution to stop and be able to use the debugger to search for the fault when the exception happens. I have put "debug_init_break = tbreak Reset_Handler" in my platform.ini file but haven't yet been able to get the debugger to break. I get the output "Warn : keep_alive() was not invoked in the 1000 ms timelimit. GDB alive packet not sent! (2037 ms). Workaround: increase "set remotetimeout" in GDB". What exactly does this mean? I was able to change the remotetimeout parameter by adding a .gdbinit file. I have a display connected to the ESP32 which shows the clock. What I see is that I get a couple of these warning messages and after that the clock stops updating but the debugger doesn't break. So what's happening? Any help or additional information how to learn to use the debugger is appreciated.
JTAG Debug ESP32 with GDB in platformio
Jump to
- English Forum
- Explore
- News
- General Discussion
- FAQ
- Documentation
- Documentation
- Sample Code
- Discussion Forum
- Hardware
- ESP-IDF
- ESP-BOX
- ESP-ADF
- ESP-MDF
- ESP-WHO
- ESP-SkaiNet
- ESP32 Arduino
- IDEs for ESP-IDF
- ESP-AT
- ESP IoT Solution
- ESP RainMaker
- Rust
- ESP8266
- Report Bugs
- Showcase
- Chinese Forum 中文社区
- 活动区
- 乐鑫活动专区
- 讨论区
- 全国大学生物联网设计竞赛乐鑫答疑专区
- ESP-IDF 中文讨论版
- 《ESP32-C3 物联网工程开发实战》书籍讨论版
- 中文文档讨论版
- ESP-AT 中文讨论版
- ESP-BOX 中文讨论版
- ESP IoT Solution 中文讨论版
- ESP-ADF 中文讨论版
- ESP Mesh 中文讨论版
- ESP Cloud 中文讨论版
- ESP-WHO 中文讨论版
- ESP-SkaiNet 中文讨论版
- ESP 生产支持讨论版
- 硬件问题讨论
- 项目展示
Who is online
Users browsing this forum: No registered users and 64 guests
- All times are UTC
- Top
- Delete cookies
About Us
Espressif Systems is a fabless semiconductor company providing cutting-edge low power WiFi SoCs and wireless solutions for wireless communications and Internet of Things applications. ESP8266EX and ESP32 are some of our products.