From fd17c3e7eaeaab5a54019418b1f9c7314598ebff Mon Sep 17 00:00:00 2001 From: Max Barnash Date: Wed, 29 Mar 2023 21:54:11 +0100 Subject: [PATCH] Also add note the the f3disco version --- f3discovery/src/05-led-roulette/flash-it.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/f3discovery/src/05-led-roulette/flash-it.md b/f3discovery/src/05-led-roulette/flash-it.md index 31831e411..0b18a832d 100644 --- a/f3discovery/src/05-led-roulette/flash-it.md +++ b/f3discovery/src/05-led-roulette/flash-it.md @@ -97,6 +97,17 @@ gdb-multiarch -q -ex "target remote :3333" target/thumbv7em-none-eabihf/debug/le ``` console gdb -q -ex "target remote :3333" target/thumbv7em-none-eabihf/debug/led-roulette ``` + +> **NOTE**: If you are getting `target/thumbv7em-none-eabihf/debug/led-roulette: No such file or directory` +> error, try adding `../../` to the file path, for example: +> +> ```shell +> $ gdb -q -ex "target remote :3333" ../../target/thumbv7em-none-eabihf/debug/led-roulette +> ``` +> +> This is caused by each example project being in a `workspace` that contains the entire book, and workspaces have +> a single `target` directory. Check out [Workspaces chapter in Rust Book] for more. + ### **Failing case** You can detect a failing case if there is a `warning` or `error` after the `Remote debugging using :3333` line: