| /Zephyr-latest/doc/develop/toolchains/ |
| D | zephyr_sdk.rst | 3 Zephyr SDK
6 The Zephyr Software Development Kit (SDK) contains toolchains for each of
7 Zephyr's supported architectures. It also includes additional host tools, such
10 Use of the Zephyr SDK is highly recommended and may even be required under
16 The Zephyr SDK supports the following target architectures:
18 * ARC (32-bit and 64-bit; ARCv1, ARCv2, ARCv3)
19 * ARM (32-bit and 64-bit; ARMv6, ARMv7, ARMv8; A/R/M Profiles)
20 * MIPS (32-bit and 64-bit)
22 * RISC-V (32-bit and 64-bit; RV32I, RV32E, RV64I)
23 * x86 (32-bit and 64-bit)
[all …]
|
| D | designware_arc_mwdt.rst | 9 #. You need to have :ref:`Zephyr SDK <toolchain_zephyr_sdk>` installed on your host.
12 A Zephyr SDK is used as a source of tools like device tree compiler (DTC), QEMU, etc...
13 Even though ARC MWDT toolchain is used for Zephyr RTOS build, still the GNU preprocessor & GNU
15 generation. We used Zephyr SDK as a source of these ARC GNU tools as well.
16 … To setup ARC GNU toolchain please use SDK Bundle (Full or Minimal) instead of manual installation
18 that allows you to avoid toolchain related issues while building Zephyr.
22 - Set :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` to ``arcmwdt``.
23 - Set :envvar:`ARCMWDT_TOOLCHAIN_PATH` to the toolchain installation directory. MWDT installation
29 :envvar:`ARCMWDT_TOOLCHAIN_PATH` - it would be detected automatically.
35 .. code-block:: console
|
| D | crosstool_ng.rst | 3 Crosstool-NG (Deprecated)
9 :ref:`cross-compile toolchain variant <other_x_compilers>` should be used
10 when using a custom toolchain built with Crosstool-NG.
12 You can build toolchains from source code using crosstool-NG.
14 #. Follow the steps on the crosstool-NG website to `prepare your host
15 <http://crosstool-ng.github.io/docs/os-setup/>`_.
17 #. Follow the `Zephyr SDK with Crosstool NG instructions
18 <https://github.com/zephyrproject-rtos/sdk-ng/blob/master/README.md>`_ to
22 You will need to clone the ``sdk-ng`` repo and run the following command:
24 .. code-block:: console
[all …]
|
| /Zephyr-latest/cmake/modules/ |
| D | FindZephyr-sdk.cmake | 1 # SPDX-License-Identifier: Apache-2.0
3 # Copyright (c) 2022-2023, Nordic Semiconductor ASA
5 # FindZephyr-sdk module for supporting module search mode of Zephyr SDK.
7 # It is possible to control the behavior of the Zephyr-SDK package using
9 # The Zephyr-SDK package supports the components:
10 # - LOAD: Load a Zephyr-SDK. This is the default behavior if no COMPONENTS is specified.
11 # Its purpose is to allow the find_package basic signature mode to lookup Zephyr
12 # SDK and based on user / environment settings of selected toolchain decide if
13 # the Zephyr SDK CMake package should be loaded.
15 # It extends the Zephyr-sdk CMake package by providing more flexibility in when
[all …]
|
| D | FindHostTools.cmake | 1 # SPDX-License-Identifier: Apache-2.0
6 # Zephyr development.
8 # This module will lookup the following tools for Zephyr development:
9 # +---------------------------------------------------------------+
11 # +---------------------------------------------------------------+
12 # | Generic C-compiler | Yes | Pre-processing of devicetree |
13 # | Zephyr-sdk | | |
18 # +---------------------------------------------------------------+
24 # Set to 'CMAKE_C_COMPILER-NOTFOUND' if no C compiler was found.
28 # Set to 'GPERF-NOTFOUND' if gperf was not found.
[all …]
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | installation_linux.rst | 32 .. group-tab:: Ubuntu
34 .. code-block:: console
36 sudo apt-get update
37 sudo apt-get upgrade
39 .. group-tab:: Fedora
41 .. code-block:: console
45 .. group-tab:: Clear Linux
47 .. code-block:: console
51 .. group-tab:: Arch Linux
53 .. code-block:: console
[all …]
|
| D | index.rst | 8 - Set up a command-line Zephyr development environment on Ubuntu, macOS, or
11 - Get the source code
12 - Build, flash, and run a sample application
23 .. group-tab:: Ubuntu
28 .. code-block:: bash
33 .. group-tab:: macOS
39 <https://support.apple.com/en-us/HT201541>`_.
41 .. group-tab:: Windows
46 .. _install-required-tools:
55 .. list-table::
[all …]
|
| /Zephyr-latest/cmake/toolchain/arcmwdt/ |
| D | generic.cmake | 1 # SPDX-License-Identifier: Apache-2.0
20 # arcmwdt relies on Zephyr SDK for the use of C preprocessor (devicetree) and objcopy
21 find_package(Zephyr-sdk 0.15 REQUIRED)
22 # Handling to be improved in Zephyr SDK, we can drop setting TOOLCHAIN_HOME after
23 # https://github.com/zephyrproject-rtos/sdk-ng/pull/682 got merged and we switch to proper SDK
28 # MWDT has no it's own preprocessor, so here zephyr-SDK preprocessor is used.
29 # At the same time zephyr-SDK requires ARCH variable to be initialized before include "generic.cmak…
31 # This workaround uses any (first awailable, independent on ARCH) toolchain from SDK for DTC prepro…
33 include(${ZEPHYR_SDK_INSTALL_DIR}/cmake/zephyr/generic.cmake)
38 # Handling to be improved in Zephyr SDK, to avoid overriding ZEPHYR_TOOLCHAIN_VARIANT by
[all …]
|
| /Zephyr-latest/scripts/west_commands/ |
| D | sdk.py | 3 # SPDX-License-Identifier: Apache-2.0
23 class Sdk(WestCommand): class
26 "sdk",
27 "manage Zephyr SDK",
28 "List and Install Zephyr SDK",
41 Run 'west sdk' or 'west sdk list' to list installed SDKs.
42 See 'west sdk list --help' for details.
45 Installing SDK:
47 Run 'west sdk install' to install Zephyr SDK.
48 See 'west sdk install --help' for details.
[all …]
|
| /Zephyr-latest/scripts/ |
| D | west-commands.yml | 2 west-commands:
3 - file: scripts/west_commands/completion.py
5 - name: completion
8 - file: scripts/west_commands/boards.py
10 - name: boards
13 - file: scripts/west_commands/shields.py
15 - name: shields
18 - file: scripts/west_commands/build.py
20 - name: build
22 help: compile a Zephyr application
[all …]
|
| /Zephyr-latest/modules/hal_rpi_pico/pico/ |
| D | config_autogen.h | 4 * SPDX-License-Identifier: Apache-2.0
8 * Originally this file is generated by pico-sdk, and some files
11 * Since this file ends up included in all pico-sdk code, it's
12 * used to inject workarounds to make pico-sdk compile with Zephyr.
24 #include <zephyr/toolchain.h>
36 #include <zephyr/devicetree.h>
40 /* Zephyr compatible way of forcing inline */
|
| /Zephyr-latest/doc/ |
| D | conf.py | 1 # Zephyr documentation build configuration file.
2 # Reference: https://www.sphinx-doc.org/en/master/usage/configuration.html
25 # Add the directory which contains the pytest-twister-pytest
26 sys.path.insert(0, str(ZEPHYR_BASE / "scripts" / "pylib" / "pytest-twister-harness" / "src"))
35 # -- Project --------------------------------------------------------------
37 project = "Zephyr Project"
38 copyright = "2015-2024 Zephyr Project members and individual contributors"
39 author = "The Zephyr Project Contributors"
62 version += "-" + extra
66 # parse SDK version from 'SDK_VERSION' file
[all …]
|
| /Zephyr-latest/scripts/west_commands/zspdx/ |
| D | sbom.py | 3 # SPDX-License-Identifier: Apache-2.0
32 # should also add an SPDX document for the SDK?
36 # create Cmake file-based API directories and query file
51 # check that codemodel-v2 exists as a file, or else create it
52 queryFilePath = os.path.join(cmakeApiDirPath, "codemodel-v2")
72 log.wrn(f"config: requested to analyze includes but not to generate SDK SPDX document;")
73 log.wrn(f"config: will proceed but will discard detected includes for SDK header files")
102 # write SDK document, if we made one
104 retval = writeSPDX(os.path.join(cfg.spdxDir, "sdk.spdx"), w.docSDK)
106 log.err("SPDX writer failed for SDK document; bailing")
[all …]
|
| /Zephyr-latest/doc/develop/ |
| D | beyond-GSG.rst | 1 .. _beyond-gsg:
6 The :ref:`getting_started` gives a straight-forward path to set up
7 your Linux, macOS, or Windows environment for Zephyr development. In
8 this document, we delve deeper into Zephyr development setup
11 .. _python-pip:
16 Python 3 and its package manager, pip\ [#pip]_, are used extensively by Zephyr
17 to install and run scripts required to compile and run Zephyr
18 applications, set up and maintain the Zephyr development environment,
22 ``--user`` flag to the ``pip3`` command when installing new packages. This is
25 information about pip\ [#pip]_, including `information on -\\-user`_.
[all …]
|
| /Zephyr-latest/soc/nxp/mcx/mcxn/ |
| D | CMakeLists.txt | 4 # SPDX-License-Identifier: Apache-2.0
7 # Pass this flag so the SDK I2C, UART and SPI drivers do not init the LP
8 # Flexcomm SDK driver
22 set(SOC_LINKER_SCRIPT ${ZEPHYR_BASE}/include/zephyr/arch/arm/cortex_m/scripts/linker.ld CACHE INTER…
|
| /Zephyr-latest/scripts/west_commands/tests/ |
| D | test_bossac.py | 3 # Copyright (c) 2020-2021 Gerson Fernando Budke <nandojve@gmail.com>
5 # SPDX-License-Identifier: Apache-2.0
18 pytest.skip("skipping Linux-only bossac tests", allow_module_level=True)
20 TEST_BOSSAC_PORT = 'test-bossac-serial'
27 ['stty', '-F', TEST_BOSSAC_PORT, 'raw', 'ispeed', '115200',
28 'ospeed', '115200', 'cs8', '-cstopb', 'ignpar', 'eol', '255',
30 ['bossac', '-p', TEST_BOSSAC_PORT, '-R', '-w', '-v',
31 '-b', RC_KERNEL_BIN],
35 ['stty', '-F', TEST_BOSSAC_PORT, 'raw', 'ispeed', TEST_BOSSAC_SPEED,
36 'ospeed', TEST_BOSSAC_SPEED, 'cs8', '-cstopb', 'ignpar', 'eol', '255',
[all …]
|
| /Zephyr-latest/boards/shields/frdm_kw41z/doc/ |
| D | index.rst | 3 NXP FRDM-KW41Z Shield
9 The FRDM-KW41Z is a development kit enabled by the Kinetis |reg| W series
10 KW41Z/31Z/21Z (KW41Z) family built on ARM |reg| Cortex |reg|-M0+ processor with
15 The FRDM-KW41Z can be used as a standalone board or as an Arduino shield. This
16 document covers usage as a shield; see :zephyr:board:`frdm_kw41z` for usage as a
22 To use the FRDM-KW41Z as a Bluetooth low energy controller shield with a serial
25 #. Download the MCUXpresso SDK for FRDM-KW41Z from the `MCUXpresso SDK Builder
33 .. code-block:: console
39 #. Connect the FRDM-KW41Z board to your computer with a USB cable. A USB mass
48 - J30 pin 1 is attached to J31 pin 2
[all …]
|
| /Zephyr-latest/drivers/mipi_dbi/ |
| D | CMakeLists.txt | 3 # SPDX-License-Identifier: Apache-2.0
11 # Data bus width is used by the SDK driver and processes it as a compile time option
13 dt_chosen(flexio0_lcd PROPERTY "zephyr,display")
14 dt_prop(data_bus_width PATH "${flexio0_lcd}" PROPERTY "mipi-mode")
15 # Values for mipi-mode property are defined inside dt-bindings/mipi_dbi/mipi_dbi.h.
16 # We pass a define to the SDK driver if we are using 8-bit mode.
|
| /Zephyr-latest/scripts/west_commands/completion/ |
| D | west-completion.fish | 20 set -l tokens (commandline -opc)
41 set -l tokens (commandline -opc)
42 set -l argc (count $argv)
43 set -l max $argv[1]
44 set -l counter 0
46 if test $argc -eq 1
47 if test (math (count $tokens) - 2) -ge $max
60 if $counter -ge $max
77 set -l tokens (commandline -opc)
80 if string match -qr -- "$token*" "$tokens[-1]"
[all …]
|
| /Zephyr-latest/boards/altr/max10/doc/ |
| D | index.rst | 1 .. zephyr:board:: altera_max10
6 The Zephyr kernel is supported on the Altera MAX10 Rev C development kit, using
28 Other switches are user switches, their position is application-specific.
33 You will need the Altera Quartus SDK in order to work with this device. The
37 For your convenience using the SDK tools (such as ``nios2-configure-sof``),
38 you should put the binaries provided by the SDK
40 SDK:
42 .. code-block:: console
48 II peripheral, which is the built-in JTAG interface for this device.
52 .. code-block:: console
[all …]
|
| /Zephyr-latest/boards/ti/cc3235sf_launchxl/doc/ |
| D | index.rst | 1 .. zephyr:board:: cc3235sf_launchxl
5 The SimpleLink Wi-Fi CC3235SF LaunchPad development kit (CC3235SF-LAUNCHXL)
6 highlights CC3235SF, a single-chip wireless microcontroller (MCU) with
16 Cortex-M4 MCU and a network processor MCU to run all Wi-Fi and
18 * 40-pin LaunchPad standard leveraging the BoosterPack ecosystem
19 * On-board accelerometer and temperature sensor
22 * BoosterPack plug-in module for adding graphical displays, audio
25 * XDS110-based JTAG emulation with serial port for flash programming
35 #. Applications MCU - an ARM |reg| Cortex |reg|-M4 Core at 80 MHz, with 256Kb RAM,
39 #. Network Coprocessor (NWP) - a dedicated ARM MCU, which completely
[all …]
|
| /Zephyr-latest/boards/ti/cc3220sf_launchxl/doc/ |
| D | index.rst | 1 .. zephyr:board:: cc3220sf_launchxl
5 The SimpleLink Wi-Fi CC3220SF LaunchPad development kit (CC3220SF-LAUNCHXL)
6 highlights CC3220SF, a single-chip wireless microcontroller (MCU) with
16 Cortex-M4 MCU and a network processor MCU to run all Wi-Fi and
18 * 40-pin LaunchPad standard leveraging the BoosterPack ecosystem
19 * On-board accelerometer and temperature sensor
22 * BoosterPack plug-in module for adding graphical displays, audio
25 * XDS110-based JTAG emulation with serial port for flash programming
35 #. Applications MCU - an ARM |reg| Cortex |reg|-M4 Core at 80 MHz, with 256Kb RAM,
39 #. Network Coprocessor (NWP) - a dedicated ARM MCU, which completely
[all …]
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | ota.rst | 3 Over-the-Air Update
9 Over-the-Air (OTA) Update is a method for delivering firmware updates to remote
17 The :ref:`dfu` section discusses upgrading Zephyr firmware using MCUboot. The
35 1. A working sample can be found on the `Golioth Firmware SDK repository`_
47 There is a :zephyr:code-sample:`hawkbit-api` sample included in the
48 Zephyr :zephyr:code-sample-category:`mgmt` section.
58 There is an :zephyr:code-sample:`updatehub-fota` sample included in the Zephyr
59 :zephyr:code-sample-category:`mgmt` section.
69 There is an :zephyr:code-sample:`smp-svr` sample included in the Zephyr
70 :zephyr:code-sample-category:`mgmt` section.
[all …]
|
| /Zephyr-latest/doc/_templates/ |
| D | zversions.html | 1 {# Add rst-badge after rst-versions for small badge style. #}
2 <div class="rst-versions" data-toggle="rst-versions" role="note" aria-label="versions">
3 <span class="rst-current-version" data-toggle="rst-current-version">
4 <span class="fa fa-book"> Zephyr Project</span>
6 <span class="fa fa-caret-down"></span>
8 <div class="rst-other-versions">
18 <dd><a href="/{{ prefix }}/zephyr.pdf">PDF</a></dd>
26 <a href="https://github.com/zephyrproject-rtos/sdk-ng/releases">SDK</a>
29 <a href="https://github.com/zephyrproject-rtos/zephyr/releases">Releases</a>
|
| /Zephyr-latest/boards/qemu/arc/ |
| D | board.cmake | 7 set(QEMU_FLAGS_${ARCH} -cpu arcem)
10 set(QEMU_FLAGS_${ARCH} -cpu archs)
14 set(QEMU_FLAGS_${ARCH} -cpu hs5x)
18 set(QEMU_FLAGS_${ARCH} -cpu hs6x)
22 # to 'virt' board. It will be renamed in ARC QEMU in the nearest Zephyr SDK
25 # until the updated Zephyr SDK will be set as default. By that we keep both SDKs
27 # After that we can specify board explicitly with '-M virt' option.
29 -m 8M
30 -nographic
31 -no-reboot
[all …]
|
