@@ -210,87 +210,90 @@ environment is recommended to avoid interfering with your system Python.
210
210
Install the Zephyr Software Development Kit (SDK)
211
211
*************************************************
212
212
213
- Use of the Zephyr SDK is optional, but recommended. Some of the dependencies
214
- installed above are only needed for installing the SDK.
213
+ The Zephyr Software Development Kit (SDK) contains toolchains for each of
214
+ Zephyr's supported architectures. It also includes additional host tools, such
215
+ as custom QEMU and OpenOCD.
215
216
216
- Zephyr's :abbr: `SDK ( Software Development Kit ) ` contains all necessary tools to
217
- build Zephyr on all supported architectures. Additionally, it includes host
218
- tools such as custom QEMU binaries and a host compiler. The SDK supports the
219
- following target architectures:
217
+ Use of the Zephyr SDK is highly recommended and may even be required under
218
+ certain conditions (for example, running tests in QEMU for some architectures).
220
219
221
- * :abbr: ` X86 ( Intel Architecture 32 bits ) `
220
+ The Zephyr SDK supports the following target architectures:
222
221
223
- * :abbr: `Arm ( Advanced RISC Machine ) `
222
+ * ARC (32-bit and 64-bit; ARCv1, ARCv2, ARCv3)
223
+ * ARM (32-bit and 64-bit; ARMv6, ARMv7, ARMv8; A/R/M Profiles)
224
+ * MIPS (32-bit and 64-bit)
225
+ * Nios II
226
+ * RISC-V (32-bit and 64-bit; RV32I, RV32E, RV64I)
227
+ * x86 (32-bit and 64-bit)
228
+ * Xtensa
224
229
225
- * :abbr: `ARC ( Argonaut RISC Core ) `
226
-
227
- * :abbr: `MIPS ( Microprocessor without Interlocked Pipeline Stages ) `
228
-
229
- * :abbr: `Nios II `
230
+ Follow these steps to install the Zephyr SDK:
230
231
231
- * :abbr: `RISC-V `
232
+ #. Download and verify the `latest Zephyr SDK bundle
233
+ <https://github.com/zephyrproject-rtos/sdk-ng/releases> `_:
232
234
233
- * :abbr: ` SPARC `
235
+ .. code-block :: bash
234
236
235
- * :abbr: `Xtensa `
237
+ wget https://github.com/zephyrproject-rtos/sdk-ng/releases/download/v0.14.0/zephyr-sdk-0.14.0_linux-x86_64.tar.gz
238
+ wget -O - https://github.com/zephyrproject-rtos/sdk-ng/releases/download/v0.14.0/sha256.sum | shasum --check --ignore-missing
236
239
237
- Follow these steps to install the Zephyr SDK:
240
+ You can change ``0.14.0 `` to another version if needed; the `Zephyr SDK
241
+ Releases `_ page contains all available SDK releases.
238
242
239
- #. Download the `latest SDK
240
- <https://github.com/zephyrproject-rtos/sdk-ng/releases> `_ as a
241
- self-extracting installation binary:
243
+ If your host architecture is 64-bit ARM (for example, Raspberry Pi), replace
244
+ ``x86_64 `` with ``aarch64 `` in order to download the 64-bit ARM Linux SDK.
242
245
243
- .. code-block :: console
246
+ #. Extract the Zephyr SDK bundle archive:
244
247
245
- wget https://github.com/zephyrproject-rtos/sdk-ng/releases/download/v0.13.2/zephyr-sdk-0.13.2-linux-x86_64-setup.run
248
+ .. code-block :: bash
246
249
247
- (You can change * 0.13.2 * to another version if needed; the ` Zephyr
248
- Downloads `_ page contains all available SDK releases.)
250
+ cd < sdk download directory >
251
+ tar xvf zephyr-sdk-0.14.0_linux-x86_64.tar.gz
249
252
250
- #. Run the installation binary, installing the SDK at
251
- :file: `~/zephyr-sdk-0.13.2 `:
253
+ #. Run the Zephyr SDK bundle setup script:
252
254
253
- .. code-block :: console
255
+ .. code-block :: bash
254
256
255
- cd <sdk download directory>
256
- chmod +x zephyr-sdk-0.13.2-linux-x86_64-setup.run
257
- ./zephyr-sdk-0.13.2-linux-x86_64-setup.run -- -d ~/zephyr-sdk-0.13.2
257
+ cd zephyr-sdk-0.14.0
258
+ ./setup.sh
258
259
259
- You can pick another directory if you want. If this fails, make sure
260
- Zephyr's dependencies were installed as described in `Install Requirements
261
- and Dependencies `_.
260
+ If this fails, make sure Zephyr's dependencies were installed as described
261
+ in `Install Requirements and Dependencies `_.
262
262
263
- If you ever want to uninstall the SDK, just remove the directory where you
264
- installed it .
263
+ If you want to uninstall the SDK, remove the directory where you installed it.
264
+ If you relocate the SDK directory, you need to re-run the setup script .
265
265
266
266
.. note ::
267
- It is recommended to install the Zephyr SDK at one of the following locations:
267
+ It is recommended to extract the Zephyr SDK bundle at one of the following locations:
268
268
269
- * ``$HOME/zephyr-sdk[-x.y.z] ``
270
- * ``$HOME/.local/zephyr-sdk[-x.y.z] ``
271
- * ``$HOME/.local/opt/zephyr-sdk[-x.y.z] ``
272
- * ``$HOME/bin/zephyr-sdk[-x.y.z] ``
273
- * ``/opt/zephyr-sdk[-x.y.z] ``
274
- * ``/usr/zephyr-sdk[-x.y.z] ``
275
- * ``/usr/local/zephyr-sdk[-x.y.z] ``
269
+ * ``$HOME ``
270
+ * ``$HOME/.local ``
271
+ * ``$HOME/.local/opt ``
272
+ * ``$HOME/bin ``
273
+ * ``/opt ``
274
+ * ``/usr/local ``
276
275
277
- where ``[-x.y.z] `` is optional text, and can be any text, for example ``-0.13.2 ``.
276
+ The Zephyr SDK bundle archive contains the ``zephyr-sdk-0.14.0 `` directory and, when
277
+ extracted under ``$HOME ``, the resulting installation path will be
278
+ ``$HOME/zephyr-sdk-0.14.0 ``.
278
279
279
- If you install the Zephyr SDK outside any of those locations, then it is
280
- required to register the Zephyr SDK in the CMake package registry during
281
- installation or set :envvar: `ZEPHYR_SDK_INSTALL_DIR ` to point to the Zephyr
282
- SDK installation folder .
280
+ If you install the Zephyr SDK outside any of these locations, you must
281
+ register the Zephyr SDK in the CMake package registry by running the setup
282
+ script, or set :envvar: `ZEPHYR_SDK_INSTALL_DIR ` to point to the Zephyr SDK
283
+ installation directory .
283
284
284
- :envvar: `ZEPHYR_SDK_INSTALL_DIR ` can also be used for pointing to a folder
285
- containing multiple Zephyr SDKs, allowing for automatic toolchain selection,
286
- for example: ``ZEPHYR_SDK_INSTALL_DIR=/company/tools ``
285
+ You can also use :envvar: `ZEPHYR_SDK_INSTALL_DIR ` for pointing to a
286
+ directory containing multiple Zephyr SDKs, allowing for automatic toolchain
287
+ selection. For example, ``ZEPHYR_SDK_INSTALL_DIR=/company/tools ``, where
288
+ the ``company/tools `` folder contains the following subfolders:
287
289
288
290
* ``/company/tools/zephyr-sdk-0.13.2 ``
289
291
* ``/company/tools/zephyr-sdk-a.b.c ``
290
292
* ``/company/tools/zephyr-sdk-x.y.z ``
291
293
292
- this allow Zephyr to pick the right toolchain, while allowing multiple Zephyr
293
- SDKs to be grouped together at a custom location.
294
+ This allows the Zephyr build system to choose the correct version of the
295
+ SDK, while allowing multiple Zephyr SDKs to be grouped together at a
296
+ specific path.
294
297
295
298
.. _sdkless_builds :
296
299
@@ -316,5 +319,5 @@ To make sure this variable is unset, run:
316
319
317
320
unset ZEPHYR_SDK_INSTALL_DIR
318
321
319
- .. _Zephyr Downloads : https://github.com/zephyrproject-rtos/sdk-ng/releases
322
+ .. _Zephyr SDK Releases : https://github.com/zephyrproject-rtos/sdk-ng/releases
320
323
.. _CMake Downloads : https://cmake.org/download
0 commit comments