Combining S3+C5, or possibly P4+C5

[savenlid]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate.
• Described the feature in detail and justified the reason for the request.
• Provided specific use cases and examples.

Feature description

ESP32-S3 + ESP32-C5, a more complete descripton for this user case

Use cases

We started with the S3 but today we need 5Ghz wifi ( market requierments )
The quickest solution is to hook up the C5 and let it do the wifi ( disable S3 radio )
Could you make some mentioning of this specific combo considering its 2 pcs esp chips involved.
We need the USB of the S3 and the 5Ghz wifi of the C4
Another option would be P4+C5
Or another competitor chip for example STM32H743 + C5
But the low cost of the esp keep all of us trying to use the esp32 chips to solve everything.

Alternatives

P4+C5
STM32+C5

Additional context

No response

[SohKamYung-Espressif]

Hi, @savenlid ,

Please take a look at ESP-Hosted-MCU https://github.com/espressif/esp-hosted-mcu/ . This is a version of ESP-Hosted that should cater to your requirements.

For the S3 + C5 combination, see https://github.com/espressif/esp-hosted-mcu/blob/main/docs/troubleshooting.md#1-esp-host-to-evaluate-already-has-native-wi-fi , which contains instructions on how to disable the Native Wi-Fi on the S3 so it will use ESP-Hosted to communicate with the C5 co-processor.

For P4 as a host, you can check https://github.com/espressif/esp-hosted-mcu/blob/main/docs/esp32_p4_function_ev_board.md , which contains instructions for the P4 + C6 combination, but can be changed to the C5.

A question: which transport do you plan to use? SPI or SDIO?

[savenlid]

Thanks for helping me.

I started reading the links you gave.

Regarding SDO versus SPI i am agnostic.
But when i tried the NG case with a C5 and RPI5, only SPI was supported.
So I assumed only SPI is an option with the C5.

I am also trying to get my hands on P4-eval kit and some P4 processors to try this out.

[savenlid]

Hi

Is this expected ?
I guess I follow what is written on web-page ?

this is the slave, menuconfig
target was set as esp32-c5

[SohKamYung-Espressif]

Is this expected ?
I guess I follow what is written on web-page ?

Yes, please use the GPIOs listed on the web page.

The menuconfig values are for a C5 test board and should be updated.

Thank you for bringing it to my attention.

[mantriyogesh]

But when i tried the NG case with a C5 and RPI5, only SPI was supported

This is correct. ESP32-C5 eco1 can work with SPI.
From ESP32-C5 eco2, you can expect SDIO, maybe May end. Once IDF supports C5 SDIO, we can easily support on ESP-Hosted.

[savenlid]

Can I assume this to be the same port ?

I want to use port spi-3 for my DM9051 eth-mac, currently I have that one on spi-2, need to move to spi3.
I hope that will work.

The slave/co-processor dont drive the clock does it ?
Did not find this in menuconfig.

[SohKamYung-Espressif]

Can I assume this to be the same port ?

Yes. The default config is to use SPI2. No need to change "SPI controller to use".

The slave/co-processor dont drive the clock does it ?

No. The SPI clock is driven by the SPI master.

"Set the SPI clock frequency" refers to setting the SPI clock frequency on the SPI Master. Start with a low CLK frequency (10 MHz or lower), especially if you are connecting the master and co-processor using wires. High frequency CLKs are only stable if you use a PCB for the system.

Make sure that both the SPI master and slave are using the same SPI Mode (default is Mode 3).

[savenlid]

After flashing the C5 as a co-processor it keeps repeating the last lines of my text below.
"mem_dump free:108996 min-free:108920 lfb-dma:90112 lfb-def:90112 lfb-8bit:90112"
Is it ok ?
FYI: Nothing is connected to any pins yet, maybe its upset about that ?
Or maybe its normal status info about the memory.

spressif\frameworks\esp-idf-master-3\tools\idf.py'"...
--- Warning: GDB cannot open serial ports accessed as COMx
--- Using \.\COM5 instead...
--- esp-idf-monitor 1.6.2 on \.\COM5 115200
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H
ESP-ROM:esp32c5-eco1-20240726
Build:Jul 26 2024
rst:0x1 (POWERON),boot:0x18 (SPI_FAST_FLASH_BOOT)
SPI mode:DIO, clock div:1
load:0x40855ab0,len:0x1708
load:0x4084c7a0,len:0xd90
--- 0x4084c7a0: esp_bootloader_get_description at C:/Espressif/frameworks/esp-idf-master-3/components/esp_bootloader_format/esp_bootloader_desc.c:39 (discriminator 1)

load:0x4084e9a0,len:0x3680
--- 0x4084e9a0: esp_flash_encryption_enabled at C:/Espressif/frameworks/esp-idf-master-3/components/bootloader_support/src/flash_encrypt.c:86

entry 0x4084c7aa
--- 0x4084c7aa: call_start_cpu0 at C:/Espressif/frameworks/esp-idf-master-3/components/bootloader/subproject/main/bootloader_start.c:25

I (23) boot: ESP-IDF v5.5-dev-698-g030c9957db 2nd stage bootloader
I (23) boot: compile time Apr 30 2025 12:44:00
I (24) boot: chip revision: v0.1
I (25) boot: efuse block revision: v0.1
I (28) boot.esp32c5: SPI Speed : 80MHz
I (32) boot.esp32c5: SPI Mode : DIO
I (36) boot.esp32c5: SPI Flash Size : 4MB
I (40) boot: Enabling RNG early entropy source...
I (44) boot: Partition Table:
I (47) boot: ## Label Usage Type ST Offset Length
I (53) boot: 0 nvs WiFi data 01 02 00009000 00004000
I (60) boot: 1 otadata OTA data 01 00 0000d000 00002000
I (66) boot: 2 phy_init RF data 01 01 0000f000 00001000
I (73) boot: 3 ota_0 OTA app 00 10 00010000 00180000
I (79) boot: 4 ota_1 OTA app 00 11 00190000 00180000
I (86) boot: End of partition table
I (89) esp_image: segment 0: paddr=00010020 vaddr=420c0020 size=2ad0ch (175372) map
I (127) esp_image: segment 1: paddr=0003ad34 vaddr=40800000 size=052e4h ( 21220) load
I (131) esp_image: segment 2: paddr=00040020 vaddr=42000020 size=ba104h (762116) map
I (260) esp_image: segment 3: paddr=000fa12c vaddr=408052e4 size=13870h ( 79984) load
I (276) esp_image: segment 4: paddr=0010d9a4 vaddr=40818b80 size=03f30h ( 16176) load
I (284) boot: Loaded app from partition at offset 0x10000
I (284) boot: Disabling RNG early entropy source...
I (294) cpu_start: Unicore app
W (302) clk: esp_perip_clk_init() has not been implemented yet
I (308) cpu_start: Pro cpu start user code
I (308) cpu_start: cpu freq: 240000000 Hz
I (308) app_init: Application information:
I (308) app_init: Project name: network_adapter
I (313) app_init: App version: v5.5-dev-698-g030c9957db
I (318) app_init: Compile time: Apr 30 2025 12:43:05
I (323) app_init: ELF file SHA256: 56d72526d...
I (327) app_init: ESP-IDF: v5.5-dev-698-g030c9957db
I (333) efuse_init: Min chip rev: v0.0
I (337) efuse_init: Max chip rev: v0.99
I (341) efuse_init: Chip rev: v0.1
I (344) heap_init: Initializing. RAM available for dynamic allocation:
I (351) heap_init: At 40822D00 len 00039CA0 (231 KiB): RAM
I (356) heap_init: At 4085C9A0 len 00002B60 (10 KiB): RAM
I (361) heap_init: At 50000000 len 00003FE8 (15 KiB): RTCRAM
I (367) spi_flash: detected chip: generic
I (370) spi_flash: flash io: dio
W (373) spi_flash: Detected size(8192k) larger than the size in the binary image header(4096k). Using the size in the binary image header.
I (385) sleep_gpio: Configure to isolate all GPIO pins in sleep state
I (392) sleep_gpio: Enable automatic switching of GPIO sleep configuration
I (398) coexist: coex firmware version: 49a8cdc
I (417) coexist: coexist rom version 78e5c6e42
I (417) main_task: Started on CPU0
I (417) main_task: Calling app_main()
I (417) fg_mcu_slave: *********************************************************************
I (424) fg_mcu_slave: ESP-Hosted-MCU Slave FW version :: 2.0.0
I (433) fg_mcu_slave: Transport used :: SPI only
I (441) fg_mcu_slave: *********************************************************************
I (449) fg_mcu_slave: Supported features are:
I (453) fg_mcu_slave: - WLAN over SPI
I (456) h_bt: - BT/BLE
I (458) h_bt: - HCI Over SPI
I (461) h_bt: - BLE only
I (464) fg_mcu_slave: capabilities: 0xe8
I (467) fg_mcu_slave: Supported extended features are:
I (472) h_bt: - BT/BLE (extended)
I (475) fg_mcu_slave: extended capabilities: 0x0
I (484) h_bt: ESP Bluetooth MAC addr: 60:55:f9:fb:cf:96
I (485) BLE_INIT: Using main XTAL as clock source
I (491) BLE_INIT: ble controller commit:[4f138b0]
W (493) BLE_INIT: BLE modem sleep is enabled
I (497) BLE_INIT: Bluetooth MAC: 60:55:f9:fb:cf:96
I (502) phy_init: phy_version 102,3b01d78a,Nov 27 2024,17:24:11
I (1405) phy: libbtbb version: 351e560, Nov 27 2024, 17:24:22
I (1406) SPI_DRIVER: Using SPI interface
I (1406) gpio: GPIO[3]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (1411) gpio: GPIO[4]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (1420) SPI_DRIVER: SPI Ctrl:1 mode: 3, Freq:ConfigAtHost
GPIOs: MOSI: 7, MISO: 2, CS: 10, CLK: 6 HS: 3 DR: 4

I (1430) SPI_DRIVER: Hosted SPI queue size: Tx:20 Rx:20
I (1435) gpio: GPIO[10]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (1443) gpio: GPIO[10]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
I (1453) SPI_DRIVER: Slave chip Id[12]
I (1455) fg_mcu_slave: Initial set up done
I (1459) slave_ctrl: event ESPInit
mem_dump free:108996 min-free:108920 lfb-dma:90112 lfb-def:90112 lfb-8bit:90112
mem_dump free:108996 min-free:108920 lfb-dma:90112 lfb-def:90112 lfb-8bit:90112
mem_dump free:108996 min-free:108920 lfb-dma:90112 lfb-def:90112 lfb-8bit:90112
mem_dump free:108996 min-free:108920 lfb-dma:90112 lfb-def:90112 lfb-8bit:90112

[savenlid]

I did follow instrctions for setting up the esp32-s3 as a host. ( i think )
But I cannot find esp-hosted in menuconfig

I suspect the esp32-s3 is not an option for esp-hosted ?

[SohKamYung-Espressif]

I suspect the esp32-s3 is not an option for esp-hosted

Yes, you are correct. The default host configuration for ESP-Hosted is for ESP32-P4 and ESP32-H2.

Add esp32s3 as a target for esp_wifi_remote and esp_hosted.

[SohKamYung-Espressif]

After flashing the C5 as a co-processor it keeps repeating the last lines of my text below.
"mem_dump free:108996 min-free:108920 lfb-dma:90112 lfb-def:90112 lfb-8bit:90112"
Is it ok ?

Yes, this is fine. It is periodically printed by the slave app_main.c https://github.com/espressif/esp-hosted-mcu/blob/e6489fbbfe3b35e837b34e97cc34912c59e210a6/slave/main/app_main.c#L941

[mantriyogesh]

#598 (comment)

The P4 and H2, by default, do not have Wi-Fi with them. that is the reason ESP-Hosted is defaulted for them.

ESP32-S3 by default has Wi-Fi. Following link includes a table and legend below, shows which all chipsets are supported:
https://github.com/espressif/esp-hosted-mcu?tab=readme-ov-file#6-decide-the-communication-bus-in-between-host-and-slave

To evaluate ESP32-S3 as ESP-Hosted Slave, you might need to disable default Wi-Fi using https://github.com/espressif/esp-hosted-mcu/blob/main/docs/troubleshooting.md#1-esp-host-to-evaluate-already-has-native-wi-fi

[savenlid]

I managed to get it working in iperf.
Somethings are confusing when reset is described as active high, you get very insecure what else can be strange.
However after manually adding esp32s3 as a host in en yml file I got it working.
I never tested the iperf functionallity tough.
I wanted a better example where I acutally could run trafffic in the s3 via the c5.
I thought i do the example/protocols/http_server/simple.
I made sure I had a screaming fresh copy from github of espressif.
git clone --recursive https://github.com/espressif/esp-idf.git
I installed all chips.
I updated it.
everything was fine.
I did add the "modules"
idf.py add-dependency "espressif/esp_wifi_remote"
idf.py add-dependency "espressif/esp_hosted"
I had to manually add esp32c5 as an option in slave yml file to be able to choose it in menuconfig for wifi-remote.
(this always feels very nervous, as I do something forbidden or at least its sure to to fail)

setting the target gives a less than reassuring output:
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: esp_stubs
NOTICE: Skipping optional dependency: esp_stubs
NOTICE: Skipping optional dependency: esp_stubs
NOTICE: Using component placed at /home/pi/esp250305/esp-idf/examples/common_components/protocol_examples_common for dependency "protocol_examples_common", specified in /home/pi/esp250305/esp-idf/examples/protocols/http_server/simple/main/idf_component.yml
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: esp_stubs

However, equal to the iperf example it seems to work ok.
But both examples are unhappy with GPIO4 as IRQ, it seems to have been spoken for by someone else

I (389) os_wrapper_esp: GPIO [17] configuring as Interrupt
I (389) spi: No element in any queue found
I (399) os_wrapper_esp: GPIO [4] configuring as Interrupt
E (399) gpio: gpio_install_isr_service(526): GPIO isr service already installed

The ISR I can suspect to be only 1 single ISR for all GPIO, so maybe its what it says.
A bit unclear.

Success

now a question to you 2 gentlemens.

My plan is to convert our current system S3 -> S3+C5 (for the sake of 5Ghz wifi capability)
I also have ETH (DM9051) works today.
RNDIS over USB (works in your examples )
I2C-Master ( works today)

Will I succeed or am I a dead man walking ?

Will I get the DM9051 in on the SPI3 over the gpio-mux, or will it be possible to run both the C5 and DM9051 on SPI2-port using 2 chip-selects ?

Thank you.

[SohKamYung-Espressif]

Somethings are confusing when reset is described as active high, you get very insecure what else can be strange.

You are referring to this ESP-Hosted SPI setting in menuconfig: Reset GPIO Config (RESET: Active High)

You can check Symbol info ('?' key) for that setting which explains what it means:

Help:

"If Active High, High->Low->High will trigger reset (Low will trigger reset)                         
If Active Low, Low->High->Low will trigger reset (High will trigger reset)"

I had to manually add esp32c5 as an option in slave yml file to be able to choose it in menuconfig for wifi-remote.

I checked wifi-remote and you are right. esp32c5 is not currently a slave option (probably a temporary removal).

As a temporary measure, you can use an earlier version of wifi-remote that has the C5 as an option, like v0.8.5 https://components.espressif.com/components/espressif/esp_wifi_remote/versions/0.8.5?language=en

You can use it by running:

idf.py add-dependency "espressif/esp_wifi_remote^0.8.5" 

NOTICE: Skipping optional dependency: espressif/esp_hosted

Just a check: you are seeing this while using the S3 as the ESP-Hosted host? If yes, please check that you have disabled wifi related settings as mentioned in the link https://github.com/espressif/esp-hosted-mcu/blob/main/docs/troubleshooting.md#1-esp-host-to-evaluate-already-has-native-wi-fi

Can you provide the console output from your ESP-Hosted master (S3?) and slave (C5?) from boot-up onwards?

[savenlid]

Remark: as I wrote, its working, but with failure to register an GPIO4 as IRQ.

Yes I did disable all wifi in the host (S3 ).
Once I forgot and got a linking error.

Remark: you don't find this text confusing ?
"If Active High, High->Low->High will trigger reset (Low will trigger reset)
If Active Low, Low->High->Low will trigger reset (High will trigger reset)"

I think I slowly start to understand the wordings
Active in your world would be that the host is active ?
For all the rest of us , its that the signal is active = asserted.
Reset is asserted High ( and its not )

Question #1
Why do the ISR fail ?
Complete boot below as requested (Host S3, only, the one with the IRQ GPIO4 problem).
Let me know if the (slave C5 is still relevant).

pi@RPI16:~/esp250305/esp-idf/examples/protocols/http_server/simple $ idf.py moni
tor
Executing action: monitor
Serial port /dev/ttyUSB0
Connecting....
Detecting chip type... ESP32-S3
Running idf_monitor in directory /home/pi/esp250305/esp-idf/examples/protocols/h ttp_server/simple
Executing "/home/pi/.espressif/python_env/idf5.5_py3.11_env/bin/python /home/pi/ esp250305/esp-idf/tools/idf_monitor.py -p /dev/ttyUSB0 -b 115200 --toolchain-pre fix xtensa-esp32s3-elf- --target esp32s3 --revision 0 /home/pi/esp250305/esp-idf /examples/protocols/http_server/simple/build/simple.elf /home/pi/esp250305/esp-i df/examples/protocols/http_server/simple/build/bootloader/bootloader.elf -m '/ho me/pi/.espressif/python_env/idf5.5_py3.11_env/bin/python' '/home/pi/esp250305/es p-idf/tools/idf.py'"...
--- esp-idf-monitor 1.6.2 on /dev/ttyUSB0 115200
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce2820,len:0x15d8
load:0x403c8700,len:0xd24
--- 0x403c8700: _stext at ??:?

load:0x403cb700,len:0x2f84
entry 0x403c8924
--- 0x403c8924: call_start_cpu0 at /home/pi/esp250305/esp-idf/components/bootloa der/subproject/main/bootloader_start.c:25

I (24) boot: ESP-IDF v5.5-dev-3372-g38628f98b9-dirty 2nd stage bootloader
I (25) boot: compile time May 4 2025 02:09:55
I (25) boot: Multicore bootloader
I (27) boot: chip revision: v0.1
I (30) boot: efuse block revision: v1.2
I (33) boot.esp32s3: Boot SPI Speed : 80MHz
I (37) boot.esp32s3: SPI Mode : DIO
I (41) boot.esp32s3: SPI Flash Size : 2MB
I (45) boot: Enabling RNG early entropy source...
I (49) boot: Partition Table:
I (52) boot: ## Label Usage Type ST Offset Length
I (58) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (65) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (71) boot: 2 factory factory app 00 00 00010000 00100000
I (78) boot: End of partition table
I (81) esp_image: segment 0: paddr=00010020 vaddr=3c060020 size=260a4h (155812) map
I (116) esp_image: segment 1: paddr=000360cc vaddr=3fc95900 size=02d40h ( 11584) load
I (119) esp_image: segment 2: paddr=00038e14 vaddr=40374000 size=07204h ( 29188) load
I (126) esp_image: segment 3: paddr=00040020 vaddr=42000020 size=57af4h (359156) map
I (191) esp_image: segment 4: paddr=00097b1c vaddr=4037b204 size=0a690h ( 42640) load
I (200) esp_image: segment 5: paddr=000a21b4 vaddr=600fe000 size=0001ch ( 28) load
I (207) boot: Loaded app from partition at offset 0x10000
I (208) boot: Disabling RNG early entropy source...
I (218) cpu_start: Multicore app
I (227) cpu_start: Pro cpu start user code
I (227) cpu_start: cpu freq: 160000000 Hz
I (227) app_init: Application information:
I (227) app_init: Project name: simple
I (231) app_init: App version: v5.5-dev-3372-g38628f98b9-dirty
I (237) app_init: Compile time: May 4 2025 02:24:08
I (242) app_init: ELF file SHA256: dbcf0aca0...
I (246) app_init: ESP-IDF: v5.5-dev-3372-g38628f98b9-dirty
I (252) efuse_init: Min chip rev: v0.0
I (256) efuse_init: Max chip rev: v0.99
I (260) efuse_init: Chip rev: v0.1
I (264) heap_init: Initializing. RAM available for dynamic allocation:
I (270) heap_init: At 3FC99D40 len 0004F9D0 (318 KiB): RAM
I (275) heap_init: At 3FCE9710 len 00005724 (21 KiB): RAM
I (281) heap_init: At 3FCF0000 len 00008000 (32 KiB): DRAM
I (286) heap_init: At 600FE01C len 00001FCC (7 KiB): RTCRAM
I (292) spi_flash: detected chip: generic
I (295) spi_flash: flash io: dio
W (298) spi_flash: Detected size(8192k) larger than the size in the binary image header(2048k). Using the size in the binary image header.
I (310) host_init: ESP Hosted : Host chip_ip[9]
I (341) H_API: ESP-Hosted starting. Hosted_Tasks: prio:23, stack: 5120 RPC_task_ stack: 5120
spi_mempool_create free:358288 min-free:358288 lfb-def:311296 lfb-8bit:311296

I (345) spi_wrapper: Transport: SPI, Mode:3 Freq:40MHz TxQ:20 RxQ:20
GPIOs: MOSI:11 MISO:13 CLK:12 CS:10 HS:17 DR:4 SlaveReset:5
I (358) H_API: ** add_esp_wifi_remote_channels **
I (361) transport: Add ESP-Hosted channel IF[1]: S[0] Tx[0x4200c610] Rx[0x420176 a4]
--- 0x4200c610: transport_drv_sta_tx at /home/pi/esp250305/esp-idf/examples/prot ocols/http_server/simple/managed_components/espressif__esp_hosted/host/drivers/t ransport/transport_drv.c:216
--- 0x420176a4: esp_wifi_remote_channel_rx at /home/pi/esp250305/esp-idf/example s/protocols/http_server/simple/managed_components/espressif__esp_wifi_remote/esp _wifi_remote_net.c:19

I (369) transport: Add ESP-Hosted channel IF[2]: S[0] Tx[0x4200c58c] Rx[0x420176 a4]
--- 0x4200c58c: transport_drv_ap_tx at /home/pi/esp250305/esp-idf/examples/proto cols/http_server/simple/managed_components/espressif__esp_hosted/host/drivers/tr ansport/transport_drv.c:246
--- 0x420176a4: esp_wifi_remote_channel_rx at /home/pi/esp250305/esp-idf/example s/protocols/http_server/simple/managed_components/espressif__esp_wifi_remote/esp _wifi_remote_net.c:19

I (377) sleep_gpio: Configure to isolate all GPIO pins in sleep state
I (382) sleep_gpio: Enable automatic switching of GPIO sleep configuration
I (389) os_wrapper_esp: GPIO [17] configuring as Interrupt
I (389) spi: No element in any queue found
I (399) os_wrapper_esp: GPIO [4] configuring as Interrupt
E (399) gpio: gpio_install_isr_service(526): GPIO isr service already installed
I (399) main_task: Started on CPU0
I (419) main_task: Calling app_main()
I (429) example_connect: Start example_connect.
I (429) transport: Attempt connection with slave: retry[0]
I (429) transport: Reset slave using GPIO[5]
I (429) os_wrapper_esp: GPIO [5] configured
I (1989) transport: Received INIT event from ESP32 peripheral
I (1989) transport: EVENT: 12
I (1989) transport: EVENT: 11
I (1989) transport: capabilities: 0xe8
I (1999) transport: Features supported are:
I (1999) transport: - HCI over SPI
I (1999) transport: - BLE only
I (2009) transport: EVENT: 13
I (2009) transport: ESP board type is : 23

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

I (2019) transport: Slave chip Id[12]
I (2019) hci_stub_drv: Host BT Support: Disabled
I (2019) spi: Received INIT event
I (2889) example_connect: Connecting to NSP5G...
I (2929) H_API: esp_wifi_remote_connect
I (2949) example_connect: Waiting for IP(s)
I (12759) esp_wifi_remote: esp_wifi_internal_reg_rxcb: sta: 0x4202385c
--- 0x4202385c: wifi_sta_receive at /home/pi/esp250305/esp-idf/components/esp_wifi/src/wifi_netif.c:38

I (17039) esp_netif_handlers: example_netif_sta ip: 192.168.1.215, mask: 255.255.255.0, gw: 192.168.1.1
I (17039) example_connect: Got IPv4 event: Interface "example_netif_sta" address: 192.168.1.215
I (17039) example_common: Connected to example_netif_sta
I (17049) example_common: - IPv4 address: 192.168.1.215,
I (17049) example: Starting server on port: '80'
I (17059) example: Registering URI handlers

Question #2:
My plan is to convert our current system S3 -> S3+C5 (for the sake of 5Ghz wifi capability)
I also have ETH (DM9051) works today.
RNDIS over USB (works in your examples )
I2C-Master ( works today)

Will I succeed or am I a dead man walking ?

Will I get the DM9051 in on the SPI3 over the gpio-mux, or will it be possible to run both the C5 and DM9051 on SPI2-port using 2 chip-selects ?

Thank you