Closed beriberikix closed 1 year ago
Hi Jonathan:)
If you want to run the Thread BR on ESP32-C6 single SoC, please use the ot_br
example from the ESP-IDF repo:
https://github.com/espressif/esp-idf/tree/master/examples/openthread/ot_br
You can build and run the ot_br
example without any change, just set-target to esp32c6.
The example in this esp-thread-br
repo is designed for the two SoCs solution (ESP BR board), which builds in the RCP image together, so the RCP image could be downloaded to the ESP32-H2 (15.4) SoC from host SoC. The compile error indicates you haven't built the ot_rcp example in ESP-IDF, so it can't find the ot_rcp image.
Thank you Shu, that worked!
@beriberikix Goog to know!
Currently, we still recommend to use the two SoCs BR solution for production. Since there is only one RF path in ESP32-C6, which means Wi-Fi and Thread can't receive simultaneously, it will cause high packet loss rate comparing to the two SoCs solution.
I saw that, understood. The challenge we have is that the H2 is not available anywhere yet :)
Can this project work with other OpenThread compatible RCP radios from other vendors?
The H2 will be public available soon:)
Yes, the ESP Thread BR could work with other RCP. While you can also use C6 as the RCP, that is:
Connect the two boards via UART, and run the two exampls as is.
It's a shame that Wi-Fi and Thread can't receive simultaneously on the ESP32-C6. I thought that having a single microcontroller with Wi-Fi 6 as a thread border router would be a great idea. Could the packet loss be solved later on with changes in the firmware/software or is it a limitation with the design of the C6?
This is usually the case in multi-radio designs, due to the physical limitations of having to share an RF path. This is very common among BLE + 802.15.4 MCUs, for example. Time slicing between the two modems becomes the main strategy. Usually software can improve to switch between the radios to a point it is "good enough" for a specific application, but it'll never be as performant as a two radio solution.
I'm curious if the math has been done to figure out what's needed for Thread and/or Matter (typical use case) and if we can hope for a good enough solution!
Hello! I recently got some of the new ESP32-C6 devkits and thought I try this out on one of them since I saw support was recently added. I'm using the VS Code extension, which also added support for the C6. However, I'm unable to build the example on any of my machines (Windows, macOS and Linux.)
Each error is slightly different but since I'm currently on my mac, I'll describe the error and my setup.
When I set up the workspace configuration and hit build, I get:
I did not change any of the default configurations that are part of the example.
Any ideas what I'm doing wrong or how to fix the build? Happy to also build on the other host OSes if that's helpful.