Use probe-rs instead of deprecated probe-run (#353)

Author: Sh3Rm4n

.cargo/config.toml

@@ -10,7 +10,7 @@
 [target.thumbv7em-none-eabihf]
 # runner = "arm-none-eabi-gdb"
 # Chip can be set via `--chip STM32F303VCTx` or `export PROBE_RUN_CHIP=STM32F303VCTx`
-runner = "probe-run --chip STM32F303VCTx --connect-under-reset"
+runner = "probe-rs run --chip STM32F303VCTx --connect-under-reset"
 rustflags = [
   "-C", "link-arg=--nmagic",
   "-C", "link-arg=-Tlink.x",

testsuite/README.md

@@ -4,7 +4,11 @@
 
 Tests are run via the integration test pattern and are executed on a target
 chip, rather than on a host system. First, install
-[probe-run](https://crates.io/crates/probe-run) via `cargo install probe-run`.
+[probe-rs](https://crates.io/crates/probe-rs) via
+
+```sh
+cargo install probe-rs --features cli
+```
 
 Currently the tests are written for the `stm32f303xc` with the STM32F3Discovery
 Board in mind. They expect that several pins are wired together as hinted in