You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,10 +6,16 @@ All notable changes to the "pico-w-go" extension will be documented in this file
6
6
7
7
## Known issues
8
8
- Run current file does not include modules that are localy imported and in current workspace, unless you upload the python file containing the module via the upload file or project feature first. (since ever)
9
-
- Mounting virtual workspace causes existing vREPLs to freeze so they need to be disposed manually for some reason. (maybe cauaused by vscode)
9
+
- Mounting virtual workspace causes existing vREPLs to freeze (*sometimes*) so they need to be disposed manually for some reason. (maybe cauaused by vscode)
10
+
- Scripts without a print statement sometime causes the extension to freeze
Copy file name to clipboardExpand all lines: README.md
+23-17Lines changed: 23 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,17 +5,17 @@ Pico-W-Go provides code auto-completion and allows you to communicate with your
5
5
> __Auto-completion based on Raspberry Pi Pico W MicroPython firmware: [rp2-pico-w-20230407-unstable-v1.19.1-1009-gcfd3b7093.uf2](https://micropython.org/resources/firmware/rp2-pico-w-20230407-unstable-v1.19.1-1009-gcfd3b7093.uf2)__
6
6
7
7
Works with:
8
-
| Platform | Architectures |
9
-
|----------|:------------------:|
10
-
| Windows |x64, arm64 |
11
-
| macOS |x64, arm64 |
12
-
| Linux |x64, arm64, armvhf|
8
+
| Platform |x64 | arm64 / aarch64 | armv7l|
9
+
|----------|:---:|:--------------:|:------:|
10
+
| Windows |:white_check_mark:|:white_check_mark:|:x:|
| Linux |:white_check_mark:|:white_check_mark:|:white_check_mark:|
13
13
14
14
## Features
15
15
16
16
- Auto-completion and docs
17
-
-Terminal integration for communication with MicroPython REPL on a Pico (w) board
18
-
- Running/Transferring files to/from your board
17
+
-Pseudo terminal integration for communication with MicroPython REPL on a Pico (w) board
18
+
- Running / Transferring files to / from your board
19
19
- Built-in virtual-workspace provider for Raspberry Pi Pico (W) boards
20
20
21
21

@@ -25,19 +25,19 @@ Works with:
25
25
*[MicroPython firmware](https://micropython.org/download) flashed onto the Raspberry Pi Pico (W):
26
26
- See [Raspberry Pi docs](https://www.raspberrypi.com/documentation/microcontrollers/micropython.html#drag-and-drop-micropython) for help.
27
27
28
-
*[Python 3.9 or newer](https://www.python.org/downloads/) installed on your system and in your PATH.
28
+
*[Python 3.9 or newer (with pip)](https://www.python.org/downloads/) (user install; Microsoft Store version not supported but may work) installed on your system and in your PATH.
On most Linux installations the device file of the Pico serial port is owned by root and a group you normal don't have by default. This leads to timeout and access denied errors when Pico-W-Go tries to connect to the Pico. There are three ways how to solve this problem:
39
-
1. Run VS Code in sudo (NOT RECOMMENDED)
40
-
2. Normaly adding your user to `dialout` group should fix the issue: `sudo usermod -a -G dialout $THEUSER` (logout required)
38
+
On most Linux installations the device file of the Pico serial port is owned by root and a group you normal don't have by default (*except on Raspbian OS*). This leads to timeout and access denied errors when Pico-W-Go tries to connect to the Pico. There are three ways how to solve this problem:
39
+
1. Run VS Code in sudo (__NOT RECOMMENDED__)
40
+
2. Normaly adding your user to `dialout` group should fix the issue: `sudo usermod -a -G dialout $USER` (logout required)
41
41
3. Dynamically add the group who "owns" the serial port file to your current user. You can easily do this by downloading and executing the `scripts/solvePermissions.sh` script. However you **have** to change the marked line in the script if you Raspberry Pi Pico (w) does not connect to/shows up as `/dev/ttyACM0` to the correct device file. The script will readout the group owning the device file and then add you to this group. (logout required)
- First of all open a folder and run `Pico-W-Go > Configure Project` command via `Ctrl+Shift+P` (or the equivalent on your platform) VS Code command palette. This will import stubs for autocompletion and the settings into your project folder. For the auto-completion to work, the extension prompts you (after project configuration) to install recommended extensions mentioned in \#Requirements.
54
+
- First of all open a folder and run `> Pico-W-Go > Configure Project` command via `Ctrl+Shift+P` (or the equivalent on your platform) VS Code command palette. This will import stubs for autocompletion and the settings into your project folder. For the auto-completion to work, the extension prompts you (after project configuration) to install recommended extensions mentioned in [\#Requirements](#requirements).
55
+
56
+
- If you have trouble running `> Pico-W-Go > Configure Project`, try setting following settings in your global VSCode `settings.json`:
- Have the onboard LED flashing in under 5 minutes:
57
62
> Note that [accessing the onboard LED is slightly different for the Pico W compared with the Pico (Page 15 Chapter 3.4)](https://datasheets.raspberrypi.com/picow/connecting-to-the-internet-with-pico-w.pdf). So, you can use the following script in place of `flash.py`:
0 commit comments