Almost ten months ago it was stated that Keil has no intention of releasing an Windows ARM driver for Keil uLinkPro. I wanted to circle back and see if that's still the plan. I find it surprising that I am rather arbitrarily forced to use Intel architecture machines to develop ARM code, especially with Windows ARM machines starting to hit the market. I installed Windows 11 on an M1 Mac under Parallels, and started a uVision trial. uVision runs great and compiles code quickly, but that solution is dead in the water without an ARM uLink driver to run the debugger.
I am really hoping that Keil reconsiders this situation.
community.arm.com/.../are-there-any-plans-to-release-ulink-drivers-for-arm64-architecture
For Keil MDK 5 usage, the Windows-based ULINKpro driver still is the solution; for details see
https://www.keil.com/support/man/docs/ulinkpro/ulinkpro_su_driver.asp
Related:
"GENERAL: Keil MDK 5 on a Mac"
https://developer.arm.com/documentation/ka002387/latest
Thank you for your reply.
To clarify: my current setup is as described in your second link. I am using an old Intel Mac running VMWare Fusion hosting Windows 10. Keil uVision runs within that environment and runs decently well and I've been doing that for ~3 years now.
The rest of my work happens on a newer Mac with Apple (ARM core) silicon, and the only reason for keeping the 2015 Intel Mac around is for embedded ARM development. I find it amusingly ironic that I am unable to develop ARM firmware using an ARM Mac, and am forced to keep an Intel machine around for this purpose.
As an aside, just as an experiment, I installed trial versions of Parallels and Windows 11 ARM on the M1 Mac, then installed a trial version of uVision, and even though uVision is meant for Intel/AMD, it ran great in whatever Rosetta-like emulation Parallels provides. The only issue is that while Parallels can run Intel Windows apps, it cannot run Intel Windows device drivers, such as the .dll required for the uLink debugger.
In your reply to the other thread ten months ago, you seemed quite certain that ARM/Keil was not going to release an ARM driver for this essential (and ironically ARM) development tool. The purpose of my post was to see whether that was still the official stance, and if ARM/Keil might be convinced to soften that stance.
It really is silly I need an Intel machine to develop ARM code!
Thanks for your time and consideration!
Dave