Hello team,
I intend to use Keil-MDK and ARM Keil Studio (AKS) for VSCode on the same computer. Both will be the Community versions for the moment. Can they coexist without side effects?
What is the proper sequence of steps for installing the two products together without interfering with each other? Should I install AKS first and MDK after? Or MDK first and AKS after? Does it matter?
Considering the two installed, what's the best way to convert MDK projects into AKS projects so that they can use the settings properly translated (like paths, file names, configuration, etc.) What is the structure of the manifest file that can help the process to have a predictable conversion?
Is it possible to do the opposite? I.e. convert AKS projects into MDK projects.
A list of prerequisites and steps for the process would be helpful.
Thank you,
Stefan
I have both tools on my laptop without issue. I had the original MDK installed first, but I doubt the install order matters
For your other questions, do these docs help?
https://developer.arm.com/documentation/108029/0000/Arm-CMSIS-csolution-extension/Convert-a-Keil--Vision-project-to-a-csolution-project
I do not believe it is possible to export from Keil Studio back to MDK.
Hello,
There are no incompatibilities as far as we are aware. You can have both Keil-MDK and the VS Code extensions installed on your machine.
For the conversion questions you had, this is indeed the procedure to convert a uvprojx to csolution: https://developer.arm.com/documentation/108029/0000/Arm-CMSIS-csolution-extension/Convert-a-Keil--Vision-project-to-a-csolution-project. You cannot do the opposite though.
Thank you.
The Keil Studio team.
Thank you for the clarification. Especially, the section of the documentation (pointed by the link) that summarizes well the procedure. The conversion eventually works. I was able to build a simple converted project. Larger projects generated some warnings and inconsistent results until VSCode + AKS managed to create the a proper environment. It looks like this process may happen in background while the user attempts to build the project. During this time the build process may generate errors and fails. It's hard to replicate the problem now. I'll keep an eye on this.Once again, many thanks.
steve58 said:Is it possible to do the opposite? I.e. convert AKS projects into MDK projects.
Not really, but we have implemented one way back to the µVision debugger. Since Keil Studio Desktop does not provide all the debug features of µVision yet, you might want to use µVision as a debug IDE for your Keil Studio Desktop project. Since MDK version 5.39 (was released on Monday this week), you can load a csolution project into µVision. However, this only enables the debugger in µVision, not the project management/build. Please see the release notes of MDK 5.39 under 'Experimental feature':developer.arm.com/.../MDK-Version-5-39
Thank you. For the moment Keil MDK 5.3x is our main focus. Students are following textbooks written with Keil MDK in mind. The labs are already equipped with Windows workstations using MDK. I wanted to offer an alternative for those familiar with Linux or MacOS. Let's not forget that some use Raspberry Pi (4 or 5) at home to learn embedded programming.