Skip to content

Latest commit

 

History

History
208 lines (115 loc) · 9 KB

wsl.md

File metadata and controls

208 lines (115 loc) · 9 KB
Raw

Using WSL

In this tutorial will show you how to develop your projects based on Visual Studio Code + ESP-IDF extension + Remote - WSL to implement all features of this extension in WSL.

Required tools

you need to install the following tools before starting our projects:

  1. Ubuntu 20.04 on Windows using WSL
  2. Visual Studio Code
  3. usbipd-win

Ubuntu 20.04 on Windows

WSL is present starting from Windows 10 OS, so we can check the WSL list with the powershell command prompt, as below

wsl -l -o

so to install WSL on windows, please type in the following command:

wsl --install --distribution　Ubuntu-20.04

where Ubuntu-20.04 is for your information.

usbipd-win

To access the USB,serial,JTAG devices which are from the local windows, this tools must be installed, else it is impossible to download,monitor and debug on IDF docker image side. the way to install it, it is also same as windows applications, so it will not be described in detail here.

configuration

we still need to do a bit configurations after installing the four tools above:

Ubuntu 20.04 on Windows

the default version of WSL is 1 after installing, it needs to upgrade to version2 and then set it as the default distribution with the following steps:

  1. check the current WSL version

    wsl -l -v

  2. please upgrade to version 2, if not

    wsl --set-version Ubuntu-20.04 2

  3. set the distribution, as below:

    wsl -s Ubuntu 20.04

at last, to check if the commands have taken effect with wsl --status command.

Adding the required linux packages in WSL

Run the following command in WSL for ESP-IDF to work on Linux.

sudo apt-get install git wget flex bison gperf python3-pip python3-venv python3-setuptools cmake ninja-build ccache libffi-dev libssl-dev dfu-util

usbipd

From windows side this tool should be already configured. However usbipd still need to be installed on the WSL, that is, open the WSL from Windows menu and then type in the following the commands separately:

sudo apt install linux-tools-virtual hwdata
sudo update-alternatives --install /usr/local/bin/usbip usbip `ls /usr/lib/linux-tools/*/usbip | tail -n1` 20

If any errors are found, try updating apt-get packages first.

apt-get update

NOTE: IF you are using a container made with the Dockerfile from this extension .devcontainer generated directory (when you create a project using the ESP-IDF: New Project, ESP-IDF: Add docker container configuration or ESP-IDF: Show Examples commands).

with this the local Windows and WSL are all installed. To check usbipd tool is working well on both side, please follow the following steps:

  1. open PowerShell command prompt with administrator right and then type in the command usbipd wsl list:

    as you can see, all USB devices from Windows have been found and not attached sate.

  2. to access the specified device from local Windows on WSL, it needs to bind this device. Open PowerShell command prompt with administrator rights and then type in the command usbipd bind -b <BUSID>:

    Note: this command needs to be used only one time,unless the computer has restarted. 1-1 is the device's bus id I would like to bind.

  3. after binding, please attach the specified device to WSL with usbipd wsl attach --busid 1-1 command in the powershell command prompt.

  1. At last, let us check if it works well on both side and type in dmesg | tail command on WSL side.

    as we can see above, 1-1 device has been attached to ttyACM0, that means WSL can access the 1-1 USB device now.

Visual Studio Code

To develop in WSL, install the Remote - WSL、Remote Development and ESP-IDF extensions, as below:

Practice

After all previous steps have taken effect, the WSL should be ready to use. Here is an example to show you how to utilize these tools.

example project with WSL

Using blink and hello_world projects as examples:

as seen from snapshot above, blink and hello_world example projects have been put in the same folder and we only need to open this folder with vscode:

some readers may see that there is a .devcontainer folder in the example_project folder, which is not included by default; this is generated by using the ESP-IDF extension of Visual Studio Code to create and configure the IDF docker image for container development. Check the docker container tutorial for more information.

Open project in WSL

Start your development by clicking the >< green button at the left bottom of Visual Studio Code and select Open Folder in WSL to start configuring the WSL and open the Blink example project.

at this moment, you can start to use the Blink example project for building, flashing, monitoring, debugging, etc.

Building the project

Here taking the esp32-c3 as an example, users only need to change the target device from esp32 to esp32-c3, as below:

next, start to build the example project, as below:

Flashing to your device

after building, we can use the following ways to download the firmware.

External USB-Serial

Based on the description above, users can follow the instructions usbipd section mentioned. here Silicon Labs CP210x USB to UART Bridge is taken as an example, it has been attached to docker image:

as you can see, this device has attached to ttyUSB0, so idf.port also need to change accordingly.

but, the container doesn't know the configuration has changed yet at this moment.

so users need to reopen the container, that is Reopen Folder Locally and then the new configuration wil be reloaded as well.

at last, click the flash button and start to download the firmware.

Internal USB-serial

Just as the external usb-serial, the only difference is the number attached. where the external usb-serial is ttyUSBx, while the internal usb-serial is ttyACMx.

USB-JTAG

Same as External USB-Serial and Internal USB-serial, but it needs to configure the following extra parameters:

the interface is the same as Internal USB-serial, that is ttyACMx:

debugging

After following USB-JTAG, press F5 to start to debug:

Precautions

  1. When the container is created for the first time, it will prompt that the ESP-IDF extension cannot be activated because it depends on the Microsoft C++ tools extension. You only need to reopen the project in WSL again. This is because the ESP-IDF extension is dependent on the C++ Tools extension being installed first.
  2. If you want to debug on Windows, you need to unplug the USB cable and re-plug in it again, otherwise the corresponding USB port cannot be found in the Windows device manager.