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
int32_terror_reboot_count;//everytime we write this struct we increment this value by 1, irrespective of time between reboots. Note that the data itself might change, but everytime we reboot due to error we update this count by 1
832
832
int32_tis_error_processed;//once this error is processed set this value to 1
833
833
uint32_tcrc_error_ctx;//crc_error_ctx should always be the last member in this struct
834
-
#endif
834
+
#endif
835
835
} mbed_error_ctx;
836
836
837
837
/** To generate a fatal compile-time error, you can use the pre-processor #error directive.
* Initialize error handling system, this is called by the mbed-os boot sequence. This is not required to be called by Application unless the boot sequence is overridden by the system implementation.
953
+
* Initialize error handling system, this is called by the mbed-os boot sequence. This is not required to be called by Application unless the boot sequence is overridden by the system implementation.
954
954
* NOTE: This function also prints the error report to serial terminal if MBED_CONF_PLATFORM_REBOOT_CRASH_REPORT_ENABLED is enabled.
955
955
* If MBED_CONF_PLATFORM_FATAL_ERROR_AUTO_REBOOT_ENABLED is enabled and if the current reboot count exceeds MBED_CONF_PLATFORM_ERROR_REBOOT_MAX the system will halt when this function is called,
956
-
* and in such cases the caller will not get the control back. Also note that calling this function may trigger mbed_error_reboot_callback() if application side overides mbed_error_reboot_callback().
956
+
* and in such cases the caller will not get the control back. Also note that calling this function may trigger mbed_error_reboot_callback() if application side overides mbed_error_reboot_callback().
* @param error_info Pointer to mbed_error_ctx struct allocated by the caller. This is the mbed_error_ctx info captured as part of the fatal error which triggered the reboot.
966
966
* @return 0 or MBED_SUCCESS on success.
967
967
* MBED_ERROR_INVALID_ARGUMENT in case of invalid error_info pointer
968
-
* MBED_ERROR_ITEM_NOT_FOUND if no reboot context is currently captured by the system
968
+
* MBED_ERROR_ITEM_NOT_FOUND if no reboot context is currently captured by the system
0 commit comments