Hi there,
My current development environment (AKS) is supposed to run on the following system:
My initial experience was unsatisfactory as AKS proved to be unstable and erratic. The PC was a clean fresh laptop with Windows 11 Pro (OEM) used for less than a week. Installing VSCode was uneventful but, maybe my choice of installation was inappropriate: installed for all users (i.e. in Program Files). The STM32F407G-DISC1 board is almost new (only used occasionally) with all the firmware updates as required by the embedded ST-Link probe.
I followed the official documentation: Arm Keil Studio Visual Studio Code Extensions - User Guide (Non-Confidential), Issue 06 - 108029_0000_06_en. I noticed the following:
Questions:1. What are the prerequisites for installing AKS for VSCode properly? (e.g. system requirements, chosen platform effects, VSCode installation, compatibility issues, 32- vs 64-bit cases and issues, software packs integration and dependencies, etc.)2. What are the configuration steps for various targets? The documentation seems incomplete and confusing as long as there aren't clear steps to follow.3. Where are the proper examples for the supported boards? The simple MDK to AKS conversion isn't reliable (multiple attempts produce, eventually, various results and various warnings and errors)4. What are the steps of the proper hardware integration of a certain target? Assuming that I build my hardware (not using an evaluation kit), what should I do to connect with it, be able to upload code, and debug it properly on my target?5. Will AKS for VSCode be replacing MDK anytime soon? If so, when will it happen? If not, what is the roadmap for Keil MDK? Will it continue to exist as MDK5? Will it be an MDK6 (or higher)?6. Is AKS only intended for non-commercial and educational purposes at this moment? I don't see how AKS could be used efficiently and reliably in an enterprise environment yet. What is the roadmap for AKS?7. The AKS debugging features look rudimentary compared with the MDK debugger. Are there any plans to improve the AKS debugger and add features like trace, logic analyzer, register/port viewer, power measurements, and more?
I know, it's a long message. After a few days of frustrating efforts, I'm at the end of the rope. I intended to use AKS with my students because it is multi-platform and many like the idea of working with VSCode. But, to be honest, I cannot recommend them AKS. Maybe AKS for Cloud is better. But not AKS for VSCode. We will continue with Keil-MDK for the moment until we find a better solution. At this moment I almost regret not using STM32Cube. The reason for selecting Keil-MDK was the availability of a huge amount of literature and documentation that the students could use combined with good debugging features supporting a multitude of probes. Last but not least, once you learn Keil-MDK you can use it for almost any ARM Cortex-M on the planet.The intention of updating the user experience of Keil tools to the 21st century is laudable. I applaud the attempt but I feel that the road ahead is long and bumpy. I would appreciate comments, advice, pointers to better documentation, and other information regarding AKS. (See the above questions.)
But I won't use it with my students in January when the winter term begins. I will only mention its existence for those inclined to take the challenge and use it.
Thank you for your time reading this.
Steve