vscode-circuitpython V2 READMEThis extension aspires to bring your entire CircuitPython workflow into a single place in VSCode. Inspired by Scott Hanselman's blog post and the VSCode Arduino extension. I have forked the original extension in order to apply fixes Note: If updating and opening an existing CIRCUITPY folder, please re-select the board from the list. Please let me know if a board needs to be included. The metadata.json file contains 550 boards, 8 of which have yet to be released or have unknown manufacturers. Getting StartedThe extension will currently activate when any of the following occurs:
Upon activation, the extension will check for the latest
Adafruit_CircuitPython_Bundle
and download it if needed. It'll then load that library metadata into the
workspace's state. You can also trigger this manually with After that, you should be ready to use the following features. FeaturesLibrary Managementv0.0.2 introduced a Circup inspired library manager with an emphasis on VSCode integration. It downloads new bundles automatically. You can use it with the following commands:
Serial Console
Hit Note: There are Linux permissions issues with the serial console, but if you're on Linux, you're probably used to that. It will also change your workspace's default If you want to choose a different board manually, a list is available with the
command NOTE FOR WINDOWS USERS: I have seen trouble with the serial console displaying anything at all. If that happens, try launching VSCode as an administrator and see if it works. I have even gotten it to work as a non-administrator after this, so perhaps running it as an admin stole the serial port from whatever was using it, and then whatever it was didn't grab it again. Auto CompleteAutomatically adds stubs for your specific board, the circuitpython standard library and all py source files in the adafruit bundle to your completion path. DemoRequirementsExtension SettingsBoard SettingsBoard-specific settings can be stored in a project's You can also use this for projects you're working from on disk with the intent of running on a specific board. You can also set these at a user level, although that's not the primary intent. If you do this, it will get overridden at the workspace level if you ever touch the choose board dropdown or open a serial monitor. I would have restricted the scope to workspace if that was an option.
Known IssuesLibrary Manager has a issue with unpacking the bundle, this affects the two commands Update All Librearies and Show Available Libraries Use circup at the CLI to do library updates. Release NotesSee the Changelog |