Docs › Debugging and testing › Debugging › Methods › Troubleshooting common issues

Troubleshooting common issues

When you start using Mbed OS, you may find small challenges in a few cases. This section includes a list of issues that Mbed OS users frequently encounter. It also includes steps you can take to prevent and overcome these problems.

Use the latest tools

Keil Studio Cloud and Mbed Studio

Keil Studio Cloud and Mbed Studio come with a built-in debugger. For instructions on using the debugger mode and debugger tools, please see the Keil Studio Cloud or Mbed Studio documentation.

Mbed CLI

If you are using an old version of Mbed CLI, you may see compile-time errors. Make sure mbed-cli is working correctly and you are using the latest version. You can check the version of mbed-cli by writing:

mbed --version

If this version is old, update it:

pip install mbed-cli --upgrade

Compiler versions

You can build Mbed OS with various toolchains. Make sure you are using the latest versions of the toolchains. You can find the currently supported versions on our tools page.

The default toolchain profiles now select C++14 and C11. Some applications that worked with older versions of Mbed OS may fail to compile because they use constructs that were valid in C++98 but not in C++14. To fix these common compatibility issues:

A space is required when a macro follows a string literal, for example in C99-style printf formats:
```
    uint32_t val;
    printf("val = %"PRIu32, val); // Not valid in C++11
    printf("val = %" PRIu32, val); // OK
```
Without the space, C++11 interprets it as being a request for a user-defined "PRIu32-type" string literal.

Initializer lists cannot have implicit narrowing conversions:

    uint32_t x;
    uint8_t array1[] = { x }; // Not valid in C++11
    uint8_t array2[] = { 0xffff }; // Not valid in C++11
    uint8_t array3[] = { x & 0xff }; // Not valid in C++11
    uint8_t array4[] = { (uint8_t) x }; // OK
    uint8_t array5[] = { static_cast<uint8_t>(x) }; // OK
    uint8_t array6[] = { 0xffff & 0xff }; // OK (because it's a compile-time constant that fits)

Compiler licenses

If using Keil MDK (Arm Compiler) or IAR, make sure you have a license installed. For example, MDK-Lite has a 32 KB restriction on code size.

Investigate whether the Mbed OS application is crashing

Examine or undo any recent code change you made to see if it is the cause of the crash.
Build using the development or debug build profile, so the serial port shows any errors in your program.
Enable debug prints for components that have them.

Take these steps if no output is shown in the serial port

If you see no output, this can indicate a serial port problem. Find the reason for such a problem by completing the following steps:

Make sure your serial port terminal is using the same baudrate as that being configured by the Mbed OS application.
Reopen the serial port.
Type into the terminal, and verify the activity light on your board blinks.

Advanced debugging your application

There might be cases when finding the root cause of the problem requires more investigation and the use of addition debug tools. You can export the project to a third party IDE and use the Mbed interface port of your Mbed board to download and execute the Mbed OS application step by step. Read on to be guided through this process.