Example of ESP32-C5 as openthread border router using CONFIG_OPENTHREAD_RADIO_NATIVE=y (IDFGH-17163) (TZ-2349)

[louisvangeldrop]

Is your feature request related to a problem?

The esp32-c5 with the native rcp is an excellent device for running an OTBR in your home automation. An example sdkconfig.defaults.esp32c5 file would be a great help. It will prevent that many developers have to find out which parameters to adjust

Describe the solution you'd like.

sdkconfig.defaults.esp32c5

[zwx1995esp]

Hi Since there is only one antenna on C5, so WiFi and thread can not receive the packets at the same time. The single chip Thread BR solution has some limitation on performance. We still recommend the two chips solutions (https://github.com/espressif/esp-thread-br#esp-thread-border-router-board), with better performance.

[louisvangeldrop]

OK. Maybe eg an example with an esp32c5 for the wifi and a Supermini esp32c6 as rcp connected over the usb serial/jtag?

[tanyanquan]

Hi @louisvangeldrop , you can try running the basic border router example using esp32c5 + esp32c6.

A few things to note:

• RCP connected over USB is only supported for posix host now, so we recommend using UART instead
• The supermini C6 does not seem to have a RST pin, which will affect the RCP update functionality in the example - you can use an ESP32-C6 DevKitC (or ESP32-H2 DevKitM) instead which will have more comprehensive pinouts
• For the time being, you can create a sdkconfig.defaults.esp32c5 using the following KConfig options:

CONFIG_ESP_BR_BOARD_P4=y (these default options will work well for C5 as well)
CONFIG_ESP_CONSOLE_UART_DEFAULT=y if you are using the UART USB-C port on the ESP32-C5 DevKit)
CONFIG_ESP_BR_C6_TARGET=y

• You can reference this table (Connect an ESP32-H2 RCP to an ESP32-P4 using UART) which was previously written for P4 but also applies to your current use case (same pins used by default)
  • ESP32-P4 pin is now for ESP32-C5
  • ESP32-H2 pin is now for ESP32-C6