raspberrypi/pico-setup-windows issues and pull requests

#53 - Release for SDK 2.0.0

Issue - State: closed - Opened by Manu3l0us 5 months ago - 3 comments

#52 - Freertos Example does not come up as an option when 'Creating New Project from Example'

Issue - State: closed - Opened by SpencerWF-Machnet 5 months ago - 1 comment

#51 - Validate output of pico-env.cmd before setting env. variables

Pull Request - State: open - Opened by daniol 6 months ago

#50 - pico-env.ps1 tries to set up wrong env. variables

Issue - State: closed - Opened by daniol 6 months ago - 1 comment

#49 - Update README.md

Pull Request - State: closed - Opened by andrum993 6 months ago - 3 comments

#48 - No support for SDK 2.0

Issue - State: closed - Opened by BenZonneveld 6 months ago - 1 comment

#47 - Unable to uninstall Pico SDK

Issue - State: closed - Opened by Intechgreater 7 months ago - 3 comments

#46 - Pico examples project build fails on windows 10

Issue - State: closed - Opened by benji7480 8 months ago - 1 comment

#45 - Just flash ELF without debugging

Issue - State: closed - Opened by Slion 8 months ago - 4 comments

#44 - Pico examples project build fails on windows 10

Issue - State: closed - Opened by benji7480 8 months ago - 4 comments

#43 - Another cmake issue

Issue - State: closed - Opened by jpitz31 9 months ago - 1 comment

#42 - cmake issue

Issue - State: closed - Opened by jpitz31 9 months ago - 1 comment

#41 - Add local Visual Studio Code just like other included software

Issue - State: closed - Opened by vbolshakov about 1 year ago - 7 comments

#40 - The system cannot find the file specified.

Issue - State: closed - Opened by sdwood68 about 1 year ago - 2 comments

#39 - Changing from debug to build and run for a Pico W

Issue - State: closed - Opened by XeYaRiQu about 1 year ago - 11 comments

#38 - GDB Error 1 in Visual Studio Code on Windows

Issue - State: closed - Opened by progvault about 1 year ago - 5 comments

#37 - No suitable code signing certificates found

Issue - State: closed - Opened by chgenly about 1 year ago - 6 comments

#36 - Use of $env:COMSPEC may be invalid in some cases.

Issue - State: closed - Opened by U-1F992 about 1 year ago - 2 comments

#35 - TinyUSB are not visible in VSCode workspace

Issue - State: closed - Opened by M0n7y5 about 1 year ago - 4 comments

#34 - Installer not working on Windows 11 on Arm64

Issue - State: closed - Opened by Nabla128k over 1 year ago - 6 comments

#32 - Keeping the SDK repo updated as often as possible

Issue - State: closed - Opened by Nippius over 1 year ago - 2 comments

#31 - Installer able to install Pico_W SDK?

Issue - State: closed - Opened by zackfuchtel over 1 year ago - 3 comments

#30 - Installer Cant Get Pased The Choose Location

Issue - State: closed - Opened by Cyberbulat over 1 year ago - 2 comments

#29 - Problem finding path with new project

Issue - State: closed - Opened by Sarahelma over 1 year ago - 2 comments

#28 - Latest pico installer downloading as unconfirmed[random_number].crdownload

Issue - State: closed - Opened by ozoidemi over 1 year ago - 2 comments

#27 - Installer not checking PowerShell execution policy

Issue - State: closed - Opened by wattyka over 1 year ago - 2 comments

#26 - Pico - Visual Studio Code link does nothing if VS code is not in PATH

Issue - State: closed - Opened by wattyka over 1 year ago - 2 comments

#25 - v1.5.1 does not create all registry keys anymore

Issue - State: closed - Opened by paulober over 1 year ago - 8 comments

#24 - New install not working

Issue - State: closed - Opened by ParrSt over 1 year ago - 12 comments

#23 - No way to build Pico W examples from VSCode Cmake tab

Issue - State: closed - Opened by mdrobot7 over 1 year ago - 5 comments

#22 - Starting picoprobe debugging with VSCode not working

Issue - State: closed - Opened by mdrobot7 over 1 year ago - 7 comments

#21 - SDK 1.5.1 Release

Pull Request - State: closed - Opened by ndabas over 1 year ago

#20 - Update tutorial.md

Pull Request - State: closed - Opened by ivancmz over 1 year ago - 1 comment

#19 - Missing components

Issue - State: closed - Opened by mohdrais almost 2 years ago - 2 comments

#18 - Setup through proxy

Issue - State: closed - Opened by SteveCan1 almost 2 years ago - 3 comments

#17 - Installation from normal (not Administrator) account

Issue - State: closed - Opened by SteveCan1 almost 2 years ago - 2 comments

#16 - Start menu links not all being installed

Issue - State: closed - Opened by willeccles almost 2 years ago - 10 comments

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

Issue - State: closed - Opened by philwu almost 2 years ago - 8 comments

#14 - add ability to specify what need to install.

Issue - State: closed - Opened by slyshykO almost 2 years ago - 5 comments

#13 - Project using TinyUSB installed with windows installer only shows code :10

Issue - State: closed - Opened by NicoAICP almost 2 years ago - 2 comments

#12 - python installed without tkinter?

Issue - State: closed - Opened by ullibak almost 2 years ago - 13 comments

#11 - After first installation cmake is not working anymore

Issue - State: closed - Opened by AndreasMainz almost 2 years ago - 4 comments

#10 - Windows 11 Not supported (possible on an ARM install only)

Issue - State: closed - Opened by dcomer almost 2 years ago - 9 comments

#9 - Windows create new project tutorial command does not include vscode settings

Issue - State: closed - Opened by JazzBrown1 almost 2 years ago - 3 comments

#9 - Windows create new project tutorial command does not include vscode settings

Issue - State: closed - Opened by JazzBrown1 almost 2 years ago - 3 comments

#8 - Unable to build after install on new project

Issue - State: closed - Opened by mytechnotalent almost 2 years ago - 2 comments

GitHub / raspberrypi/pico-setup-windows issues and pull requests