You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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)
And I get the following:
I had a similar issue with another library recently but I'm guessing it has a different cause: esp-rs/espflash#166
The text was updated successfully, but these errors were encountered: