Embedded fixups

.vscode/settings.json

@@ -1,5 +1,4 @@
 {
-    "editor.inlayHints.enabled": "offUnlessPressed",
     "files.autoSave": "afterDelay",
     "files.autoSaveDelay": 500,
     "rust-analyzer.linkedProjects": [

book/src/instructions.md

@@ -79,6 +79,12 @@ More info:
 - <https://rust-analyzer.github.io/>
 - <https://code.visualstudio.com/learn/collaboration/live-share>
 
+### Tip
+
+This repo contains quite a lot of rust projects and due to the complicated setup of the repo Rust Analyzer can't autodiscover them well.
+
+To fix this we've specified the projects manually in the `.vscode/settings.json` file. To reduce the burden on your computer, you can comment out any of the projects that we're not using in our training.
+
 ## Git
 During the trainings, you'll need the Git version control tool.
 If you haven't installed Git already, you can find instructions here: <https://git-scm.com/book/en/v2/Getting-Started-Installing-Git>.
@@ -121,7 +127,7 @@ You can view variable values by hovering over them while execution is paused, or
 *This part is relevant only if you're partaking in one of the workshops on embedded Rust.*
 
 ## Hardware
-You should have a [BBC micro:bit](https://microbit.org/buy/bbc-microbit-single/ V2) available.
+We will use the [BBC micro:bit](https://microbit.org/buy/bbc-microbit-single/ V2) and either you've already got it or we will bring it with us.
 
 You'll also need a Micro-USB cable, but we're sure you've got one to spare.
 
@@ -154,10 +160,10 @@ sudo udevadm control --reload-rules
 sudo udevadm trigger
 ```
 
-If you're on `windows`, we need to install a generic WinUSB driver. You can use [Zadig](https://zadig.akeo.ie/) to select the usb device that uses the jlink driver and install WinUSB on it. 
-*This will uninstall the official driver, which means that the official Segger tools will not work anymore after this.* To revert, go to `device manager` and uninstall the usb device. The jlink driver will then be used again for that usb connection.
-
-Then, unplug the USB cable and plug it in again.
+It's possible that probe-rs detects two debugging interfaces. This is known to happen on Windows.
+In that case, go to the `.cargo/config.toml` and change the runner to the one that specifies the exact probe
+it needs to use. Make sure the values are the same as what probe-rs reports is one of the interfaces.
+Unsure? You can run `probe-rs list` to get a list of all connected probes.
 
 ## Trying it out
 Before we begin, we need to test our hardware. We'll be testing the nRF52833 microcontroller and the LSM303AGR motion sensor, that are present on the micro:bit V2. Make sure you have checked out the latest version of the workshop source.

exercises/1-course-introduction/1-introduction/2-embedded/.cargo/config.toml

@@ -1,5 +1,7 @@
 [target.'cfg(all(target_arch = "arm", target_os = "none"))']
-runner = "probe-rs run --chip nRF52833_xxAA --catch-reset --catch-hardfault --allow-erase-all"
+# runner = "probe-rs run --chip nRF52833_xxAA --catch-reset --catch-hardfault --allow-erase-all"
+runner = "probe-rs run --chip nRF52833_xxAA --catch-reset --catch-hardfault --allow-erase-all --probe 0d28:0204:990636020005282085E7C008F3731B68000000006E052820"
+
 rustflags = [
   "-C", "link-arg=-Tlink.x",
   # This is needed if your flash or ram addresses are not aligned to 0x10000 in memory.x

exercises/1-course-introduction/1-introduction/2-embedded/Cargo.toml

@@ -7,9 +7,9 @@ edition = "2021"
 cortex-m = { version = "0.7.7", features = ["critical-section-single-core"] }
 cortex-m-rt = "0.7.3"
 panic-probe = { version = "0.3.0", features = ["print-rtt"] }
-embedded-hal = "0.2.7"
+embedded-hal = "1.0.0"
 rtt-target = "0.5.0"
-lsm303agr = "1.0.0"
+lsm303agr = "1.1.0"
 
 [dependencies.nrf52833-hal]
 version = "0.18.0"

exercises/8-embedded/1-embedded-ecosystem/1-lsm303agr-id/.cargo/config.toml

@@ -1,5 +1,6 @@
 [target.'cfg(all(target_arch = "arm", target_os = "none"))']
 runner = "probe-rs run --chip nRF52833_xxAA --catch-reset --catch-hardfault --allow-erase-all"
+# runner = "probe-rs run --chip nRF52833_xxAA --catch-reset --catch-hardfault --allow-erase-all --probe 0d28:0204:990636020005282085E7C008F3731B68000000006E052820"
 
 rustflags = [
   "-C", "link-arg=-Tlink.x",

exercises/8-embedded/1-embedded-ecosystem/1-lsm303agr-id/Cargo.toml

@@ -10,7 +10,7 @@ cortex-m = { version = "0.7.7", features = ["critical-section-single-core"] }
 cortex-m-rt = "0.7.3"
 rtt-target = "0.5.0"
 embedded-hal = "1.0.0"
-embassy-nrf = { version = "0.1.0", features = ["nrf52833", "unstable-pac"] }
+embassy-nrf = { version = "0.2.0", features = ["nrf52833", "unstable-pac"] }
 
 [profile.release]
 debug = true

exercises/8-embedded/2-portable-drivers/1-lsm303agr-driver/.cargo/config.toml

@@ -1,5 +1,6 @@
 [target.'cfg(all(target_arch = "arm", target_os = "none"))']
 runner = "probe-rs run --chip nRF52833_xxAA --catch-reset --catch-hardfault --allow-erase-all"
+# runner = "probe-rs run --chip nRF52833_xxAA --catch-reset --catch-hardfault --allow-erase-all --probe 0d28:0204:990636020005282085E7C008F3731B68000000006E052820"
 
 rustflags = [
   "-C", "link-arg=-Tlink.x",