rpc_core: Timeout (EHM-56)

[Big-mouth-c]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate.
• Provided a clear description of your suggestion.
• Included any relevant context or examples.

Issue or Suggestion Description

I configured a third-party ESP32-P4 and ESP32-C6 using the ESP-Hosted SPI FD (Full Duplex) Operation mode and used the iperf example for testing, but a timeout issue occurred. The ESP32-P4 and ESP32-C6 are two separate development boards connected with short jumper wires. I'm not sure where the problem lies. Do you have any suggestions? (It seems that pull-up resistors are not needed in SPI FD mode.)

ESP32P4
I (28) boot: ESP-IDF v5.4.1-dirty 2nd stage bootloader
I (28) boot: compile time May 31 2025 11:03:20
I (29) boot: Multicore bootloader
I (30) boot: chip revision: v1.0
I (32) boot: efuse block revision: v0.3
I (35) boot.esp32p4: SPI Speed : 40MHz
I (39) boot.esp32p4: SPI Mode : DIO
I (43) boot.esp32p4: SPI Flash Size : 16MB
I (47) boot: Enabling RNG early entropy source...
I (51) boot: Partition Table:
I (54) boot: ## Label Usage Type ST Offset Length
I (60) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (67) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (73) boot: 2 factory factory app 00 00 00010000 00100000
I (80) boot: End of partition table
I (83) esp_image: segment 0: paddr=00010020 vaddr=40070020 size=286ach (165548) map
I (123) esp_image: segment 1: paddr=000386d4 vaddr=30100000 size=0000ch ( 12) load
I (124) esp_image: segment 2: paddr=000386e8 vaddr=3010000c size=00038h ( 56) load
I (127) esp_image: segment 3: paddr=00038728 vaddr=4ff00000 size=078f0h ( 30960) load
I (142) esp_image: segment 4: paddr=00040020 vaddr=40000020 size=6c7f4h (444404) map
I (229) esp_image: segment 5: paddr=000ac81c vaddr=4ff078f0 size=0e040h ( 57408) load
I (243) esp_image: segment 6: paddr=000ba864 vaddr=4ff15980 size=0218ch ( 8588) load
I (250) boot: Loaded app from partition at offset 0x10000
I (250) boot: Disabling RNG early entropy source...
I (260) cpu_start: Multicore app
I (270) cpu_start: Pro cpu start user code
I (270) cpu_start: cpu freq: 360000000 Hz
I (270) app_init: Application information:
I (271) app_init: Project name: iperf
I (274) app_init: App version: 1
I (277) app_init: Compile time: May 31 2025 11:22:29
I (282) app_init: ELF file SHA256: cd9899512...
I (287) app_init: ESP-IDF: v5.4.1-dirty
I (291) efuse_init: Min chip rev: v0.1
I (295) efuse_init: Max chip rev: v1.99
I (299) efuse_init: Chip rev: v1.0
I (303) heap_init: Initializing. RAM available for dynamic allocation:
I (309) heap_init: At 4FF1A720 len 000208A0 (130 KiB): RAM
I (314) heap_init: At 4FF3AFC0 len 00004BF0 (18 KiB): RAM
I (319) heap_init: At 4FF40000 len 00060000 (384 KiB): RAM
I (325) heap_init: At 50108080 len 00007F80 (31 KiB): RTCRAM
I (330) heap_init: At 30100044 len 00001FBC (7 KiB): TCM
I (336) spi_flash: detected chip: generic
I (339) spi_flash: flash io: dio
I (342) host_init: ESP Hosted : Host chip_ip[18]
I (346) H_API: ESP-Hosted starting. Hosted_Tasks: prio:23, stack: 5120 RPC_task_stack: 5120
spi_mempool_create free:163516 min-free:163516 lfb-def:122880 lfb-8bit:122880

I (361) spi_wrapper: Transport: SPI, Mode:3 Freq:1MHz TxQ:20 RxQ:20
GPIOs: MOSI:14 MISO:15 CLK:18 CS:19 HS:16 DR:17 SlaveReset:45
I (374) H_API: ** add_esp_wifi_remote_channels **
I (377) transport: Add ESP-Hosted channel IF[1]: S[0] Tx[0x4000edc6] Rx[0x4001cbf0]
--- 0x4000edc6: transport_drv_sta_tx at D:/vscodeidf/iperf4/iperf/managed_components/espressif__esp_hosted/host/drivers/transport/transport_drv.c:219
--- 0x4001cbf0: esp_wifi_remote_channel_rx at D:/vscodeidf/iperf4/iperf/managed_components/espressif__esp_wifi_remote/esp_wifi_remote_net.c:19

I (385) transport: Add ESP-Hosted channel IF[2]: S[0] Tx[0x4000ed0c] Rx[0x4001cbf0]
--- 0x4000ed0c: transport_drv_ap_tx at D:/vscodeidf/iperf4/iperf/managed_components/espressif__esp_hosted/host/drivers/transport/transport_drv.c:249
--- 0x4001cbf0: esp_wifi_remote_channel_rx at D:/vscodeidf/iperf4/iperf/managed_components/espressif__esp_wifi_remote/esp_wifi_remote_net.c:19

I (393) spi: No element in any queue found
I (394) os_wrapper_esp: GPIO ISR service installed successfully
I (402) os_wrapper_esp: GPIO [16] configuring as Interrupt
I (407) gpio: GPIO[16]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:1
I (415) os_wrapper_esp: GPIO [17] configuring as Interrupt
I (420) gpio: GPIO[17]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:1
I (394) main_task: Started on CPU0
I (432) main_task: Calling app_main()
I (442) WIFI: WiFi init config: nvs_enable=0, static_rx_buf=10, dynamic_rx_buf=32
I (445) transport: Attempt connection with slave: retry[0]
I (448) transport: Reset slave using GPIO[45]
I (452) os_wrapper_esp: GPIO [45] configured
I (456) gpio: GPIO[45]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (1642) transport: Received INIT event from ESP32 peripheral
I (1642) transport: EVENT: 12
I (1642) transport: EVENT: 11
I (1642) transport: capabilities: 0xa0
I (1645) transport: Features supported are:
I (1649) transport: EVENT: 13
I (1652) stats: ESP peripheral capabilities: 0x1
I (1656) stats: ***** Host Raw throughput Testing (report per 5 sec) *****

I (1663) transport: ESP board type is : 13

I (1667) transport: Base transport is set-up

I (1671) transport: Slave chip Id[12]
I (1675) hci_stub_drv: Host BT Support: Disabled
I (1679) spi: Received INIT event
I (6663) stats: 0-5 sec Tx:47 Rx:0 Kbps
W (7565) rpc_core: Timeout waiting for Resp for Req[0x116]
E (7565) rpc_core: Response not received for [0x116]
E (7565) WIFI: esp_wifi_init failed: 0xffffffff
ESP_ERROR_CHECK failed: esp_err_t 0xffffffff (ESP_FAIL) at 0x4001de86
--- 0x4001de86: wifi_cmd_initialize_wifi at D:/vscodeidf/iperf4/iperf/managed_components/esp-qa__wifi-cmd/src/wifi_init.c:191 (discriminator 1)

file: "./managed_components/esp-qa__wifi-cmd/src/wifi_init.c" line 191
func: wifi_cmd_initialize_wifi
expression: wifi_cmd_init_wifi_and_handlers(s_wifi_init_cfg)

abort() was called at PC 0x4ff08ab3 on core 0
--- 0x4ff08ab3: _esp_error_check_failed at E:/program/IDF_5.4.1/frameworks/esp-idf-v5.4.1/components/esp_system/esp_err.c:49

Core 0 register dump:
MEPC : 0x4ff00d44 RA : 0x4ff08abe SP : 0x4ff25420 GP : 0x4ff16180
--- 0x4ff00d44: panic_abort at E:/program/IDF_5.4.1/frameworks/esp-idf-v5.4.1/components/esp_system/panic.c:468
--- 0x4ff08abe: __ubsan_include at E:/program/IDF_5.4.1/frameworks/esp-idf-v5.4.1/components/esp_system/ubsan.c:311

TP : 0x4ff25680 T0 : 0x37363534 T1 : 0x7271706f T2 : 0x33323130
S0/FP : 0x4ff2545c S1 : 0x4ff2545c A0 : 0x4ff2545c A1 : 0x4ff2543e
A2 : 0x00000000 A3 : 0x4ff1a000 A4 : 0x00000001 A5 : 0x4ff1a000
A6 : 0x00000000 A7 : 0x76757473 S2 : 0x4ff25440 S3 : 0x00000000
S4 : 0x00000000 S5 : 0x00000000 S6 : 0x00000000 S7 : 0x00000000
S8 : 0x00000000 S9 : 0x00000000 S10 : 0x00000000 S11 : 0x00000000
T3 : 0x6e6d6c6b T4 : 0x6a696867 T5 : 0x66656463 T6 : 0x62613938
MSTATUS : 0x00011880 MTVEC : 0x4ff00003 MCAUSE : 0x00000002 MTVAL : 0x00000000
--- 0x4ff00003: _vector_table at ??:?

MHARTID : 0x00000000

Stack memory:
4ff25420: 0x00000000 0x00000000 0x4ff2545c 0x4ff1471e 0x00000000 0x00000000 0x00000000 0x00000030
--- 0x4ff1471e: __assert_func at E:/program/IDF_5.4.1/frameworks/esp-idf-v5.4.1/components/newlib/assert.c:33

4ff25440: 0x30666634 0x33626138 0x4ff25500 0x4ff170d8 0x4ff25440 0x4ff170f4 0x4ff2543c 0x726f6261
4ff25460: 0x20292874 0x20736177 0x6c6c6163 0x61206465 0x43502074 0x34783020 0x38306666 0x20336261
4ff25480: 0x63206e6f 0x2065726f 0x00000030 0x40090000 0x4ff1a000 0x4ff1a000 0x4ff25598 0x4ff08ab6
--- 0x4ff08ab6: esp_system_abort at E:/program/IDF_5.4.1/frameworks/esp-idf-v5.4.1/components/esp_system/port/esp_system_chip.c:86

4ff254a0: 0x4ff1a000 0x4ff1a000 0x4ff25598 0x4001de8a 0x00000003 0x00000000 0x4ff18d08 0x00000000
--- 0x4001de8a: app_wifi_operations at D:/vscodeidf/iperf4/iperf/managed_components/esp-qa__wifi-cmd/src/wifi_init.c:210

4ff254c0: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
4ff254e0: 0x00000000 0x00000000 0x0000000a 0x00000020 0x00000001 0x00000000 0x00000020 0x00000000
4ff25500: 0x00000005 0x00000000 0x00000000 0x00000001 0x00000001 0x00000000 0x00000001 0x00000000
4ff25520: 0x00000006 0x00000000 0x000002f0 0x00000020 0x000000a1 0x00000000 0x00000001 0x00000007
4ff25540: 0x00000003 0xa5a5a500 0x1f2f3f4f 0xa5a5a5a5 0x00000000 0x40064000 0x40072000 0x4001cd80
--- 0x40064000: esp_netif_lwip_ipc_call at E:/program/IDF_5.4.1/frameworks/esp-idf-v5.4.1/components/esp_netif/lwip/esp_netif_lwip.c:231
--- (inlined by) esp_netif_dhcps_get_clients_by_mac at E:/program/IDF_5.4.1/frameworks/esp-idf-v5.4.1/components/esp_netif/lwip/esp_netif_lwip.c:1967
--- 0x4001cd80: app_main at D:/vscodeidf/iperf4/iperf/main/iperf_example_main.c:105

4ff25560: 0xa5a5a5a5 0x00000000 0x00000000 0x00000000 0x00000000 0x00000001 0x4ff256a8 0x4ff0c176
--- 0x4ff0c176: xTaskPriorityDisinherit at E:/program/IDF_5.4.1/frameworks/esp-idf-v5.4.1/components/freertos/FreeRTOS-Kernel/tasks.c:5218

4ff25580: 0x4ff1bbec 0x00000000 0x4ff1bba0 0x4ff0c376 0x00000000 0x00000001 0x00000000 0x00000000
--- 0x4ff0c376: pvTaskIncrementMutexHeldCount at E:/program/IDF_5.4.1/frameworks/esp-idf-v5.4.1/components/freertos/FreeRTOS-Kernel/tasks.c:5718

4ff255a0: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
4ff255c0: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
4ff255e0: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
4ff25600: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
4ff25620: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000001 0x00000000 0xa1a2a3a4 0x00000000
4ff25640: 0x40071fec 0x00000189 0x40072000 0x4006427a 0x00000000 0x00000000 0x00000000 0x00000000
--- 0x4006427a: main_task at E:/program/IDF_5.4.1/frameworks/esp-idf-v5.4.1/components/freertos/app_startup.c:209 (discriminator 13)

4ff25660: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0xa5a5a5a5 0xa5a5a5a5 0xa5a5a5a5
4ff25680: 0x00000000 0x4ff246a4 0x4ff246a4 0x00000000 0x00000000 0x00000000 0xa5a5a5a5 0xa5a5a5a5
4ff256a0: 0xa5a5a5a5 0x00000160 0x4ff25300 0x00001c04 0x4ff17d00 0x4ff17d00 0x4ff256a8 0x4ff17cf8
4ff256c0: 0x00000018 0x4ff29d4c 0x4ff29d4c 0x4ff256a8 0x00000000 0x00000001 0x4ff246a4 0x6e69616d
4ff256e0: 0x00000000 0x00000000 0x00000000 0x00000000 0x4ff256a0 0x00000001 0x00000000 0x00000000
4ff25700: 0x00000000 0x00000000 0x4ff1ad70 0x4ff1add8 0x4ff1ae40 0x00000000 0x00000000 0x00000001
4ff25720: 0x00000000 0x00000000 0x00000000 0x40006d5e 0x00000000 0x00000000 0x00000000 0x00000000
--- 0x40006d5e: esp_cleanup_r at E:/program/IDF_5.4.1/frameworks/esp-idf-v5.4.1/components/newlib/newlib_init.c:43

4ff25740: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
4ff25760: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
4ff25780: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
4ff257a0: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
4ff257c0: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
4ff257e0: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0xa3a1fc72
4ff25800: 0x2fcdbc32 0x4ff256a0 0x00000600 0xa5a5a5a5 0xa5a5a5a5 0xa5a5a5a5 0xa5a5a5a5 0xa5a5a5a5

ESP32C6
I (400) fg_mcu_slave: ESP-Hosted-MCU Slave FW version :: 2.0.4
I (409) fg_mcu_slave: Transport used :: SPI only
I (417) fg_mcu_slave: *********************************************************************
I (425) fg_mcu_slave: Supported features are:
I (429) fg_mcu_slave: - WLAN over SPI
I (432) fg_mcu_slave: capabilities: 0xa0
I (436) fg_mcu_slave: Supported extended features are:
I (440) fg_mcu_slave: extended capabilities: 0x0
I (457) SPI_DRIVER: Using SPI interface
I (458) gpio: GPIO[3]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (458) gpio: GPIO[4]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (467) SPI_DRIVER: SPI Ctrl:1 mode: 3, Freq:ConfigAtHost
GPIOs: MOSI: 7, MISO: 2, CS: 10, CLK: 6 HS: 3 DR: 4

I (476) SPI_DRIVER: Hosted SPI queue size: Tx:20 Rx:20
I (481) gpio: GPIO[10]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (490) gpio: GPIO[10]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (500) stats:

***** Slave: Raw Throughput testing (Report per 10 sec)*****

I (505) SPI_DRIVER: Slave chip Id[12]
I (509) fg_mcu_slave: Initial set up done
I (512) slave_ctrl: event ESPInit
mem_dump free:335640 min-free:335616 lfb-dma:303104 lfb-def:303104 lfb-8bit:303104
--- Error: ClearCommError failed (PermissionError(13, '璁惧涓嶈瘑鍒鍛戒护銆?', None, 22))
--- Waiting for the device to reconnect
I (474) SPI_DRIVER: Using SPI interface
I (474) gpio: GPIO[3]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (475) gpio: GPIO[4]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (483) SPI_DRIVER: SPI Ctrl:1 mode: 3, Freq:ConfigAtHost
GPIOs: MOSI: 7, MISO: 2, CS: 10, CLK: 6 HS: 3 DR: 4

I (493) SPI_DRIVER: Hosted SPI queue size: Tx:20 Rx:20
I (498) gpio: GPIO[10]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (506) gpio: GPIO[10]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (517) stats:

***** Slave: Raw Throughput testing (Report per 10 sec)*****

I (522) SPI_DRIVER: Slave chip Id[12]
I (525) fg_mcu_slave: Initial set up done
I (529) slave_ctrl: event ESPInit
mem_dump free:335640 min-free:335616 lfb-dma:303104 lfb-def:303104 lfb-8bit:303104

ELF file SHA256: cd9899512

[mantriyogesh]

It seems that pull-up resistors are not needed in SPI FD mode

Yes thats right. You can use the jumper wires for Full-Duplex SPI with <=10cm.
In fact, the SPI pins need not be strict to specific GPIOs, as they can be even routed through GPIO matrix as well, on both sides.

Would it be possible to show up the connections you had used in connections: both (1) in camera picture and (2) the hardware connections used.

[mantriyogesh]

Let me cross-check if same thing works at my place or not and get back to this..

[Big-mouth-c]

Hello.
I made the configurations according to the jumper - connection examples for ESP32 - P4 and ESP32 - C6 in the ESP - Hosted SPI FD (Full Duplex) instructions.
The host and slave sides have been configured and programmed according to the SPI FD (Full Duplex) instructions, with no code modifications made.

[Big-mouth-c]

ESP32P4 reset out 53
The RESET OUT of ESP32 - P4 has been modified to interface 53. As for the development board I have, interface 54 is not left unused and is used for other purposes.

[Big-mouth-c]

I found the problem. There is an issue with the output voltage of GPIO14 and GPIO15. The measured voltage is only 1.3V. After switching these two pins to pins 20 and 21, the communication works normally. I still don't know if it's a problem with the board itself or something else. Looking at the development board schematic, GPIO4 - GPIO15 all belong to the VDDPST_1 power domain, and GPIO16 - 23 belong to the VDDPST_2 power domain. The schematic clearly indicates that the IO voltage of VDDPST_2 is 3.3V. And VDDPST_1 is the ESP_LDO_VO4 with adjustable output voltage.

[SohKamYung-Espressif]

Hello @Big-mouth-c ,

Thank you for discovering and solving the problem with the GPIO pins on the P4. You are right that the suggested SPI GPIO pins are in two different P4 power domains. We will update the documentation so the P4 SPI GPIOs pins use only one power domain, and add information on the P4 power domains.