Frequently asked questions

• What are the Mbed OS error reports?

When something goes wrong with your Mbed OS based program, the program crashes and prints an error report to the serial terminal with information related to the cause and location of the error.
An example error report from Mbed OS:

++ Mbed OS error info ++
Error Status: 0x80010132 Code: 306 Module: 1
Error Message: Thread: 0x20001F0C, System is out of memory
Location: 0x1DB7
Error Value: 0x20001F0C
Current Thread: Id: 0x20001F0C Entry: 0x2701 StackSize: 0x1000 StackMem: 0x20001F58 SP: 0x20002EF0
For more info, goto: https://armmbed.github.io/mbedos-error/?error=0x80010132
-- Mbed OS error info --

• What does the Mbed OS error status mean?

Error status in Mbed OS is a 32-bit signed integer used for reporting error conditions in the system. The error statuses are always NEGATIVE and encode - type of error, module that caused the error and the error code that indicates the cause of the error.

• How do I modify the error messages to print more detailed information?

The Mbed OS error handling system exposes specific interfaces for an application or any Mbed OS subsystem to report errors or warnings. These APIs take error message strings as arguments, and clients can use these arguments to specify context-specific error messages.

• Where can I find more information on the Mbed OS error handling system?

Please look into documentation for Mbed OS error handling - https://os.mbed.com/docs/latest/apis/error-handling.html