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
### Mechanism to report the error data after reboot
170
169
171
-
MbedOS initialization sequence should check if the reboot is caused by a fatal error and should report the same to the application using callback mechanism. The system may also print this to terminal if enabled.
170
+
MbedOS initialization sequence should check if the reboot is caused by a fatal error and should report the same to the application using callback mechanism.
172
171
173
172
MbedOS initialization sequence should be modified as shown in below diagram to report the crash report and invoke the callback.
174
173
@@ -193,7 +192,6 @@ Crash reporting implementation should provide enough parameters to control diffe
193
192
1. Configuration option to enable or disable error the entire feature
194
193
1. Configuration option to enable or disable auto-reboot when the system enters a fatal error scenario
195
194
1. Configuration option to limit the number of auto-reboots
196
-
1. Configuration option to print the saved error report on reboot
197
195
198
196
# Usage scenarios and examples
199
197
@@ -288,10 +286,6 @@ Enables crash context capture when the system enters a fatal error/crash. When t
288
286
289
287
Enables auto-reboot on fatal errors.
290
288
291
-
**reboot-crash-report-enabled**
292
-
293
-
Enables crash report over terminal when the system reboots after a fatal error/crash.
294
-
295
289
**error-reboot-max**
296
290
297
291
Maximum number of auto reboots permitted when an error happens.
0 commit comments