Root cause (verified against our exact IDF tree, not the community guess): the "258" in "sdio_write_task: Failed to send data: 258" is NOT a timeout (that is 263). 258 = 0x102 = ESP_ERR_INVALID_ARG. On the ESP32-P4, block- mode CMD53 writes require the SOURCE buffer to be 64-byte (cache-line) aligned; the IDF sdmmc driver rejects a misaligned source with INVALID_ARG BEFORE any bus activity. esp_hosts write loop then declares "Unrecoverable host sdio state" and reboots the whole P4. The audio TX payload is not 64-aligned, so streaming mic audio wedged on the very FIRST frame (which is exactly what we saw: listening -> instant Failed to send -> reboot). This also explains why buffer/queue/clock/retry tuning all did nothing: the write never reached the bus. And why our symptom was instant, not after ~100 writes (the community block-mode-desync theory) — it is the first misaligned buffer, every time. Fix: vendored esp_hosted 2.12.11 as an editable local component (overrides the registry copy) and bounce a misaligned TX payload through one aligned DMA scratch buffer in hosted_sdio_write_block (port_esp_hosted_host_sdio.c). TX is serialized by the bus lock so a single static bounce buffer is safe; freed in hosted_sdio_deinit. Host-only change — no C6 reflash. VERIFIED ON HARDWARE (autonomous self-test): 40s of continuous mic-audio upstream streaming — the traffic that previously wedged on the first frame — ran clean, zero timeouts, zero reboots. A guarded SDIO_TX_SELFTEST harness is kept (compiled out) for future SDIO stress testing. Credit: root cause + patch designed via multi-agent investigation; the precise 258=INVALID_ARG decode (correcting the upstream community timeout assumption) came from checking our actual esp_err.h. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1.7 KiB
1.7 KiB
Features Implemented in ESP-Hosted-MCU
This page documents the features implemented by ESP-Hosted-MCU.
Wi-Fi
- Station (scan, connect to an AP)
- SoftAP (configure, start, stop)
- SoftAP+Station
- (Optional) Network Split for splitting network traffic support between the co-processor and the host
- (Optional) iTWT (individual Target Wake Time) Wi-Fi 6 (802.11ax) feature that lets a station negotiate its own wake/sleep schedule with an iTWT supporting AP to reduce power consumption
- only works with co-processors that support iTWT like the ESP32-C6 and ESP32-C5
- (Optional) Wi-Fi Enterprise security mode for enhanced security in business environments
- (Optional) Wi-Fi Easy Connect (DPP) to securely onboard devices by scanning a QR code (displayed by the host) without entering a Wi-Fi password
- requires a smartphone that supports Wi-Fi Easy Connect to scan the QR code and start the onboarding operation
- APIs added:
esp_supp_dpp_initesp_supp_dpp_deinitesp_supp_dpp_bootstrap_genesp_supp_dpp_start_listenesp_supp_dpp_stop_listen
Bluetooth
- ESP-Hosted / UART HCI support for ESP-Nimble and ESP-Bluedroid. See Bluetooth Design for more information
OpenThread
- ESP-Hosted / Dedicated UART support for ESP OpenThread / Zigbee. See OpenThread / Zigbee Support for more information
Miscellaneous
- (Optional) Host Power Save to allow Host to go to sleep and be waken by co-processor
- (Optional) GPIO Expander to allow the host to control the GPIOs of the slave.