Mistake on this page? Email us

Known issues and troubleshooting

Known issues

Mbed Studio has the following known issues:

  • Programs that you download from the Online Compiler as ZIP files contain a cut-down version of Mbed OS specific to the selected target. To select a different target, delete the Mbed OS library and replace it with a full copy of the library.
  • Some users have reported licensing issues for Arm Compiler 6. These issues may be related to the system clock and region format.
  • Trying to use Mbed Studio with Arm Compiler 6 on a remote desktop raises the FlexNet licensing error -103, because Arm Compiler 6 is not licensed for use in Remote Desktop setups. If you need to work in a Remote Desktop setup, please use GCC instead of Arm Compiler 6.
  • Build output wraps on Windows.
  • When you start a debug session, breakpoints are ignored until they are disabled and then re-enabled.
  • Windows installer does not show the individual files or tools as they are installed, causing the progress bar to jump.
  • On Linux, there is a limit on the number of files that can be watched in the workspace. Please follow the instructions on the Visual Studio documentation site to increase the limit.
  • On Linux, C/C++ IntelliSense works only on Ubuntu 16.04 and 18.04.
  • On Linux, source control management requires the libcurl4 package to work correctly.
  • On macOS, if using the installer, you must uninstall the existing version of Mbed Studio before installing a new version.
  • On Windows, the installation may fail if Windows system restart is pending.
  • On Windows, you can only connect one external probe at a time. Mbed Studio may not find a probe if you connect multiples.

Help us develop Mbed Studio by reporting issues to studio@mbed.com.

To help us reproduce and fix the reported issue, please attach the Mbed Studio log files to your report:

  1. From the Help menu, select Report an Issue. This opens the Report an issue or provide feedback window.
  2. Click Access Log. This opens the folder that contains the Mbed Studio log files.
  3. Attach the mbed-studio.log and mbed-studio.log.1 files to your email.

Troubleshooting

Can't log into Mbed Studio

Please make sure that your Mbed account credentials are correct. If you are working behind a proxy, you may need additional setup.

Compilation not working on Remote Desktop

Switch Mbed Studio to GCC, instead of Arm Compiler 6.

Connected development board not found

  1. Update the board's firmware to the latest version:
  2. ST development boards on Windows require additional drivers. You can install them through the Mbed Studio installation, or download them from ST's site.

Development board not showing serial data

  • Try to disconnect and connect the board.
  • Check that no other program is accessing the serial data on the board; the device can only connect to one serial monitor at a time.

Linker failing with "file not found" for Mbed OS 15.4.0 and older

Mbed OS 15.4.0 and older does not support spaces in the program name - the linker fails with "file not found". Change your program name and try compiling again.

Important Information for this Arm website

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies. If you are not happy with the use of these cookies, please review our Cookie Policy to learn how they can be disabled. By disabling cookies, some features of the site will not work.