You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
I have searched the issue tracker for a similar issue and not found a similar issue.
IDF version.
4.4.2
Espressif SoC revision.
ESP32-S3
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
Development Kit.
ESP32-S3
Power Supply used.
USB
What is the expected behavior?
The vendor client model application flashed on ESP32-S3 should run without any error during communication with the vendor server model flashed on ESP32-H2.
What is the actual behavior?
The vendor client model running on ESP32-S3 application goes unresponsive after some successful message transactions.
Steps to reproduce.
Provision the vendor client model node (ESP32-S3).
Provision 3 vendor server model nodes (ESP32-H2).
Create a ESP-BLE-MESH of 4 nodes and start message passing between client and server nodes.
After a few successful transactions, the ESP32-S3 stops responding after printing "RPL is full".
Debug Logs.
BLE_MESH: RPL is full!
BLE_MESH: RPL is full!
BLE_MESH: RPL is full!
BLE_MESH: RPL is full!
BLE_MESH: RPL is full!
BLE_MESH: RPL is full!
BLE_MESH: RPL is full!
BLE_MESH: RPL is full!
BLE_MESH: RPL is full!
More Information.
The ESP32-H2 (Server node) uses ESP-IDF 5.1.2 while the ESP32-S3 (Client node) uses ESP-IDF 4.4.2.
Also, the value of CONFIG_BLE_MESH_CRPL is set to default value of 10 on the Client node side.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
ESP-BLE-MESH : RPL is full during message communication using vendor model
ESP-BLE-MESH : RPL is full during message communication using vendor model (IDFGH-13413)
Aug 7, 2024
Answers checklist.
IDF version.
4.4.2
Espressif SoC revision.
ESP32-S3
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
Development Kit.
ESP32-S3
Power Supply used.
USB
What is the expected behavior?
The vendor client model application flashed on ESP32-S3 should run without any error during communication with the vendor server model flashed on ESP32-H2.
What is the actual behavior?
The vendor client model running on ESP32-S3 application goes unresponsive after some successful message transactions.
Steps to reproduce.
Debug Logs.
More Information.
The ESP32-H2 (Server node) uses ESP-IDF 5.1.2 while the ESP32-S3 (Client node) uses ESP-IDF 4.4.2.
Also, the value of CONFIG_BLE_MESH_CRPL is set to default value of 10 on the Client node side.
The text was updated successfully, but these errors were encountered: