Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Board attached to WSL 2 using usbipd is not detected #47

Open
KorvinSzanto opened this issue May 18, 2022 · 0 comments
Open

Board attached to WSL 2 using usbipd is not detected #47

KorvinSzanto opened this issue May 18, 2022 · 0 comments

Comments

@KorvinSzanto
Copy link

I'm using an adafruit samd qt py in bootloader mode (I'm sure because when I attach it to windows it mounts and expects a uf2 file)

% lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 018: ID 239a:00cb Adafruit Industries QT Py M0
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

And I get the following:

% RUST_BACKTRACE=1 RUST_LOG=debug cargo hf2 --example neopixel --release --pid 0x00cb --vid 0x239a
 DEBUG cargo_project > Project::query(path=/home/korvin/projects/micro/atsamd/boards/qt_py_m0): root=/home/korvin/projects/micro/atsamd/boards/qt_py_m0
 DEBUG cargo_project > workspace search: cwd=/home/korvin/projects/micro/atsamd/boards
    Finished release [optimized] target(s) in 0.01s
thread 'main' panicked at 'Are you sure device is plugged in and in bootloader mode?: HidApiError { message: "hid_error is not implemented yet" }', /home/korvin/.cargo/registry/src/github.com-1ecc6299db9ec823/cargo-hf2-0.3.3/src/main.rs:77:14
stack backtrace:
   0: rust_begin_unwind
             at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
             at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/panicking.rs:143:14
   2: core::result::unwrap_failed
             at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/result.rs:1749:5
   3: cargo_hf2::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

I had a similar issue with another library recently but I'm guessing it has a different cause: esp-rs/espflash#166

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant