What do the reset reasons and counts mean for Verv devices using Amazon FreeRTOS firmware?
In the new Amazon FreeRTOS firmware (devices with shadow schema 0.3 and above), you can access detailed debugging information related to device resets. This information helps engineers understand why a device has rebooted or reset, and how often it has happened.
Note: These counts track resets over the device’s runtime since the last major reset, not since manufacturing.
The ESP soft reset reason shows the last recorded soft reset cause along with the total count for each type, provided in a mini JSON payload for easy debugging.
No. |
Reason |
Description |
1 |
SOFT_RST_NONE |
No reset |
2 |
SOFT_RST_AWS |
Reset performed through shadow |
3 |
SOFT_RST_GATTS |
Reset performed through Bluetooth |
4 |
SOFT_RST_BLE_DISCON |
Bluetooth disconnected |
5 |
SOFT_RST_BLE_FLEET_TASK_FAIL |
Fleet provisioning task failed to execute |
5 |
SOFT_RST_BLE_FLEET_TASK_RESTART |
Reset performed after fleet provisioning |
7 |
SOFT_RST_ESP_OTA_UPGRADE |
Reset performed after successful OTA upgrade to ESP32 |
8 |
SOFT_RST_STM_NO_RSP_EXC_FIRMWARE |
Reset performed because of no communication with STM32 (only in three phase and currently disabled) |
9 |
SOFT_RST_S3_DWN_FAIL_STM |
STM32 binary file downloading failed |
10 |
SOFT_RST_SMPLRATE_CHANGED |
Sampling rate has changed (three phase only) |
11 |
SOFT_RST_STM_DWN_CPLT |
STM32 binary file download was successful |
12 |
SOFT_RST_ADC_CALIB_TIMEOUT |
ADC calibration performed through shadow |
13 |
SOFT_RST_S3_DWN_CPLT |
ESP32 binary file downloaded |
14 |
SOFT_RST_S3_DWN_FAIL |
Failed to download ESP32 binary file from S3 |
15 |
SOFT_RST_S3_DWN_TASK_FAIL |
ESP32 binary file downloader task failed to execute |
16 |
SOFT_RST_SHADOW_TASK_FAIL |
Shadow thread failed to execute |
17 |
SOFT_RST_WIFI_SCAN_TIMEOUT |
WiFi scan timeout |
18 |
SOFT_RST_UPL_DWN_BUCKET_CHANGED |
Upload or download bucket has been changed |
19 |
SOFT_RST_BLE_TIMEOUT |
Bluetooth state timeout (max 10 mins) |
20 |
SOFT_RST_BLE_FLEET_PROV_DONE |
Fleet provisioning credentials have been successfully passed on to the device via Bluetooth app |
21 |
SOFT_RST_BLE_FLEET_PROV_TASK_FAIL |
Bluetooth task failed |
22 |
SOFT_RST_BLE_FLEET_PROV_FAIL |
Failed to get all of fleet provisioning credentials via Bluetooth |
23 |
SOFT_RST_USER_BUTTON |
User button/touch sensor soft reset |
24 |
SOFT_RST_BLE_MODE |
Device switching to Bluetooth mode |
25 |
SOFT_RST_MIDNIGHT |
Midnight reset |