commit 60f0e13bef2ce8fa27f9ba4651160c1d471f6300
author Junior Martinez <67972863+jmartinez-silabs@users.noreply.github.com> Wed May 17 10:10:39 2023 -0400
committer GitHub <noreply@github.com> Wed May 17 10:10:39 2023 -0400
tree 356640ed21409f99add36d2892fc152b5aa539de
parent 64bf86774fda0e2a5dcd6fdafb701d5cdc509aac

vTaskPrioritySet(NULL, 0) doesn't always fix the issue it was trying to address and could even prevent the current task to be run again. Use a vTaskDelay of 500 ms to address the missing response issue and also make sure the task can execute the device reset. (#26585)

src/platform/silabs/efr32/ConfigurationManagerImpl.cpp

diff --git a/src/platform/silabs/efr32/ConfigurationManagerImpl.cpp b/src/platform/silabs/efr32/ConfigurationManagerImpl.cpp
index 886a304..fc87f43 100644
--- a/src/platform/silabs/efr32/ConfigurationManagerImpl.cpp
+++ b/src/platform/silabs/efr32/ConfigurationManagerImpl.cpp
@@ -295,9 +295,8 @@
 
     // When called from an RPC, the following reset occurs before the RPC can respond,
     // which breaks tests (because it looks like the RPC hasn't successfully completed).
-    // One way to fix this is to reduce the priority of this task, to allow logging to
-    // complete before the reset occurs.
-    vTaskPrioritySet(NULL, 0);
+    // Block the task for 500 ms before the reset occurs to allow RPC response to be sent
+    vTaskDelay(pdMS_TO_TICKS(500));
 
     NVIC_SystemReset();
 }