Still trying to get Visual Studio running with Windows 11 and Raspberry Pi Pico.
This time I used an install script and VS did come up, but with errors:
Unable to resolve configuration with compilerPath "${env:PICO_INSTALL_PATH}/gcc-arm-none-eabi/bin/arm-none-eabi-gcc.exe". Using "cl.exe" instead.
What does this mean? What should I do about it?
Also it didn't behave as the documentation said it would.
Documentation: ## Building an example
Visual Studio Code will ask if you want to configure the pico-examples
project when it is first opened; click *Yes* on that prompt to proceed.
(If you miss the prompt look for the 'bell' icon in the bottom right.)
You will then be prompted to select a kit -- select the *Pico ARM GCC -
Pico SDK Toolchain with GCC arm-none-eabi* entry. If the *Pico ARM GCC*
entry is not present, select *Unspecified* to have the SDK auto-detect
the compiler.
To build one of the examples, click the *CMake* button on the sidebar.
You should be presented with a tree view of the example projects; expand
the project you'd like to build, and click the small build icon to the
right of the target name to build that specific project.
I was never prompted, so I clicked on the bell and unfortunately did not save a copy of the message but it was not as stated and asked about adding extensions, I did say yes.
I am really out of my depth here and no idea what I am doing. I do know how to program in C, C++ but no experience with make files etc.
I tried to run some of the examples, and get another error:
Error: unable to find a matching CMSIS-DAP device
** OpenOCD init failed **
shutdown command invoked
Another thing I am not comfortable with is that literally everything runs out of "Downloads" directory excepts VS and Cmake. I am used to having program files under Program Files, or user/appdata and data/user files in Documents.
This time I used an install script and VS did come up, but with errors:
Unable to resolve configuration with compilerPath "${env:PICO_INSTALL_PATH}/gcc-arm-none-eabi/bin/arm-none-eabi-gcc.exe". Using "cl.exe" instead.
What does this mean? What should I do about it?
Also it didn't behave as the documentation said it would.
Documentation: ## Building an example
Visual Studio Code will ask if you want to configure the pico-examples
project when it is first opened; click *Yes* on that prompt to proceed.
(If you miss the prompt look for the 'bell' icon in the bottom right.)
You will then be prompted to select a kit -- select the *Pico ARM GCC -
Pico SDK Toolchain with GCC arm-none-eabi* entry. If the *Pico ARM GCC*
entry is not present, select *Unspecified* to have the SDK auto-detect
the compiler.
To build one of the examples, click the *CMake* button on the sidebar.
You should be presented with a tree view of the example projects; expand
the project you'd like to build, and click the small build icon to the
right of the target name to build that specific project.
I was never prompted, so I clicked on the bell and unfortunately did not save a copy of the message but it was not as stated and asked about adding extensions, I did say yes.
I am really out of my depth here and no idea what I am doing. I do know how to program in C, C++ but no experience with make files etc.
I tried to run some of the examples, and get another error:
Error: unable to find a matching CMSIS-DAP device
** OpenOCD init failed **
shutdown command invoked
Another thing I am not comfortable with is that literally everything runs out of "Downloads" directory excepts VS and Cmake. I am used to having program files under Program Files, or user/appdata and data/user files in Documents.
Statistics: Posted by Roy_H — Thu Mar 21, 2024 6:26 pm — Replies 1 — Views 63