diff --git a/src/tooling/debugging/probe-rs.md b/src/tooling/debugging/probe-rs.md
index aaf410b..e712479 100644
--- a/src/tooling/debugging/probe-rs.md
+++ b/src/tooling/debugging/probe-rs.md
@@ -68,14 +68,6 @@ There is a `probe-rs` extension in VS Code, see `probe-rs` [VS Code documentatio
                 {
                     "coreIndex": 0,
                     "programBinary": "target/riscv32imc-unknown-none-elf/debug/${workspaceFolderBasename}", //!MODIFY
-                    "rttEnabled": true,
-                    "rttChannelFormats": [
-                        {
-                            "channelNumber": 0,
-                            "dataFormat": "String",
-                            "showTimestamp": true,
-                        }
-                    ]
                 }
             ]
         },
@@ -89,14 +81,6 @@ There is a `probe-rs` extension in VS Code, see `probe-rs` [VS Code documentatio
                 {
                     "coreIndex": 0,
                     "programBinary": "target/riscv32imc-unknown-none-elf/debug/${workspaceFolderBasename}", //!MODIFY
-                    "rttEnabled": true,
-                    "rttChannelFormats": [
-                        {
-                            "channelNumber": 0,
-                            "dataFormat": "String",
-                            "showTimestamp": true,
-                        }
-                    ]
                 }
             ]
         }
@@ -104,19 +88,10 @@ There is a `probe-rs` extension in VS Code, see `probe-rs` [VS Code documentatio
 }
 ```
 
-> ⚠️ **Note**: The example `launch.json` uses `rtt`, which may require enabling such feature in some crates, like [`esp-println`][esp-println] and [`esp-backtrace`][esp-backtrace]
-> Eg: ESP32-C3 `no_std` project that uses `esp-println` and `esp-backtrace`:
-> ```toml
-> esp-backtrace = { version = "0.9.0", features = ["esp32c3", "panic-handler", "exception-handler", "print-rtt"] }
-> esp-println = { version = "0.7.0", features = ["esp32c3", "rtt"], default-features = flase }
-> ```
-
 The `Launch` configuration will flash the device and start debugging process while `Attach` will start the debugging in the already running application of the device. See VS Code documentation on [differences between launch and attach][vscode-configs] for more details.
 
 
 [probe-rs-vscode]: https://probe.rs/docs/tools/debugger/
-[esp-println]: https://github.com/esp-rs/esp-println
-[esp-backtrace]: https://github.com/esp-rs/esp-backtrace?tab=readme-ov-file#features
 [vscode-configs]: https://code.visualstudio.com/docs/editor/debugging#_launch-versus-attach-configurations
 
 ## `cargo-flash` and `cargo-embed`
diff --git a/src/troubleshooting/espflash.md b/src/troubleshooting/espflash.md
index dab50cd..099507b 100644
--- a/src/troubleshooting/espflash.md
+++ b/src/troubleshooting/espflash.md
@@ -20,13 +20,3 @@ one.
 
 If you want to use `espflash`, you need to specify an appropriate bootloader image using
 `--bootloader`. You can find the bootloader in `target/<your MCU's target folder>/<debug or release depending on your build>/build/esp-idf-sys-*/build/bootloader/bootloader.bin`
-
-### If you are building an `esp-hal` based project
-
-Make sure your HAL ([ESP32](https://docs.rs/esp32-hal/latest/esp32_hal/), [ESP32-C2](https://docs.rs/esp32c2-hal/latest/esp32c2_hal/))
-is configured to the correct crystal frequency. To do this, you must disable the default features
-and enable `xtal-26mhz` (besides the other default features).
-
-When flashing, you need to specify an appropriate bootloader image using `--bootloader`. Currently,
-you will need to build this bootloader using an `esp-idf` based project (Rust or C based should work
-equally, we recommend a project set up with [esp-idf-template](https://github.com/esp-rs/esp-idf-template)).