esp-rs / esp-idf-template

A "Hello, world!" template of a Rust binary crate for the ESP-IDF framework.
372 stars 43 forks source link

Unable to flash "Broken Pipe" m1 mac #206

Closed toddmcintire closed 2 months ago

toddmcintire commented 2 months ago

Bug description

To Reproduce

Steps to reproduce the behavior:

  1. ... build with CRATE_CC_NO_DEFAULTS=1 cargo build
  2. ... run with cargo run

Expected behavior

output along the lines of

I (268) cpu_start: Starting scheduler. Hello, world

Screenshots

Screenshot 2024-04-12 at 11 52 18

Environment

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

Vollbrecht commented 2 months ago

What board are you using? What version of espflash are you using? What happens if you manually connect after flashing withespflash monitor`?

toddmcintire commented 2 months ago

What board are you using? What version of espflash are you using? What happens if you manually connect after flashing withespflash 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

Screenshot 2024-04-15 at 09 43 51

If I press CTRL + R I get the broken pipe.

Screenshot 2024-04-15 at 09 45 35
Vollbrecht commented 2 months ago

espflash has a additional optional argument --no-stub. Can you try it out and see if it makes a difference in your case?

toddmcintire commented 2 months ago

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.

Screenshot 2024-04-15 at 10 38 22

I do apologize for all confusion created by this issue.