embedded-trainings-2020/embedded-workshop-book/src/troubleshoot-cargo-run-error.md

# `cargo run` errors

You may get one of these errors:

- "Access denied (insufficient permissions)" (seen on macOS)
- "USB error while taking control over USB device: Resource busy" (seen on Linux)

``` console
$ cargo run --bin 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)

Caused by:
    USB error while taking control over USB device: Access denied (insufficient permissions)
```

``` console
$ cargo run --bin 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

Caused by:
    USB error while taking control over USB device: Resource busy
```

All of them have the same root issue: You have another instance of the `cargo run` process running.

It is not possible to have two or more instances of `cargo run` running. Terminate the old instance before executing `cargo run`. If you are using VS Code click the garbage icon ("Kill Terminal") on the top right corner of the terminal output window (located on the bottom of the screen).
extend cargo run troubleshooting section with the Linux variant of the error 2020-07-16 12:00:18 +00:00			# `cargo run` errors

			`You may get one of these errors:`

			`- "Access denied (insufficient permissions)" (seen on macOS)`
			`- "USB error while taking control over USB device: Resource busy" (seen on Linux)`

			``` console
			`$ cargo run --bin usb-4`
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. 2020-09-17 00:30:09 +00:00			Running `probe-run target/thumbv7em-none-eabihf/debug/usb-4`
extend cargo run troubleshooting section with the Linux variant of the error 2020-07-16 12:00:18 +00:00			`Error: An error specific to a probe type occured: USB error while taking control over USB device: Access denied (insufficient permissions)`

			`Caused by:`
			`USB error while taking control over USB device: Access denied (insufficient permissions)`
			```

			``` console
			`$ cargo run --bin usb-4`
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. 2020-09-17 00:30:09 +00:00			Running `probe-run target/thumbv7em-none-eabihf/debug/usb-4`
extend cargo run troubleshooting section with the Linux variant of the error 2020-07-16 12:00:18 +00:00			`Error: An error specific to a probe type occured: USB error while taking control over USB device: Resource busy`

			`Caused by:`
			`USB error while taking control over USB device: Resource busy`
			```

			All of them have the same root issue: You have another instance of the `cargo run` process running.

			It is not possible to have two or more instances of `cargo run` running. Terminate the old instance before executing `cargo run`. If you are using VS Code click the garbage icon ("Kill Terminal") on the top right corner of the terminal output window (located on the bottom of the screen).