Hello, I have several ESP's in remote locations, and I was quite happy with EspSaveCrash library to investigate some intermittent crashes on ESP8266's. Transitioning to ESP32 I discovered that EspSaveCrash no longer works, due to (I guess) ESP232 doesn't call the custom_crash_callback. That is very disappointing!
Anyway, I found in the standard ESP32 library esp_core_dump.h with some functions that look interesting, like esp_core_dump_to_flash(); and esp_core_dump_to_uart();.
I can successfully compile them but the linker says: undefined reference to esp_core_dump_to_uart()
Any idea? Any suggestions to save crash information "somewhere" and retrieve them after a reboot?
ESP32 remote crash investigation
-
- Posts: 7
- Joined: Tue Mar 02, 2021 3:16 pm
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 99 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.