Issue with flashing esp32s3 using probe-rs

[ttzytt]

Not sure if this is the right place to ask, but hopefully someone has encountered this before and knows how to solve it.

When generating the template, the program asks me to select whether to use espflash or probe-rs as the "Flashing, logging, and debugging" tool in the TUI.

If I choose espflash, I will be able to successfully flash the program and see output like this printed on my terminal:

[INFO ] Embassy initialized! (esp_dsp_driver_espflash src/bin/main.rs:42)
[INFO ] Hello world! (esp_dsp_driver_espflash src/bin/main.rs:59)
[INFO ] Hello world! (esp_dsp_driver_espflash src/bin/main.rs:59)
[INFO ] Hello world! (esp_dsp_driver_espflash src/bin/main.rs:59)

However, if I chose probe-rs I'll sometimes see this kind of output when flashing:

    Finished `dev` profile [optimized + debuginfo] target(s) in 0.17s
     Running `probe-rs run --chip=esp32s3 --preverify --always-print-stacktrace --no-location --catch-hardfault --protocol jtag --speed 5000 target\xtensa-esp32s3-none-elf\debug\esp_disp_driver`
    Verifying ✔ 100% [####################] 348.27 KiB @   1.05 MiB/s (took 0s)                  
      Erasing ✔  10% [###-----------------]  64.00 KiB @ 314.56 KiB/s (ETA 0s)                   
Error: An error with the flashing procedure has occurred.                                        

Caused by:
    0: Failed to erase flash sector at address 0x00010000.
    1: The execution of 'erase_sector' failed with code 65536. This might indicate a problem with the flash algorithm.
error: process didn't exit successfully: `probe-rs run --chip=esp32s3 --preverify --always-print-stacktrace --no-location --catch-hardfault --protocol jtag --speed 5000 target\xtensa-esp32s3-none-elf\debug\esp_disp_driver` (exit code: 1)

Running cargo run again won't solve the problem. I've also tried setting the esp32s3 into download mode or erasing the memory using espflash erase-flash and probe-rs erase --chip esp32s3.

Erasing memory with espflash doesn't help with the problem, and doing probe-rs erase will give output like:

Error: Failed to open probe: Failed to open the debug probe.

Caused by:
    0: The debug probe could not be created.
    1: Timeout accessing device descriptor

If I flash the code again using espflash (I assume this will clean up some corrupted memory?), I will be able to flash using probe-rs successfully. However, nothing shows up in my terminal after a long time (the hello world message). After pressing ctrl+c something like this is printed:

Received Ctrl+C, exiting

~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~Exited by user request
 WARN probe_rs_debug::debug_info: No reliable return address is available, so we cannot determine the program counter to unwind the previous frame.
 WARN probe_rs_debug::debug_info: No reliable return address is available, so we cannot determine the program counter to unwind the previous frame.
ERROR probe_rs_debug::debug_info: Other("Stack pointer is too low to unwind")
Core 0
    Frame 0: idle_hook @ 0x4207e682
       C:\Users\ZYT20\.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\esp-rtos-0.2.0\src\task\xtensa.rs:19:18
    Frame 1: esp_rtos::task::arch_specific::idle_entry @ 0x42023e55> @ 0x0000000042023e55        

Core 1
    Frame 0: esp_disp_driver::__main::____embassy_main_task::____embassy_main_task_inner_function::{{closure}}::HEAP @ 0x400003c0> : ERROR : Stack pointer is too low to unwind @ 0x00000000400003c0

I've searched and read relavant issues in the probe-rs repo. The problem seems to be similar, but the potential solutions mentioned, like running with --speed 10000, do not help.

Please let me know if you need additional information. Any help is appreciated.

Thank you!

[bugadani]

This is a probe-rs issue (link to cross-post), but thanks for reporting.