raspberrypi / pico-setup-windows Goto Github PK

As a developer, I have installed VScode, Cmake, Ninja, Pyhton and arm-none-eabi-gcc.

I don't need it will be installed twice.

It would be handy if I could install only tools specific to rp2040.

Thank you.

Hi,

Just used this setup for the first time and was wondering if there is a correct way to update the installed SDK?

I like to keep the SDK updated as often as possible but the installer seems to create a shallow copy of SDK repo so I manually deleted the it and did a full clone to the same place so that I can git pull every so often.

Will this cause any issues (haven't personally found any so far) or is there a better way?

Thanks

As Shown In The Image It Dosent Let Me Get Passed This Screen Even If I Change The Location

Running setup on windows 10 I get the following failure.

After installing the PICO SDK, I only get the following start menu links:

This is on my work machine, so it was not a surprise that my already complicated environment would cause issues. However, I had a coworker with no software installed (he's a mechanical guy) run the installer, and he had the same results. We're both on Windows 10. The installer log shows that all was well, and it claims that it installed all the links, but we don't see them:

Directly running pico-code.ps1 works fine for both of us, so everything appears to have installed correctly except for the shortcuts themselves. I do most of my development work on Linux, so this is the first time I have used the Windows installer. I'm not sure if I've missed something. I have tried rerunning the installer which simply uninstalls and re-installs with the same results.

I suspect the fact that the first shortcut was successfully created and the second and third were not might be a hint at the root cause, but I am not familiar enough with Windows installer packages to know for sure.

Hi, not sure if this is the right place to ask this.

I very much appreciate this automated installer for C development on Windows for the Pico boards, but I'd like simply cmake my own project code and run the command to build the executables with the uf2 binaries without debugging if that makes sense. How should I go about doing that? What settings do I change and where?

Thanks in advance

With the new v1.5.1 installer, no new key in "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Raspberry Pi" gets created anymore.

Using Firefox (116.0.2 (64-bit)) and Edge (Version 115.0.1901.203 (Official build) (64-bit)) web browsers, clicking on the windows installer download link leads to downloading a file named unconfirmed[random_number].crdownload.

The current fix is very simple, just manually rename the file extension to .exe, and eveything works as expected from then on.

Hi, friends.

I have download and run Windows Pico Installer.

But I got following error when I tried to make the pico-examples folder:

Compiler 'arm-none-eabi-gcc' not found

What should I do? Add a "PICO_TOOLCHAIN_PATH" env variable? What value should be?

I am using Windows 11 22H2 22621.1555

Hello all, I installed the pico sdk as indicated in the pico-setup-windows git, set the environment variables, PICO_SDK_PATH and
PICO_EXAMPLES_PATH, I can cmake and build all of the example programs just fine.

I followed your example for creating a new project from the pico-setup-windows/docs
/tutorial.md

I created the CmakeLists.txt files as indicated in this tutorial.

When I attempt to make my new project I get the following error:
[cmake] Not searching for unused variables given on the command line.
[cmake] CMake Error at src/CMakeLists.txt:12 (pico_add_extra_outputs):
[cmake] Unknown CMake command "pico_add_extra_outputs".

I must be missing a path or something.

Please let me know what the resolution is to this issue.

Cheers

Joe

Hi,

Is it possible to configure the setup executable through a Windows proxy?

Running the pico-windows-setup program from a location requiring a proxy fails, and supporting a proxy could simply setup of the overall environment...

Thanks,

Steve

How to overcome the missing components as shpwn in the Pico-Developer Command Pr

ompt

In following the tutorial on coping all of the files and creating the make files. When I make the new project
I get all of the below cmake errors.

When I cmake and built the example project, everything worked just fine.

Now I create a new project, with no files I get the below cmake errors:

[cmake] Missing variable is:
[cmake] CMAKE_ASM_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_CXX_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_CXX_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_ASM_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_ASM_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_ASM_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_ASM_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_ASM_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_ASM_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_ASM_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_ASM_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_ASM_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_ASM_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_ASM_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_CXX_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_C_COMPILE_OBJECT
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_LIBRARY_PATH_FLAG
[cmake] CMake Error: Error required internal CMake variable not set, cmake may not be built correctly.
[cmake] Missing variable is:
[cmake] CMAKE_LIBRARY_PATH_TERMINATOR

Could you please give some insight on why I am getting this issue?

Cheers

Joe

I tried to compile my project PTPE with branch sdk15 with the windows installer for pi pico development. https://github.com/NicoAICP/PTPE/tree/sdk15
The uf2 compiles just fine, but after plugging it into my pc and selecting skylanders, it throws the issue that the device couldnt be started (code 10).
If i compile the project using linux, same sdk version and everything, I do not get the error code 10 and it boots up just fine.

Could you guys take a look, if this is an issue with the windows installer?
You probably wont be able to run my code due to it needing hardware for the pi pico, but it should work the same if you just create a tinyusb project acting as a hid device.

After installing pico-setup-windows-x64-standalone when I load Pico - Visual Studio Code and created a new project, when I try to CMAKE:PROJECT OUTLINE and build a copy of the picow_tcp_client.c I get the below. All files are in the root of the project.

Does it only do cmake -DPICO_BOARD=pico .. rather than cmake -DPICO_BOARD=pico_w .. and it does not have the right board? If so what is the fix?

CMakeLists.txt
lwipopts_examples_common.h
lwipopts.h
pico_sdk_import.cmake
picow_tcp_client.c

picow_tcp_client.c:11:10: fatal error: pico/cyw43_arch.h: No such file or directory
[build]    11 | #include "pico/cyw43_arch.h"
[build]       |          ^~~~~~~~~~~~~~~~~~~
[build] compilation terminated.

my CMakeLists.txt

cmake_minimum_required(VERSION 3.13)

# Pull in SDK (must be before project)
include(pico_sdk_import.cmake)

project(badge1 C CXX ASM)
set(CMAKE_C_STANDARD 11)
set(CMAKE_CXX_STANDARD 17)

set(PICO_EXAMPLES_PATH ${PROJECT_SOURCE_DIR})

# Initialize the SDK
pico_sdk_init()

add_compile_options(-Wall
        -Wno-format          # int != int32_t as far as the compiler is concerned because gcc has int32_t as long int
        -Wno-unused-function # we have some for the docs that aren't called
        -Wno-maybe-uninitialized
        )

if (PICO_CYW43_SUPPORTED) # set by PICO_BOARD=pico_w
    if (NOT TARGET pico_cyw43_arch)
        message("Skipping Pico W examples as support is not available")
    else()

        if (DEFINED ENV{WIFI_SSID} AND (NOT WIFI_SSID))
            set(WIFI_SSID $ENV{WIFI_SSID})
            message("Using WIFI_SSID from environment ('${WIFI_SSID}')")
        endif()

        if (DEFINED ENV{WIFI_PASSWORD} AND (NOT WIFI_PASSWORD))
            set(WIFI_PASSWORD $ENV{WIFI_PASSWORD})
            message("Using WIFI_PASSWORD from environment")
        endif()

        set(WIFI_SSID "${WIFI_SSID}" CACHE INTERNAL "WiFi SSID for examples")
        set(WIFI_PASSWORD "${WIFI_PASSWORD}" CACHE INTERNAL "WiFi password for examples")
    endif()
endif()

set(WIFI_SSID "${WIFI_SSID}" CACHE INTERNAL "WiFi SSID for examples")
set(WIFI_PASSWORD "${WIFI_PASSWORD}" CACHE INTERNAL "WiFi password for examples")

add_executable(badge1
        picow_tcp_client.c
        )
target_compile_definitions(badge1 PRIVATE
        WIFI_SSID=\"${WIFI_SSID}\"
        WIFI_PASSWORD=\"${WIFI_PASSWORD}\"
        TEST_TCP_SERVER_IP=\"${TEST_TCP_SERVER_IP}\"
        )
target_include_directories(badge1 PRIVATE
        ${CMAKE_CURRENT_LIST_DIR}
        ${CMAKE_CURRENT_LIST_DIR}/.. # for our common lwipopts
        )
target_link_libraries(badge1
        pico_cyw43_arch_lwip_threadsafe_background
        pico_cyw43_arch_lwip_poll
        pico_stdlib
        )

pico_add_extra_outputs(badge1)

With the first setup everything works fine, eben Debugger is working, but if you leave
VSC and restart, even the include path for the stdlib.h is lost.
Cmake reports:
Bad CMake executable: "". Check to make sure it is installed or the value of the "cmake.cmakePath" setting contains the correct path.

Forgot to write some vars permantently?

The "Pico - Visual Studio Code" start menu link seemed to do nothing on my Win 10 machine. Turns out that the execution of .ps1 scripts was prohibited by the default PS execution policy. "set-executionpolicy unrestricted" fixed this for me. I'm a little confused why nobody else seems to run into this problem (I personally never used Powershell so far).

The setup should probably check the active execution policy for power shell scripts and make some suggestions.

In certain environments, this will be reproduced by running the installer as usual and launching Pico - Developer PowerShell.

Sorry for the Japanese UI, but it says "The expression after '&' in a pipeline element produced an object that was not valid. It must result in a command name, a script block, or a CommandInfo object."

This indicates that $env:COMSPEC is not defined. In fact, echo $env:COMSPEC did not print anything. Of course, I did not intentionally erase it... perhaps.

The disappearance seems to be a common occurrence, as evidenced by reports of similar problems occurring in other projects (other 3rd party applications supposedly erasing it? I have not investigated further).
ref: ScoopInstaller/Scoop#3845

Anyway, $env:COMSPEC is just an environment variable, and since it can disappear or contain strange things, some people think it is wise to specify cmd.exe directly if we obviously know we will use it.
ref: ScoopInstaller/Scoop#4692

hi
I've followed your tutorials and it's working fine when I'm running the examples, when I've tried to create a new project using it this is what I'm getting

PS C:\> copy ${env:PICO_SDK_PATH}\external\pico_sdk_import.cmake .
copy : Cannot find path 'C:\external\pico_sdk_import.cmake' because it does not exist.
At line:1 char:1
+ copy ${env:PICO_SDK_PATH}\external\pico_sdk_import.cmake .
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : ObjectNotFound: (C:\external\pico_sdk_import.cmake:String) [Copy-Item], ItemNotFoundExce
ption
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.CopyItemCommand

What am I doing wrong? Is it to do with setting the pico sdk path in environment variables?

Clicking the bottom debug icon in Visual Studio Code produces an error:

[proc] Executing command: "C:/Program Files/Raspberry Pi/Pico SDK v1.5.1/gcc-arm-none-eabi/bin/arm-none-eabi-gdb.exe" --version
[proc] The command: "C:/Program Files/Raspberry Pi/Pico SDK v1.5.1/gcc-arm-none-eabi/bin/arm-none-eabi-gdb.exe" --version exited with code: 1
[proc] Executing command: gdb --version
[proc] The command: gdb --version exited with code: 1

Are the forward slashes correct?

On Windows 11 x86-64
After install finishes and when it starts to install the pico-examples into the def

The system cannot find the file specified.
Copying pico-examples...
New-Item : Could not find file 'Pico-v1.5.1'.
At
C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\Microsoft.PowerShell.Archive\Microsoft.PowerShell.Archive.psm1:318
char:32
+ ... eatedItem = New-Item -Path $DestinationPath -ItemType Directory -Conf ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (C:\Users\Stuart\Documents\Pico-v1.5.1:String) [New-Item], FileNotFoundExcep
   tion
    + FullyQualifiedErrorId : CreateDirectoryIOError,Microsoft.PowerShell.Commands.NewItemCommand


C:\Program Files\Raspberry Pi\Pico SDK v1.5.1>

Hi,
When working in Windows, I generally like to work in a regular account, but when trying to install the Pico-SDK environment in Win11, I encountered errors and was unable to complete the installation.

I believe this stems from the choice of directories in which the SDK and sample files are stored...

Is it possible to override this location, so the files themselves can be stored in a "public" directory structure on the machine?

Thanks,
Steve

OS: Windows 11 Pro 22H2
Installer version: 1.5.1
Picoprobe version: picoprobe-cmsis-v1.0.2 (used picoprobe.uf2)
Both the picoprobe and target device are standard Raspberry Pi Picos.

Debugger profile: Pico Debug (Cortex-Debug)
Kit: Pico ARM GCC

I have been using Pico for a while, but I recently did a fresh installation on a new system and used the updated instructions from the getting started guide (which included this installer).

I followed the steps in the getting started guide and the readme that opens after running the installer. Everything builds perfectly and the environment seems to be set up correctly.

I then followed the instructions for setting up Picoprobe from the getting started guide (Appendix A). I did a fresh installation of OpenOCD, gdb, and updated all of the MSYS packages. I also used the latest picoprobe prebuilt .uf2 from their repo. Everything installed cleanly, no issues. The picoprobe is picked up in device manager as "Picoprobe CMSIS-DAP v2". I'm using the installer's VSCode config files and the latest version of pico_sdk_import.cmake.

When I try to start the debugger in VSCode, it errors out. Console outputs are below. However, when I run OpenOCD and gdb from the command line, it seems to connect properly (I can't do any extensive testing since I don't know the command line versions at all). The program pointers are picked up for both cores, they are both initialized, and everything appears connected according to the OpenOCD output.

Any help?

VSCode Debugger Outputs:

Build Output:

[main] Building folder: pico-pwm-audio all
[build] Starting build
[proc] Executing command: "C:\Users\Michael\DATA\Projects\Raspberry Pi\Pico SDK v1.5.1\cmake\bin\cmake.EXE" --build c:/Users/Michael/DATA/Projects/pico-pwm-audio/build --config Debug --target all --
[build] ninja: no work to do.
[driver] Build completed: 00:00:00.170
[build] Build finished with exit code 0

Debug Console:

Cortex-Debug: VSCode debugger extension version 1.12.0 git(d7a405a). Usage info: https://github.com/Marus/cortex-debug#usage
Reading symbols from arm-none-eabi-objdump --syms -C -h -w C:/Users/Michael/DATA/Projects/pico-pwm-audio/build/pico-pwm-audio.elf
Reading symbols from arm-none-eabi-nm --defined-only -S -l -C -p C:/Users/Michael/DATA/Projects/pico-pwm-audio/build/pico-pwm-audio.elf
Launching GDB: arm-none-eabi-gdb -q --interpreter=mi2
    IMPORTANT: Set "showDevDebugOutput": "raw" in "launch.json" to see verbose GDB transactions here. Very helpful to debug issues or report problems
Launching gdb-server: "C:/Users/Michael/DATA/Projects/openocd/openocd.exe" -c "gdb_port 50000" -c "tcl_port 50001" -c "telnet_port 50002" -s "C:\\Users\\Michael\\DATA\\Projects\\pico-pwm-audio" -f "c:/Users/Michael/.vscode/extensions/marus25.cortex-debug-1.12.0/support/openocd-helpers.tcl" -f interface/cmsis-dap.cfg -f target/rp2040.cfg -c "adapter speed 5000"
    Please check TERMINAL tab (gdb-server) for output from C:/Users/Michael/DATA/Projects/openocd/openocd.exe
Finished reading symbols from objdump: Time: 86 ms
Failed to launch OpenOCD GDB Server: Error: spawn C:/Users/Michael/DATA/Projects/openocd/openocd.exe ENOENT

Terminal:

[2023-06-17T00:12:40.276Z] SERVER CONSOLE DEBUG: onBackendConnect: gdb-server session connected. You can switch to "DEBUG CONSOLE" to see GDB interactions.
"C:/Users/Michael/DATA/Projects/openocd/openocd.exe" -c "gdb_port 50000" -c "tcl_port 50001" -c "telnet_port 50002" -s "C:\\Users\\Michael\\DATA\\Projects\\pico-pwm-audio" -f "c:/Users/Michael/.vscode/extensions/marus25.cortex-debug-1.12.0/support/openocd-helpers.tcl" -f interface/cmsis-dap.cfg -f target/rp2040.cfg -c "adapter speed 5000"
[2023-06-17T00:12:42.510Z] SERVER CONSOLE DEBUG: GDBServerConsole: onBackendConnect: gdb-server program client error Error: read ECONNRESET
[2023-06-17T00:12:42.514Z] SERVER CONSOLE DEBUG: onBackendConnect: gdb-server session closed
GDB server session ended. This terminal will be reused, waiting for next session to start...

I installed the SDK by running "pico-setup-windows-x64-standalone.exe". Everything was installed without error messages. Example projects compile without problems.

Then, I tried to run the Pico Project Generator (github.com/raspberrypi/pico-project-generator) with the "--gui" option and found that tkinter was missing.
A search on the internet revealed that with newer versions of Python, tkinter ist always included. Here, version 3.9.13 installed, but tkinter is missing.
Is there an issue in the Python installation routine or how can I install tkinter manually?

Thx.

Installer refuse to work on Arm64 Windows 11. Is there a reason for this?

If VS Code was installed with "add to PATH environment variable" not checked in the VS Code Setup, the "Pico - Visual Studio Code" link seems to do nothing (no error message etc.).

The pico-setup and/or the pico-code.ps1 should probably check if VS Code is actually available in the path and give some meaningful feedback if it is not.

Basically what the title says -- building for Pico W require extra build flags specifying that the board is a Pico W, network SSID, and network password. The Cmake tab doesn't pick up the Pico W examples as Cmake projects, and there is no way to set these flags to build them.

Setup script version: 1.5.1
OS: Windows 11 Pro

I tried to remove all the old components because I constantly had issues I could not figure out. I think I may not have had all the componentes linked properly. I was quite excited to find a full install for windows but when I tried to compile anything I get this errror

CMake Error at CMakeLists.txt:7 (project):Running
'nmake' '-?'
failed with:
The system cannot find the file specifiedCMake (project)

As near as I can find that is one of the most key commands for the CMakeLists.txt. Any ideas?

Bob

Hi

I followed the instructions on this page to create a new project and realised the .vscode folder that was copying was empty.

(https://github.com/raspberrypi/pico-setup-windows/tree/master/docs)/tutorial.md

I assume the contents should be copied too? If so I think this is the correct command:

Copy-Item ${env:PICO_EXAMPLES_PATH}.vscode -recurse

I am not able to see TinyUsb examples in workspace folder despite being installed in Program Files/PicoSDK.

Clearly not all users are using Parallels on an Apple Silicon system, but it is very unfortunate that, despite having Rosetta, that one cannot use this project to install in this environment. I, fortunately have a x86 Mac as well and will try on that platform.

This is not to knock this project. I greatly appreciate the work. Just wish there was a Mac Silicon fork.

Thank you.

Include VSCode in the installer (may be an option).
Add the "data" folder to VSCode so that the extensions will also be installed locally.
And provide a "portable" version of pico-setup in .zip format without any installation.