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
$ cargo run --example blinky --release
Compiling esp32c3-hal v0.14.0 (…/esp-hal/esp32c3-hal)
Finished release [optimized + debuginfo] target(s) in 0.22s
Running `probe-rs run --chip esp32c3 target/riscv32imc-unknown-none-elf/release/examples/blinky`
Erasing ⠁ [00:00:00] [-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 0 B/ 0 B @ 0 B/s (eta 0s )Error: The flashing procedure failed for 'target/riscv32imc-unknown-none-elf/release/examples/blinky'.
Caused by:
0: Something during the interaction with the core went wrong
1: An error with the usage of the probe occurred
2: USB Communication Error
3: Operation timed out
The same setup is working as expected with runner = "espflash flash --monitor".
Am I missing anything ? Or is there a bug somewhere ? Should I report this in probe-rs instead ?
Additionnal info
dmesg
[ 2087.030094] usb 1-6.4.4.2: new full-speed USB device number 39 using xhci_hcd
[ 2087.154933] usb 1-6.4.4.2: New USB device found, idVendor=303a, idProduct=1001, bcdDevice= 1.01
[ 2087.154948] usb 1-6.4.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2087.154955] usb 1-6.4.4.2: Product: USB JTAG/serial debug unit
[ 2087.154960] usb 1-6.4.4.2: Manufacturer: Espressif
[ 2087.154965] usb 1-6.4.4.2: SerialNumber: 60:55:F9:BC:45:2C
[ 2087.168153] cdc_acm 1-6.4.4.2:1.0: ttyACM0: USB ACM device
probe-rs list
The following debug probes were found:
[0]: ESP JTAG (VID: 303a, PID: 1001, Serial: 60:55:F9:BC:45:2C, EspJtag)
probe-rs info
Probing target via JTAG
No DAP interface was found on the connected probe. Thus, ARM info cannot be printed.
RISC-V Chip:
IDCODE: 0000005c25
Version: 0
Part: 5
Manufacturer: 1554 (Espressif Systems (Shanghai) Co Ltd)
Probing target via SWD
Error identifying target using protocol SWD: Probe does not support SWD
The text was updated successfully, but these errors were encountered:
Hi,
On the current main branch, with an esp32-c3-devkit-RUST-1 v1.2a, and probe-rs 0.22.0 (with
--features cli,ftdi
) setup according to the docs:I get:
The same setup is working as expected with
runner = "espflash flash --monitor"
.Am I missing anything ? Or is there a bug somewhere ? Should I report this in probe-rs instead ?
Additionnal info
dmesg
probe-rs list
probe-rs info
The text was updated successfully, but these errors were encountered: