Merge branch 'master' into patch-1

Author: Yatekii

.github/workflows/deploy-preview.yml

@@ -20,7 +20,7 @@ jobs:
 
     steps:
       - name: Clone repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
         with:
           ref: ${{ github.event.pull_request.head.sha }}
 

.github/workflows/deploy.yml

@@ -23,7 +23,7 @@ jobs:
 
     steps:
       - name: Clone repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       - name: Install & build with Astro
         uses: withastro/action@v4

.github/workflows/update-probe-rs-dep.yml

@@ -10,10 +10,10 @@ jobs:
   update:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
         with:
           token: ${{ secrets.PAT }}
-      - uses: actions/setup-node@v4
+      - uses: actions/setup-node@v6
         with:
           node-version: 23
       - run: npm update probe-rs-targets

package-lock.json

@@ -14,7 +14,7 @@
     "@astrojs/rss": "^4.0.11",
     "@astrojs/sitemap": "^3.2.1",
     "@tailwindcss/vite": "^4.0.12",
-    "astro": "^5.4.2",
+    "astro": "^5.14.4",
     "astro-expressive-code": "^0.40.2",
     "astro-icon": "^1.1.5",
     "astro-pagefind": "^1.8.3",

package.json

@@ -4,7 +4,8 @@ import { useEffect, useState } from "preact/hooks";
 
 type Props = {};
 
-const shell = `curl -LsSf https://github.com/probe-rs/probe-rs/releases/latest/download/probe-rs-tools-installer.sh | sh`;
+const latestBase = `https://github.com/probe-rs/probe-rs/releases/latest/download`;
+const shell = `curl -LsSf ${latestBase}/probe-rs-tools-installer.sh | sh`;
 
 export default function TargetsView({}: Props) {
   const [instructions, setInstructions] = useState([shell, "shell"] as [
@@ -47,7 +48,7 @@ export function installInstructions(): [string, BundledLanguage] {
     return [shell, "shell"];
   } else if (windowsPlatforms.indexOf(platform) !== -1) {
     return [
-      `powershell -ExecutionPolicy Bypass -c "irm https://github.com/probe-rs/probe-rs/releases/download/v0.27.0/probe-rs-tools-installer.ps1 | iex"`,
+      `powershell -ExecutionPolicy Bypass -c "irm ${latestBase}/probe-rs-tools-installer.ps1 | iex"`,
       "powershell",
     ];
   } else if (/Android/.test(userAgent)) {

src/components/index/Install.tsx

@@ -59,7 +59,7 @@ No additional setup is required.
 
 #### Windows
 
-Download and install [`cmake`](https://cmake.org/download/). Make sure it's added to your `$PATH`.
+No additional setup is required.
 
 ### Installation
 

src/content/docs/getting-started/installation.mdx

@@ -24,7 +24,14 @@ users without root privileges access to the debug probes as well.
    devices.
 
 If you're still unable to access the debug probes after following these steps,
-try adding your user to the plugdev group.
+try adding your user to the plugdev group. This group needs to be a system group
+if you use systemd version higher than v258. In this case you can try the following
+commands to fix the udev rules :
+
+```bash
+sudo groupadd --system plugdev
+sudo usermod -a -G plugdev $USER
+```
 
 [^1]: The file needs to have an initial number lower than 73, otherwise the udev
 rules do not get applied properly. See
@@ -200,6 +207,7 @@ recommended to configure udev as described in [udev rules](#linux-udev-rules).
 
 No driver installation required.
 
+Some ESP32 devices have an incorrect WinUSB Descriptor. If ``probe-rs list`` shows your device, but ``probe-rs info`` fails with ``Could not find DeviceInterfaceGUIDs in registry``, you may need to reinstall the driver using Zadig. You can find more information in this GitHub discussion: https://github.com/probe-rs/probe-rs/discussions/3193
 
 ## [Glasgow Interface Explorer](https://glasgow-embedded.org/)
 

src/content/docs/getting-started/probe-setup.mdx

@@ -29,6 +29,7 @@ let probe = probes[0].open()?;
 Now you can access all the functionality a probe can offer. Not all probes offer the same functionality, which is why some calls may return a negative `Result`.
 
 ```rs
+
 // Perform a hard reset of the connected target via the probe.
 probe.target_reset()?;
 
@@ -67,7 +68,7 @@ In the previous sections we have learned how we attach to a core.
 Sometimes you want to access the core operations in quick fashion.
 This is what [Session::auto_attach()](https://docs.rs/probe-rs/*/probe_rs/struct.Session.html#method.auto_attach) is for.
 It lets you attach to the Core without first opening a Probe.
-It will try to open a connected prbe, and select the Core as best as it can
+It will try to open a connected probe, and select the Core as best as it can
 
 ```rs
 let session = Session::auto_attach("chip_name")?;

src/content/docs/library/basics.mdx

@@ -21,7 +21,7 @@ And there is much more to come in the future!
 You can use it like any cargo command would be used
 
 ```bash
-cargo embed <args>
+cargo embed [OPTIONS] [CONFIG_PROFILE]
 ```
 
 This will do following in sequence:
@@ -73,10 +73,10 @@ precedence.
 
 The data in the `Embed.toml` is structured in two levels: The outer layer is a
 configuration profile name, inside each profile there are then a series of
-sections with different options. The default profile is called "default" ;) When
-invoking cargo-embed, a different profile name can be passed as an argument with
-`--config <profile>`, which will load the settings under that profile instead of
-`default`.
+sections with different options. The default profile is called "default" ;)
+When invoking cargo-embed, a different profile name can be passed as positional
+argument `CONFIG_PROFILE`, which will load the settings under that profile
+instead of `default` (see [Usage](#usage)).
 
 For example, in your `Embed.toml`:
 
@@ -92,8 +92,8 @@ chip = "STM32F401CCUx"
 enabled = true
 ```
 
-Now you can run `cargo embed --config with_rtt` to have RTT enabled, while
-`cargo embed` will use the default config "default" without RTT.
+Now you can run `cargo embed with_rtt` to have RTT enabled, while `cargo embed`
+will use the default config "default" without RTT.
 
 ## RTT