Closed toddmcintire closed 7 months ago
What board are you using? What version of espflash
are you using? What happens if you manually connect after flashing with
espflash monitor`?
What board are you using? What version of
espflash
are you using? What happens if you manually connect after flashing with
espflash monitor`?
Im using the ESP32-C3-DevKit-RUST-1 and my espflash
is version 3.0.0
.
If I plug the board in and run espflash monitor
I get the following output
If I press CTRL + R
I get the broken pipe.
espflash has a additional optional argument --no-stub
. Can you try it out and see if it makes a difference in your case?
espflash has a additional optional argument
--no-stub
. Can you try it out and see if it makes a difference in your case?
Sorry it seems this bug report may have been in error.
Before running espflash
with --no-stub
I tried with just monitor and it spat out an error about Invalid chip id
. To which I just deleted the entire folder and re-generated everything with cargo-generate.
Upon flashing I now get the correct output as seen below.
I do apologize for all confusion created by this issue.
Bug description
To Reproduce
Steps to reproduce the behavior:
CRATE_CC_NO_DEFAULTS=1 cargo build
cargo run
Expected behavior
output along the lines of
I (268) cpu_start: Starting scheduler. Hello, world
Screenshots
Environment
Additional context
I can get the std-training/intro/hardware-check to work but attempting to run the esp-idf-template results in a
Error: × Broken pipe