mirror of
https://github.com/espressif/esp-idf.git
synced 2025-09-30 19:19:21 +00:00

Examples for zigbee are using custom license, which is not present on the SPDX license list. This was discussed on !16205 and a decision was made that the examples will be put on check-copyright's ignore list. SPDX has LicenseRef-[idstring] identifier for such cases, so let's try to use it. In this particular case the LicenseRef-Included is used to express that the full license text is included in the source file. Note that the LicenseRef-Included is not part of SPDX. It's just something I used. No change is needed on the check-copyright side. Signed-off-by: Frantisek Hrbata <frantisek.hrbata@espressif.com>
Supported Targets | ESP32-C6 | ESP32-H4 |
---|
Rcp Example
This test code shows how to configure Zigbee rcp (radio co-processor) device. Rcp doesn't function alone, it needs to work together with Zigbee gateway (see esp_zigbee_gateway example)
Hardware Required
- One development board with ESP32-H4 SoC acting as Zigbee rcp (loaded with esp_zigbee_rcp example)
- A USB cable for power supply and programming
- Choose ESP32 or ESP32-S3 as Zigbee gateway. The connection and setup refer to the Zigbee gateway example for setup details (see esp_zigbee_gateway example)
- TX, RX pin can be also configured by user in esp_zigbee_rcp.h
Configure the project
Before project configuration and build, make sure to set the correct chip target using idf.py --preview set-target TARGET
command.
Erase the NVRAM
Before flash it to the board, it is recommended to erase NVRAM if user doesn't want to keep the previous examples or other projects stored info using idf.py -p PORT erase-flash
Build and Flash
Build the project, flash it to the board by running idf.py -p <PORT> build flash
Rcp Functions
- After rcp starts up, it will send its own MAC ieee address and Zigbee stack version number to the Zigbee gateway and start working together with Zigbee gateway via UART communication
- For more log info please see Zigbee gateway side
Troubleshooting
For any technical queries, please open an issue on GitHub. We will get back to you soon