probe-rs run test fails on ESP32

[bugadani]

          > do you have a cloneable reproducer for your S2/ESP32 issues? 

❯ cargo install probe-rs --features cli --git https://github.com/probe-rs/probe-rs --rev ddd59fa
❯ git clone https://github.com/SergioGasquez/esp-hal --branch feat/esp32-hil
❯ cd esp-hal/hil-test/
❯ espflash erase-flash
[2024-04-03T10:35:22Z INFO ] Serial port: '/dev/ttyUSB0'
[2024-04-03T10:35:22Z INFO ] Connecting...
[2024-04-03T10:35:23Z INFO ] Using flash stub
[2024-04-03T10:35:24Z WARN ] Setting baud rate higher than 115,200 can cause issues
[2024-04-03T10:35:24Z INFO ] Erasing Flash...
[2024-04-03T10:35:26Z INFO ] Flash has been erased!
❯ CARGO_BUILD_TARGET=xtensa-esp32-none-elf \
            PROBE_RS_CHIP=esp32-3.3v \
            cargo +esp test --features=esp32 --test spi_full_duplex
    Finished test [optimized + debuginfo] target(s) in 0.09s
     Running tests/spi_full_duplex.rs (target/xtensa-esp32-none-elf/debug/deps/spi_full_duplex-872205df03ecc139)
 WARN probe_rs::config::sequences::esp32: Be careful not to reset your ESP32 while connected to the debugger! Depending on the specific device, this may render it temporarily inoperable or permanently damage it.
      Erasing ✔ [00:00:00] [###] 192.00 KiB/192.00 KiB @ 1.36 MiB/s (eta 0s )
  Programming ✔ [00:00:01] [####] 51.54 KiB/51.54 KiB @ 37.73 KiB/s (eta 0s )    Finished in 1.569s
ERROR probe_rs::cmd::run: Failed to attach to RTT, continuing...
Frame 0: <unknown function @ 0x40009a3c> @ 0x40009a3c
Frame 1: <unknown function @ 0x8000f9f7> @ 0x8000f9f7
Error: The target did not respond with test list until timeout.
error: test failed, to rerun pass `--test spi_full_duplex`

Caused by:
  process didn't exit successfully: `probe-rs run /home/sergio/Documents/Espressif/tests/esp-hal/hil-test/target/xtensa-esp32-none-elf/debug/deps/spi_full_duplex-872205df03ecc139` (exit status: 1)
❯ CARGO_BUILD_TARGET=xtensa-esp32-none-elf \
            PROBE_RS_CHIP=esp32-3.3v \
            cargo +esp test --features=esp32 --test uart
   Compiling hil-test v0.0.0 (/home/sergio/Documents/Espressif/tests/esp-hal/hil-test)
    Finished test [optimized + debuginfo] target(s) in 0.47s
     Running tests/uart.rs (target/xtensa-esp32-none-elf/debug/deps/uart-b19a5891e0111a2a)
 WARN probe_rs::config::sequences::esp32: Be careful not to reset your ESP32 while connected to the debugger! Depending on the specific device, this may render it temporarily inoperable or permanently damage it.
      Erasing ✔ [00:00:00] [###] 192.00 KiB/192.00 KiB @ 1.36 MiB/s (eta 0s )
  Programming ✔ [00:00:01] [####] 48.50 KiB/48.50 KiB @ 38.96 KiB/s (eta 0s )    Finished in 1.448s
ERROR probe_rs::cmd::run: Failed to attach to RTT, continuing...
Frame 0: <unknown function @ 0x4000f979> @ 0x4000f979
Frame 1: <unknown function @ 0x80007b5c> @ 0x80007b5c
Error: The target did not respond with test list until timeout.
error: test failed, to rerun pass `--test uart`

Caused by:
  process didn't exit successfully: `probe-rs run /home/sergio/Documents/Espressif/tests/esp-hal/hil-test/target/xtensa-esp32-none-elf/debug/deps/uart-b19a5891e0111a2a` (exit status: 1)

Are you confident that the tests you're running are supposed to pass?

Same tests are running successfully for other targets, and they should be the same in ESP32.

Originally posted by @SergioGasquez in #2292 (comment)

---

Sergio's test case fails for me, although with a different error:

WARN probe_rs::session: Failed to deconfigure device during shutdown: An Xtensa specific error occurred.

Caused by:
    0: Xtensa debug module error
    1: Error while accessing register
    2: Register-specific error
Error: Failed to attach to RTT

Caused by:
    Error attempting to attach to RTT: RTT control block not found in target memory.
    - Make sure RTT is initialized on the target, AND that there are NO target breakpoints before RTT initalization.
    - For VSCode and probe-rs-debugger users, using `halt_after_reset:true` in your `launch.json` file will prevent RTT
    initialization from happening on time.
    - Depending on the target, sleep modes can interfere with RTT.
error: test failed, to rerun pass `--test spi_full_duplex`

Caused by: