Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a note regarding target dir location #520

Merged
merged 2 commits into from
Mar 30, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions f3discovery/src/05-led-roulette/flash-it.md
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
12 changes: 12 additions & 0 deletions microbit/src/05-led-roulette/debug-it.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,18 @@ $ gdb target/thumbv6m-none-eabi/debug/led-roulette

[chapter 3]: ../03-setup/index.md#tools

> **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 ../../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.

[Workspaces chapter in Rust Book]: https://doc.rust-lang.org/book/ch14-03-cargo-workspaces.html#creating-a-workspace

> **NOTE**: If `cargo-embed` prints a lot of warnings here don't worry about it. As of now it does not fully
> implement the GDB protocol and thus might not recognize all the commands your GDB is sending to it,
> as long as it does not crash, you are fine.
Expand Down