Merge #190

190: README.md: Replace ${PROBE_RUN_CHIP} in code example r=Urhengulas a=bobmcwhirter

The example makes it look like using a literal `${PROBE_RUN_CHIP}` in the `config` is viable, while it seems to not actually be.

Co-authored-by: Bob McWhirter <[email protected]>
Co-authored-by: Johann Hemmann <[email protected]>

README.md

@@ -28,22 +28,26 @@ manager before installing `probe-run`.
 ### 1. Set the Cargo runner
 
 The recommend way to use `probe-run` is to set as the Cargo runner of your application.
-Add this line to your Cargo configuration (`.cargo/config`) file:
+Add this line to your Cargo configuration file (.cargo/config) and adjust ${PROBE_RUN_CHIP} for the particular `--chip` value:
 
 
 ``` toml
 [target.'cfg(all(target_arch = "arm", target_os = "none"))']
 runner = "probe-run --chip ${PROBE_RUN_CHIP}"
 ```
 
-Instead of `${PROBE_RUN_CHIP}` you can write the name of your microcontroller.
 For example, one would use `nRF52840_xxAA` for the nRF52840 microcontroller.
 To list all supported chips run `probe-run --list-chips`.
 
 To support multiple devices, or permit overriding default behavior, you may prefer to set the
 `${PROBE_RUN_CHIP}` environment variable, and set `runner` (or
 `CARGO_TARGET_${TARGET_ARCH}_RUNNER`) to `probe-run`.
 
+``` toml
+[target.'cfg(all(target_arch = "arm", target_os = "none"))']
+runner = "probe-run"
+```
+
 If you have several probes connected, you can specify which one to use by adding
 the --probe option to the `runner` or setting the `${PROBE_RUN_PROBE}` environment
 variable with a value containing either `${VID}:${PID}` or `${VID}:${PID}:${SERIAL}`: