MicroESP: The VS Code Extension for MicroPython MicroESP is a powerful Visual Studio Code extension designed to streamline your development workflow with MicroPython on ESP32 boards. With MicroESP, you can easily write, upload, and run your Python code on a connected board, all from within the familiar VS Code environment. Features Seamless Workflow Run: With a single click, upload the active file to your board and run it instantly. All print statements and output from your script will be streamed directly to a dedicated output panel in VS Code. Getting Started Prerequisites Python: Ensure you have Python 3 installed on your system. pip: Verify that pip is installed and up to date. mpremote: Install the mpremote tool, a command-line utility for interacting with MicroPython devices. To install mpremote, open your terminal and run the following command: pip install mpremote Installation Open Visual Studio Code. Go to the Extensions view by clicking the square icon on the side bar or pressing Ctrl+Shift+X. Search for "MicroESP". Click the Install button. Usage
Click the ▶️ Run button located in the VS Code status bar at the bottom left. The extension will: Automatically find your connected ESP32 board. If a script is already running, clicking Run again will automatically stop the old script, upload the new one, and start it for you. Upload the active .py file to the board. Execute the file on the board. Stream all output from the board to the ESP MicroPython output channel. Troubleshooting "No ESP board found.": Ensure your board is properly connected via a USB cable. Check that the necessary drivers for your board's USB-to-serial chip are installed. For ESP32 boards, this is often the CP210x or CH340G driver. Verify that mpremote is correctly installed and accessible from your terminal. "Access denied": This error occurs when another process (like a serial monitor or another instance of mpremote) is already using the serial port. Close any other applications that might be connected to the board (e.g., PuTTY, Thonny). If the error persists, try unplugging and replugging your board.1 Best regards, Arman Fouladfar from Hafnium |