We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I have a new installation of ARM Development Studio 2023.0. I haven't gotten to the point of requesting a 30-day evaluation license. Immediately when launching the program, the product hangs with the following dialog:
Any help would be greatly appreciated!!
Hi Ronan! This is a little O.T. but do you know if one can install and run ARM DS 2023.0 for Linux within WSL? Failing that, do you know if anyone has successfully run a Linux toolchain within WSL from outside of WSL using ARM DS 2023.0 for Windows? In either case, references to videos or white papers would be greatly appreciated! The problem I have is that, while I have ARM DS 2023.0 for Windows compiling programs, I can't remote debug them b/c I can't get the same tool chain installed on the target that is installed on ARM DS 2023.0 for Windows. I have access to a Linux guru and he has said that we can't get there from here. Here's a link to the tool chain we'd like to use: https://support.criticallink.com/redmine/attachments/download/27164/poky-glibc-x86_64-mitysom-image-base-cortexa9hf-neon-toolchain-2.4.4.sh This runs fine under WSL / Ubuntu or native Ubuntu.
Thanks in advance for your answer!!
I don't know if this would work, it is not something I have tried, and is not supported.
A common use case is to build on a different machine (often an automated Jenkins-type build server) than debugging, and so it is perfectly possible to load a Linux built image to a Windows-based debug session.
You will likely be prompted to fix the paths to the sources, which is a do-once operation for a given debug configuration:https://developer.arm.com/documentation/101470/2023-0/Controlling-Target-Execution/Configuring-the-debugger-path-substitution-rules
You can set this for the entire repository, you do not need to do this for individual files.