Repository navigation
Expand file tree
/
Copy pathREADME.txt
More file actions
62 lines (39 loc) · 3.18 KB
/
Copy pathREADME.txt
File metadata and controls
62 lines (39 loc) · 3.18 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
# Pico Setup for Windows
## Install
There are three installation methods available:
1. The standalone installer (pico-setup-windows-x64-standalone-user.exe) -- this is the recommended installer for most users. The installer does not need administrative privileges, and no system-wide changes are made.
2. The system installer (pico-setup-windows-x64.exe) -- this installer runs the installers for each included tool (those that have installers.) Other files (including the RISC-V toolchain, Pico SDK and tools, etc.) are copied to the chosen installation directory.
3. The zip archive (pico-setup-windows-x64.zip) -- just extract this and go.
The installers offer selectable install types. This table shows what each one includes:
Component Full Typical Minimal
----------------------------------- ---- ------- -------
Arm GNU Toolchain x x x
CMake x x x
Ninja x x x
Pico SDK Tools (picotool, pioasm) x x x
pico-sdk x x x
RISC-V GNU Toolchain x x
OpenOCD x x
pico-examples x x
pico-extras x
pico-playground x
Python x
Git for Windows x
The Typical install leaves out tools you probably have already, like Python and Git, as well as the extra example code in pico-extras and pico-playground.
Note that the installation/extraction directory path should be kept short, ideally under 30 characters -- this is because the build paths generated by CMake can otherwise get too long for GCC/Ninja etc. to handle.
The only registry entry written by the installers is the entry for _Apps and Features_ (previously _Add/Remove Programs_).
## Usage
To build and debug projects using command-line tools, you can open a terminal window using the _Pico - Developer Command Prompt_ or _Pico - Developer PowerShell_ shortcuts added by the installers.
The installers also add Pico Command Prompt and PowerShell entries to Windows Terminal, if you have it installed.
### Quick start with pico-setup.cmd
You can run pico-setup.cmd to set up the environment and test building some examples from pico-examples.
### Command Prompt
Run pico-env.cmd to set up the required environment variables.
If you downloaded the zip archive, you can create a shortcut that opens Command Prompt with the Pico SDK environment, using a command line like this:
cmd.exe /k "<Path to pico-setup-windows distribution>\pico-env.cmd"
### PowerShell
You will need to dot-source the pico-env.ps1 script.
If you downloaded the zip archive, you can create a shortcut that opens PowerShell with the Pico SDK environment, using a command line like this:
powershell.exe -NoExit -File "<Path to pico-setup-windows distribution>\pico-env.ps1"
## Uninstall
Open the _Apps and Features_ section in Windows Settings, then select _Pico SDK <version>_. Click the _Uninstall_ button and follow the prompts.