Skip to content

Commit d79f4e7

Browse files
committed
doc: wayland: update for the extension release
Updated documentation pages for the latest changes to the extension. VSC-2735, VSC-2760, VSC-2340. Signed-off-by: Grzegorz Ferenc <Grzegorz.Ferenc@nordicsemi.no>
1 parent 9b0cd12 commit d79f4e7

File tree

3 files changed

+19
-12
lines changed

3 files changed

+19
-12
lines changed

doc/nrf/app_dev/create_application.rst

+5-4
Original file line numberDiff line numberDiff line change
@@ -171,17 +171,18 @@ Use the following steps depending on the application placement:
171171
The application creation process starts after you enter the name.
172172
When the application is created, a VS Code prompt appears asking you what to do with the application.
173173
#. Click :guilabel:`Open`.
174-
This opens the new application and adds it to the :guilabel:`Applications View` in the extension.
174+
This will open the new application and adds it to the :guilabel:`Applications View` in the extension.
175175
At this point, you have created a freestanding application.
176176
#. Add the :file:`west.yml` to create a west workspace around the application:
177177

178178
a. In the :guilabel:`Welcome View`, click the :guilabel:`Manage SDKs` action.
179179
A quick pick menu appears.
180-
#. Click :guilabel:`Create west workspace`.
180+
#. Click :guilabel:`Manage West Workspace...`.
181+
#. In the :guilabel:`Manage West Workspace...` action menu, click :guilabel:`Create West Workspace`.
181182
#. Enter a location for the :file:`west.yml` file that matches the location provided in step 4.
182183
#. Select the SDK version for the west workspace.
183-
The west workspace is initialized and the :guilabel:`Manage SDKs` action changes to :guilabel:`Manage west workspace`.
184-
#. Click :guilabel:`Manage west workspace` and select :guilabel:`West Update` button to update the workspace modules.
184+
The west workspace is initialized.
185+
#. Click :guilabel:`Manage SDKs` > :guilabel:`Manage West Workspace` > :guilabel:`West Update` to update the workspace modules.
185186

186187
You can now start :ref:`configuring and building <configuration_and_build>` the application.
187188

doc/nrf/installation/install_ncs.rst

+13-7
Original file line numberDiff line numberDiff line change
@@ -105,8 +105,12 @@ Depending on your preferred development environment, complete the following step
105105
The list of available stable toolchain versions appears in the |VSC|'s quick pick.
106106
#. Select the toolchain version to install.
107107
The toolchain version should match the |NCS| version you are going to work with.
108-
If you have received a custom URL for installing the toolchain, you can provide it using the :guilabel:`Change Toolchain Index` button in the quick pick's header (wrench icon).
109-
If you are working with a development tag, disable the filter in the quick pick's header to list all available toolchains.
108+
|install_latest_version|
109+
110+
.. note::
111+
If you have received a custom URL for installing the toolchain, you can provide it using the :guilabel:`Change Toolchain Index` button in the quick pick's header (wrench icon).
112+
If you are working with a development tag, disable the filter in the quick pick's header to list all available toolchains.
113+
110114
The toolchain installation starts in the background, as can be seen in the notification that appears.
111115

112116
When you install the toolchain for the first time, the installed version is automatically selected for your project.
@@ -138,14 +142,17 @@ Depending on your preferred development environment, complete the following step
138142
139143
For example:
140144

141-
.. code-block:: console
145+
.. parsed-literal::
146+
:class: highlight
142147
143-
nrfutil toolchain-manager install --ncs-version v2.0.0
148+
nrfutil toolchain-manager install --ncs-version |release|
144149
145-
This example command installs the toolchain required for the |NCS| v2.0.0.
150+
This example command installs the toolchain required for the |NCS| |release|.
151+
|install_latest_version|
146152

147153
The ``toolchain-manager`` command installs the toolchain by default at :file:`C:/ncs/toolchains` on Windows and at :file:`~/ncs/toolchains` on Linux.
148154
These can be modified, as explained in the `Toolchain Manager command`_ documentation.
155+
To check the current configuration setting, use the ``nrfutil toolchain-manager config --show`` command.
149156
On macOS, :file:`/opt/nordic/ncs/toolchains` is used and no other location is allowed.
150157

151158
If you have received a custom URL for installing the toolchain, you can use the following command to set it as default, replacing the respective parameter:
@@ -162,8 +169,7 @@ Depending on your preferred development environment, complete the following step
162169
163170
nrfutil toolchain-manager install --bundle-id *custom_bundle_ID*
164171
165-
To check the current configuration setting, use the ``nrfutil toolchain-manager config --show`` command.
166-
To read more about these commands, use the ``nrfutil toolchain-manager --help`` command.
172+
To read more about ``toolchain-manager`` commands, use the ``nrfutil toolchain-manager --help`` command.
167173

168174
With the default location to install the toolchain (:file:`C:/ncs/toolchains` on Windows, :file:`~/ncs/toolchains/` on Linux, and the non-modifiable :file:`/opt/nordic/ncs/toolchains/` on macOS), your directory structure now looks similar to this:
169175

doc/nrf/test_and_optimize/debugging.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,7 @@ Use the following steps to enable monitor-mode debugging in the |NCS|:
128128
2. Attach the debugger to the application.
129129
3. Depending on debugger you are using, enable monitor-mode debugging:
130130

131-
* For nRF Debug in the |nRFVSC|, enter ``-exec monitor exec SetMonModeDebug=1`` in the debug console.
131+
* For nRF Debug in the |nRFVSC|, the monitor-mode is automatically enabled when you set the :kconfig:option:`CONFIG_SEGGER_DEBUGMON` Kconfig option and build your application (``-exec monitor exec SetMonModeDebug=1`` is automatically passed to the debug console).
132132
* For debugging using Ozone, enter ``Exec.Command("SetMonModeDebug = 1");`` in the console.
133133

134134
For more information about monitor-mode debugging, see Zephyr's :ref:`zephyr:debugmon` documentation and SEGGER's `Monitor-mode Debugging <Monitor-mode Debugging_>`_ documentation.

0 commit comments

Comments
 (0)