You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Installing the |NCS| and other required software and tools.
17
+
#. Preparing the nRF54H20 DK for first use:
37
18
38
-
See :ref:`supported_OS` for more information.
19
+
a. Programming the nRF54H20 DK's Board Information Configuration Registers (BICR) using the provided binary file.
20
+
#. Programming the Secure Domain and System Controller of the nRF54H20 SoC using the provided SoC binaries.
21
+
#. Transitioning the SoC's lifecycle state (LCS) to Root of Trust (RoT).
39
22
40
-
|supported OS|
23
+
#. Programming the :zephyr:code-sample:`sysbuild_hello_world` sample on the DK.
24
+
#. Testing the sample by capturing and reviewing the UART console output.
41
25
42
-
You also need the following:
26
+
.. _ug_nrf54h20_gs_requirements:
43
27
44
-
* `Git`_ or `Git for Windows`_ (on Linux and Mac, or Windows, respectively)
45
-
* `curl`_
46
-
* SEGGER J-Link |jlink_ver| and, on Windows, also the SEGGER USB Driver for J-Link from `SEGGER J-Link`_ |jlink_ver|.
47
-
For information on how to install the USB Driver, see the `nRF Util prerequisites`_ documentation.
48
-
* The latest version of |VSC| for your operating system from the `Visual Studio Code download page`_
49
-
* In |VSC|, the latest version of the `nRF Connect for VS Code Extension Pack`_
50
-
* On Linux, the `nrf-udev`_ module with udev rules required to access USB ports on Nordic Semiconductor devices and program the firmware
28
+
Hardware requirements
29
+
*********************
51
30
52
-
.. _ug_nrf54h20_gs_installing_software:
31
+
To follow this guide, make sure you have all the required hardware:
53
32
54
-
Installing the required software
55
-
********************************
33
+
* nRF54H20 DK version PCA10175 Engineering C - v0.9.0 and later DK revisions in lifecycle state (LCS) ``EMPTY`` (new DKs will always be in LCS ``EMPTY``).
34
+
Check the version number on your DK's sticker to verify its compatibility with the |NCS|.
35
+
* USB-C cable.
56
36
57
-
To work with the nRF54H20 DK, follow the instructions in the next sections to install the required tools.
After installing the |NCS| and its toolchain, you get the :ncs-tool-version:`NRFUTIL_VERSION_WIN10` version of nRF Util core module (``nrfutil``).
50
+
Using the nRF54H20 DK with the |NCS| version |release| also requires the following nRF Util components:
74
51
75
-
Installing nRF Util and its commands
76
-
====================================
52
+
.. _ug_nrf54h20_nrfutil_comm_ver:
77
53
78
-
When you install the |NCS| toolchain as listed above, you get the :ncs-tool-version:`NRFUTIL_VERSION_WIN10` version of nRF Util core module (``nrfutil``).
79
-
Using the nRF54H20 DK with the |NCS| version |release| requires the following:
Install a terminal emulator, such as the `Serial Terminal app`_ (from the nRF Connect for Desktop application) or the nRF Terminal (part of the `nRF Connect for Visual Studio Code`_ extension).
129
104
Both of these terminal emulators start the required :ref:`toolchain environment <using_toolchain_environment>`.
130
105
131
106
.. _ug_nrf54h20_gs_bringup:
132
-
133
-
nRF54H20 DK bring-up
134
-
********************
135
-
136
-
The following sections describe the steps required for the nRF54H20 bring-up.
137
-
138
-
.. note::
139
-
To program the nRF54H20 SoC binaries based on IronSide SE on your nRF54H20 SoC-based device, your device must be in lifecycle state (LCS) ``EMPTY``.
140
-
Devices already provisioned using SUIT-based binaries and in LCS ``RoT`` cannot be transitioned back to LCS ``EMPTY``.
107
+
.. _ug_nrf54h20_gs_bicr:
141
108
142
109
.. rst-class:: numbered-step
143
110
144
111
Programming the BICR
145
-
====================
112
+
********************
146
113
147
114
The Board Information Configuration Registers (BICR) are non-volatile memory (NVM) registers that contain information on how the nRF54H20 SoC must interact with other board elements, including information about power and clock delivery to the SoC.
148
115
To prepare the nRF54H20 DK for first use, you must manually program the values of the BICR using a precompiled BICR binary file (:file:`bicr.hex`).
149
116
150
-
1. Download the `BICR new binary file`_.
117
+
1. Download the `nRF54H20 DK BICR binary file`_.
151
118
#. Connect the nRF54H20 DK to your computer using the **DEBUGGER** port on the DK.
152
119
153
120
.. note::
@@ -161,18 +128,25 @@ To prepare the nRF54H20 DK for first use, you must manually program the values o
To program the nRF54H20 SoC binaries based on IronSide SE on your nRF54H20 SoC-based device, your device must be in lifecycle state (LCS) ``EMPTY``.
140
+
This means that this is likely the first use of your nRF54H20 DK.
141
+
142
+
Devices already provisioned using SUIT-based binaries and in LCS ``RoT`` cannot be transitioned back to LCS ``EMPTY``.
143
+
For more information, see :ref:`abi_compatibility`.
170
144
171
145
After programming the BICR, program the nRF54H20 SoC with the :ref:`nRF54H20 SoC binaries <abi_compatibility>`.
172
146
This bundle contains the precompiled firmware for the :ref:`Secure Domain <ug_nrf54h20_secure_domain>` and :ref:`System Controller <ug_nrf54h20_sys_ctrl>`.
173
147
To program the nRF54H20 SoC binaries to the nRF54H20 DK, do the following:
174
148
175
-
1. Download the `nRF54H20 SoC binaries v22.2.0+14`_, compatible with the nRF54H20 DK v0.9.0 and later revisions.
149
+
1. Download the `nRF54H20 SoC binaries v22.2.0+14`_, compatible with the nRF54H20 DK v0.9.0 and later DK revisions.
176
150
177
151
.. note::
178
152
On MacOS, ensure that the ZIP file is not unpacked automatically upon download.
@@ -184,7 +158,7 @@ To program the nRF54H20 SoC binaries to the nRF54H20 DK, do the following:
184
158
.. rst-class:: numbered-step
185
159
186
160
Transitioning the nRF54H20 SoC to RoT
187
-
=====================================
161
+
*************************************
188
162
189
163
The current nRF54H20 DK comes with its lifecycle state (LCS) set to ``EMPTY``.
190
164
To operate correctly, you must transition its lifecycle state to Root of Trust (``RoT``).
@@ -205,8 +179,10 @@ To transition the LCS to ``RoT``, do the following:
205
179
206
180
.. _ug_nrf54h20_gs_sample:
207
181
208
-
Building and programming the sample
209
-
***********************************
182
+
.. rst-class:: numbered-step
183
+
184
+
Building and programming your first sample to the nRF54H20 DK
The :zephyr:code-sample:`sysbuild_hello_world` sample is a multicore sample running on both the application core (``cpuapp``) and the Peripheral Processor (PPR, ``cpuppr``).
212
188
It uses the ``nrf54h20dk/nrf54h20/cpuapp`` board target.
@@ -227,20 +203,18 @@ If you have multiple Nordic Semiconductor devices, ensure that only the nRF54H20
227
203
228
204
west flash
229
205
230
-
Make sure you have the :ref:`nrfutil device <ug_nrf54h20_install_toolchain>` command installed for ``west flash`` to work with the nRF54H20 DK.
231
206
This command builds and programs the sample automatically on both the application core and the Peripheral Processor (PPR) of the nRF54H20 SoC.
232
207
233
208
.. include:: /includes/nRF54H20_erase_UICR.txt
234
209
235
210
.. _ug_nrf54h20_sample_reading_logs:
236
211
237
-
Reading the logs
238
-
****************
212
+
.. rst-class:: numbered-step
239
213
240
-
With the :zephyr:code-sample:`sysbuild_hello_world` sample programmed, the nRF54H20 DK outputs logs for the application core and the configured remote processor.
241
-
The logs are output over UART.
214
+
Testing your first sample on the nRF54H20 DK
215
+
********************************************
242
216
243
-
To read the logs from the :zephyr:code-sample:`sysbuild_hello_world` sample programmed to the nRF54H20 DK, complete the following steps:
217
+
Now that the :zephyr:code-sample:`sysbuild_hello_world` sample is programmed, verify its operation by capturing the UART logs from both the application core and the peripheral processor:
244
218
245
219
1. Connect to the DK with a terminal emulator (for example, the `Serial Terminal app`_) using the :ref:`default serial port connection settings <test_and_optimize>`.
246
220
#. Press the **Reset** button on the PCB to reset the DK.
0 commit comments