I have an issue when the ESP32 is rebooted using the EN pin. After the EN pin is toggled off/then on, I have conflicts with a linux SDIO host and I get SDIO clk timing errors on the host.
A believe this might have something to do with the SDIO CMD (IO15) and/or SDIO CLK (IO14) conflicting with the SDIO host when the ESP32 hits the ROM bootloader.
Are these pins always set to inputs even in the ROM and second stage bootloader? Do they ever change to outputs which might conflict with my linux SDIO host? Perhaps this is a bootstrapping issue withe ROM bootloader? Maybe a JTAG conflict?
Is there a FUSE I can set that might stop this issue?
if I reset the ESP32 using deep sleep, I get no errors when the ESP32 boots from deep sleep mode. This seems to indicate there is some sort of pin conflict in the ROM bootloader since I believe the deep sleep reset skips the ROM bootloader(?).
IO14/IO15 boot conflict in SDIO Slave Mode
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: nopnop2002 and 145 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.