Hi, I read about the MBED EoL in 2026 and I found this in the FAQ of the related article:
You will not be able to build an Mbed project inside Keil Studio Cloud or Mbed Studio, but it may be possible to build a project with GCC using the Mbed CLI. As of today, Arm does not provide any support on the Mbed OS code base. This includes the Mbed CLI.
How is possibile that I will be not able to use the DESKTOP IDE if it runs on my own pc?
Hello,
Mbed Studio has an online authentication for accounts.
BR, Jan
Curious why extending the license is a problem. I was under the impression MBED is part of ARM.
I’m just a bit frustrated because I have a couple of fairly large projects which I re-use with minor changes. I’d prefer to not need to rewrite. I’m getting a warning when compiling that the license expires in 20 days.
You can switch to GCC in Mbed Studio, instruction here. In the long run, we may have to switch to Mbed-CE all together when support for Mbed Studio stops.
Hello,
My Mbed studio tells me that the compiler license expires in 17 days. We’re still far from 2026 and I have a large project to maintain in the following weeks.
Do I have to switch now ?
Hi everyone,
the need to renew the license is just an internal thing and is not releated to the Mbed OS deprecation. Don’t worry about the warning, there will be soon a new release of Mbed Studio fixing the issue.
Federico - Mbed Studio team
@federicobozzini do you have any ETA of this release with license update?
Sorry to ask but in my case it expires in 6 days.
Dear Sir, I also got below warning: L9931W your license for feature mbed_armcompiler will expire in 2 days.
This is going to affect 300 students in my school currently taking the microcontroller course.
We have planned to migrate to keil MDK/uVision 5 community licence in April 2026. The lab codes are under testing.
I have checked in ARM Mbed website, seems no new version is going to be launched to solve this issue.
In last year, such issue was resolved by releasing the new mbed version: 1.4.6.
Could you give your further advice on how shall we do?
Appreciate for any help from you.
Best regards,
Lan Bo
I received a notification when opening mbed studio that an update is available. I’m assuming that extends the license. As noted an above reply you can fairly easily switch to the GCC compiler. I did this with no issues other than the compiled file size being slightly different.
EDIT: One issue with the GCC complier is that it shows a lot of errors in the IDE. Everything compiles, but types like uint16_t, uint32_t get “unknown type” errors. I’m dealing mostly with existing code though, so I’m not really looking for errors.
I think the Mbed framework is used for some targets under Platform I/O. I tried it a few years ago and found some things rather confusing and opaque though.
I have work in Mbed that I often reuse and I’d prefer not to rewrite. I think Mbed CE might be an option moving forward, but I had issues getting it working with VS studio following their instructions. (To be fair I’ve not used VS studio much and there is plenty I don’t understand) Perhaps that will be better in the future. I’m not sure there are many people working on it though.
If you need help with MbedCE, let us know, I believe we can find a way.
BR, Jan
Hi everyone,
just to confirm a new release of Mbed Studio (1.5.0) is now available. The new release permanently fixes the license issue.
Federico - Mbed Studio team
Thanks for posting the note here. I have been using it for a couple of days already. It is a big relief that we no longer need to worry about login/authentication and also the license issue of compiler.
Going forward, any plan to open source Mbed Studio? One thing I liked Mbed Studio the most over VS Code is autocomplete seems work a lot better.