Separate out transport from ESP-HOSTED (EHM-108)

[renzenicolai]

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

We request that the transport (SDIO/SPI) layer will be provided as a separate component. This allows for adding custom interface types while keeping the WiFi/BLE part of ESP-HOSTED modification free.

In addition this would allow us to customize the SDIO layer to allow for graceful recovery in case the firmware on the radio does not respond as expected, such as automatically re-flashing the firmware using esp-serial-flasher.

Use cases

For our product we wish to use the radio coprocessor for more than just standard ESP-HOSTED. By separating out the transport layer we can use unmodified ESP-HOSTED component while customizing the transport layer for our custom application.

Alternatives

No response

Additional context

No response

[mantriyogesh]

Hello @renzenicolai ,

I’m currently working on restructuring the entire coprocessor repository, with the transport moved in as a submodule. It’s reassuring to know that identifying and reporting such needs confirms we’re heading in the right direction. This is, however, a time-consuming process, so I’d appreciate your patience while I get it into the right shape. Once I have an initial version ready, I’ll share it with you for review—your input on possible improvements would be very valuable.

[renzenicolai]

Thank you! I'm looking forward to evaluating the initial version once it is ready.