ArduPilot / ArduPilot/ArduRemoteID
WSL2 Support for flashing ESP32-S3
- Dominant language
- C++
- Stars
- 250
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Description
For those working on Windows using WSL 2:
In order to connect a USB device to WSL, follow the instructions from [Microsoft](https://docs.microsoft.com/en-us/windows/wsl/connect-usb). For me, the ESP32 shows up at /dev/ttyACM0 . You can find the location of your device by checking /dev/tty* or with `lsusb` . Instead of running `make upload` inside of the RemoteIDModule dir, you can construct your own command to flash the ESP32
```
~/.arduino15/packages/esp32/hardware/esp32/2.0.3/tools/esptool.py --port /dev/ttyACM0 write_flash 0x0 ArduRemoteID-ESP32S3_DEV.bin
```
Be sure to change the command to match the settings on your system.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by checking how `make upload` works inside the `RemoteIDModule` directory and how the ESP32-S3 flashing command is assembled. Verify the documented WSL2 USB setup with `/dev/ttyACM0` or `lsusb`, then ensure a WSL2 user can flash `ArduRemoteID-ESP32S3_DEV.bin` without relying on an unsupported workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- arduino, cpp, linux
- Domain
- documentation, embedded-iot
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100