I have Keil MDK 5.39 installed on my laptop. A few days ago, I noticed a message about the expiration date of the license coming soon. I do not intend to upgrade to MDK 5.4x yet as I'm trying to finish some work and I don't intend to waste time with installation issues for the moment. Last year I sent the PSN found on the download page and I forum and received the license ID code. However, this year the registration process has changed and it uses a license server. Some people here noticed problems activating the product (errors communicating with the server).Question: how should I (re)activate my MDK (5.39) this year to keep it going for some time beyond the license expiration date without upgrading to 5.4x yet? Is it even possible? I need to mention that I need to finish my project without changing tools for another 2 or 3 months. We are using the tools in university and I cannot break anything that works.
Thank you
The Keil MDK Community Edition supports the latest MDK release:
https://www.keil.arm.com/mdk-community/
If your MDK Community license expires
- ...and you intend to keep on working with the MDK Community edition, you have to migrate to the latest MDK release
- or you have to order a license key for an MDK version introduced below from your local distributor, and former MDK versions are supported.
https://www.arm.com/products/development-tools/distributors
https://developer.arm.com/Tools%20and%20Software/Keil%20MDK#Editions
This is a limitation that didn't exist in the past. It was possible to keep the installed version by using the published PSN for Community editions and getting a new license. I asked this question last year and I received the following reply: "Simply repeat the registration as done the previous time and as described in the related information on the web to receive a new license key (LIC) for your MDK installation." I followed the advice and I continued to use MDK 5.37 without problems for another 3...4 months when I migrated to 5.38a, then 5.39. With 5.40 the licensing process has changed. Does this mean that I am forced to upgrade even if it can be disruptive for a project in progress? (It is a well known saying "If it ain't broken, don't change it")Please check the following posting for an example of failure to activate (disruptive): Keil MDK Community Edition activate failed
In this case, start the update process with Step 3 of