Anton Sterkhov

I think this is all due to the waiting time for a response? Since in version 2.1.0 everything is ok. Is it possible to somehow increase the time based on...

>Also, mind sharing the devkit that you are using? I have my own board based on the ESP32 Wroom 32 chip

I think it's here ` fn calc_timeout(timeout_per_mb: Duration, size: u32) -> Duration { let mb = size as f64 / 1_000_000.0; std::cmp::max( DEFAULT_TIMEOUT, FLASH_DEFLATE_END_TIMEOUT, Duration::from_millis((timeout_per_mb.as_millis() as f64 * mb) as...

> > I think it's here ` fn calc_timeout(timeout_per_mb: Duration, size: u32) -> Duration { let mb = size as f64 / 1_000_000.0; std::cmp::max( DEFAULT_TIMEOUT, FLASH_DEFLATE_END_TIMEOUT, Duration::from_millis((timeout_per_mb.as_millis() as f64 *...

> > I can’t start logging and I don’t understand why it crashes. > > What do you mean? > > > I think we should set it to 3...

> To be honest, I don't have much information right now and can't reproduce the issue, I would need you to share with me debug logs (`RUST_LOG=debug espflash flash --monitor...

> The [initial sync](https://docs.espressif.com/projects/esptool/en/latest/esp32c3/advanced-topics/serial-protocol.html#initial-synchronisation) might be failing, it tires 5 times (the maximum) and also [bootmode](https://docs.espressif.com/projects/esptool/en/latest/esp32/advanced-topics/boot-mode-selection.html#boot-mode-message) is not right. Few tests: > > * Have you tried using `--no-stub`? `espflash...

> Just to confirm: Have you also tried using `--no-stub`? `espflash flash --monitor target\xtensa-esp32-none-elf\debug\esp32v1 --no-stub` or modifying the custom runner to add that flag. doesn't work either

> Maybe we can try connecting without resetting: Can you try using `-b no-reset`? I tried it on the M5, it didn’t work, but my board, which didn’t require a...

I think there is a reason that it does not load in version 3, on the M5 atom there is an automatic reset and boot pull, but the time is...