ESP32 Forum

I have flashed the `ot_rcp` from ESP-IDF onto the ESP32-H2. When I execute the connection setup command with the OTBR installed on Android, the `ot-daemon` encounters a 'wait for response timeout' error. The command used is:
When I directly connect the ESP32-H2 to my host PC via UART for testing, the Spinel packet responses are received abnormally from the ESP32-H2.

In contrast, the NXP-based `ot_rcp` firmware responds correctly with Spinel, but the ESP32-H2 `ot_rcp` does not.

I suspect the following reasons:

1. In `ot_rcp/sdkconfig`, `CONFIG_OPENTHREAD_RADIO_NATIVE=y` is set by default. I am curious if this setting is correct for using the Spinel protocol.
- `#CONFIG_OPENTHREAD_RADIO_SPINEL_UART is not set` is disabled.

2. Does the fact that `#CONFIG_OPENTHREAD_SPINEL_ONLY is not set` mean there should be no issues with communicating via Spinel, even if it is not configured?

I am curious about these two points. Additionally, if I attempt to change these two options and build, I encounter build errors that prevent binary extraction.

Additionally, if there are any settings that need to be changed to enable communication with OTBR using Spinel, please let me know.

I am also curious to know if the default `ot_rcp` settings for the ESP32-H2 are specifically configured for communication with ESP32 OTBR using Spinel, or if they are compatible with other OTBRs like those on Linux or Android.