Skip to content

Commit 282791d

Browse files
minor updates for the LP
1 parent c59f9e3 commit 282791d

3 files changed

Lines changed: 11 additions & 5 deletions

File tree

content/learning-paths/embedded-and-microcontrollers/zephyr_vsworkbench/1_installation.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ When the installation completes, select **Verify Host Tools** to check the versi
7272

7373
Next, download and configure the toolchain by selecting **Import Toolchain** in the Workbench for Zephyr panel. Select the toolchain family (*Zephyr SDK*) and configure the SDK Type by choosing *Minimal* for basic functionality.
7474

75-
Select your desired version (such as v0.17.0 or v0.17.3) and choose the target architectures. For this Learning Path, you only need to select *arm*.
75+
Select your desired version (such as v0.17.4... your version may vary a little) and choose the target architectures. For this Learning Path, you only need to select *arm*.
7676

7777
Specify the parent directory for SDK installation and select **Import** to download and install the SDK.
7878

@@ -85,14 +85,16 @@ Zephyr uses a Git-based workspace manager called West to organize its source cod
8585

8686
In the Workbench for Zephyr panel, select **Initialize Workspace** to set up your project environment. Configure the workspace settings by selecting "Minimal from template" for the source location and using the default path `https://github.com/zephyrproject-rtos/zephyr`.
8787

88-
Choose a target-specific template (such as STM32 or NXP) and select your Zephyr version (such as v3.7.0 or v4.1.0). Specify the directory for your workspace, keeping in mind that initialization takes approximately 10 minutes to complete.
88+
Choose a target-specific template (such as STM32 or NXP) and select your Zephyr version (such as v4.3.0... your version may vary a bit). Specify the directory for your workspace, keeping in mind that initialization takes approximately 10 minutes to complete.
8989

9090
Select **Import** to create and update the workspace.
9191

9292
![Initialize West Workspace #center](images/initialize_workspace.png)
9393

9494
{{% notice Note %}}
95-
The workspace initialization downloads the Zephyr source code and dependencies. This process may take several minutes depending on your internet connection speed.
95+
The workspace initialization downloads the Zephyr source code and dependencies. This process may take several minutes depending on your internet connection speed.
96+
97+
Additionally, the selected revision you select may be a bit different from the one shown above.
9698
{{% /notice %}}
9799

98100
### Verify setup

content/learning-paths/embedded-and-microcontrollers/zephyr_vsworkbench/3_debug.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ The following steps show how to generate and review memory reports:
3131

3232
![Memory Analysis](images/memory_analysis.png)
3333

34-
The RAM Report displays detailed memory allocation information:
34+
The RAM Report displays detailed memory allocation information and should look like this:
3535

3636
```
3737
Path Size % Address Section
@@ -172,7 +172,7 @@ Workbench for Zephyr will automatically detect these tools when they are install
172172

173173
### Install Runners Utilities
174174

175-
To install debug tools for your specific board, go to **Host Tools > Install Debug Tools** in the Zephyr Workbench panel and select the tools applicable to your board.
175+
To install debug tools for your specific board, go to **Host Tools > Install Debug Tools** in the Zephyr Workbench panel and select the tools applicable to your board. You may need to press the refresh symbol to get the latest installation state for the selected/installed runners:
176176

177177
![Debug Runners](images/install_runners.png)
178178

@@ -205,6 +205,10 @@ You can start debugging from Workbench for Zephyr by selecting **Debug**, or fro
205205

206206
![Debug Application](images/debug_app.png)
207207

208+
{{% notice Note %}}
209+
Depending on whether you are running on Windows or a Mac, the selection of the serial monitor port may be different from what is shown above. The above picture shows a serial port from the development board being connected to a Mac.
210+
{{% /notice %}}
211+
208212
### Debug toolbar controls
209213

210214
The debug toolbar provides the following controls for stepping through your code:
215 KB
Loading

0 commit comments

Comments
 (0)