Update cross compilation target

Use the target actually mentioned in the .cargo/config file.

Updated the output in the troubleshooting page and
also updated the target for the board/dongle.
This commit is contained in:
Dave Hylands 2020-09-16 17:30:09 -07:00
parent 6b722bd1bf
commit 172dbc17cd
3 changed files with 5 additions and 5 deletions

View file

@ -1,8 +1,8 @@
[target.thumbv7em-none-eabi] [target.thumbv7em-none-eabihf]
runner = "dongle-flash" runner = "dongle-flash"
rustflags = [ rustflags = [
"-C", "link-arg=-Tlink.x", "-C", "link-arg=-Tlink.x",
] ]
[build] [build]
target = "thumbv7em-none-eabi" target = "thumbv7em-none-eabihf"

View file

@ -114,7 +114,7 @@ Go to [https://rustup.rs](https://rustup.rs/) and follow the instructions.
**All**: Run this command in a terminal: **All**: Run this command in a terminal:
``` console ``` console
$ rustup +stable target add thumbv7em-none-eabi $ rustup +stable target add thumbv7em-none-eabihf
``` ```
### ELF analysis tools ### ELF analysis tools

View file

@ -7,7 +7,7 @@ You may get one of these errors:
``` console ``` console
$ cargo run --bin usb-4 $ cargo run --bin usb-4
Running `probe-run target/thumbv7em-none-eabi/debug/usb-4` Running `probe-run target/thumbv7em-none-eabihf/debug/usb-4`
Error: An error specific to a probe type occured: USB error while taking control over USB device: Access denied (insufficient permissions) Error: An error specific to a probe type occured: USB error while taking control over USB device: Access denied (insufficient permissions)
Caused by: Caused by:
@ -16,7 +16,7 @@ Caused by:
``` console ``` console
$ cargo run --bin usb-4 $ cargo run --bin usb-4
Running `probe-run target/thumbv7em-none-eabi/debug/usb-4` Running `probe-run target/thumbv7em-none-eabihf/debug/usb-4`
Error: An error specific to a probe type occured: USB error while taking control over USB device: Resource busy Error: An error specific to a probe type occured: USB error while taking control over USB device: Resource busy
Caused by: Caused by: