Searched full:sdk (Results 1 – 25 of 346) sorted by relevance
12345678910>>...14
| /Zephyr-latest/doc/develop/toolchains/ |
| D | zephyr_sdk.rst | 3 Zephyr SDK
6 The Zephyr Software Development Kit (SDK) contains toolchains for each of
10 Use of the Zephyr SDK is highly recommended and may even be required under
16 The Zephyr SDK supports the following target architectures:
31 The Zephyr SDK bundle supports all major operating systems (Linux, macOS and
36 If no toolchain is selected, the build system looks for Zephyr SDK and uses the toolchain
40 If you install the Zephyr SDK outside any of the default locations (listed in
42 of the Zephyr SDK, then you must register the Zephyr SDK in the CMake package registry
43 by running the setup script. If you decide not to register the Zephyr SDK in the CMake registry,
44 then the :envvar:`ZEPHYR_SDK_INSTALL_DIR` can be used to point to the Zephyr SDK installation
[all …]
|
| D | cadence_xcc.rst | 18 * Follow the instruction from Cadence on how to install the SDK.
20 * Depending on the SDK, there are two set of compilers:
26 #. Make sure you have obtained a license to use the SDK, or has access to
35 * There are two ways to specify the SoC ID and the SDK version to use.
42 * Set :envvar:`TOOLCHAIN_VER` to the Xtensa SDK version.
49 to the Xtensa SDK version.
51 #. For example, assuming the SDK is installed in ``/opt/xtensa``, and
52 using the SDK for application development on ``intel_adsp/ace15_mtpm``,
|
| 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...
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
|
| D | crosstool_ng.rst | 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:
|
| /Zephyr-latest/cmake/modules/ |
| D | FindZephyr-sdk.cmake | 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.
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
16 # the Zephyr SDK is loaded and loads additional host tools from the Zephyr SDK.
20 # Install location of the Zephyr SDK
26 # True if the Zephyr SDK was found.
[all …]
|
| /Zephyr-latest/modules/hal_rpi_pico/ |
| D | Kconfig | 10 Use the UART driver from pico-sdk
15 Use the GPIO driver from pico-sdk
20 Use the flash driver from pico-sdk
25 Use the PWM driver from pico-sdk
30 Use the ADC driver from pico-sdk
35 Use the DMA driver from pico-sdk
41 Use the PIO driver from pico-sdk
46 Use the "claim" driver from pico-sdk
51 Use the TIMER driver from pico-sdk
56 Use the RTC driver from pico-sdk
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | installation_linux.rst | 192 bundled in the :ref:`Zephyr SDK <toolchain_zephyr_sdk>` by installing it.
207 Install the Zephyr Software Development Kit (SDK)
210 The Zephyr Software Development Kit (SDK) contains toolchains for each of
214 Use of the Zephyr SDK is highly recommended and may even be required under
217 The Zephyr SDK supports the following target architectures:
227 Follow these steps to install the Zephyr SDK:
229 #. Download and verify the `Zephyr SDK bundle`_:
233 wget |sdk-url-linux|
234 wget -O - |sdk-url-linux-sha| | shasum --check --ignore-missing
236 You can change |sdk-version-literal| to another version if needed; the
[all …]
|
| D | index.rst | 382 Install the Zephyr SDK
385 The :ref:`Zephyr Software Development Kit (SDK) <toolchain_zephyr_sdk>`
398 Install the Zephyr SDK using the ``west sdk install``.
403 west sdk install
407 Using the command options, you can specify the SDK installation destination
409 See ``west sdk install --help`` for details.
413 Install the Zephyr SDK using the ``west sdk install``.
418 west sdk install
422 Using the command options, you can specify the SDK installation destination
424 See ``west sdk install --help`` for details.
[all …]
|
| /Zephyr-latest/cmake/toolchain/arcmwdt/ |
| D | generic.cmake | 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…
38 # Handling to be improved in Zephyr SDK, to avoid overriding ZEPHYR_TOOLCHAIN_VARIANT by
39 # find_package(Zephyr-sdk) if it's already set
|
| /Zephyr-latest/scripts/west_commands/ |
| D | sdk.py | 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.
67 … Run 'west sdk' or 'west sdk list' command information about available SDKs is displayed.
[all …]
|
| /Zephyr-latest/modules/ |
| D | Kconfig.simplelink | 1 # CC3220/CC32XX SDK HAL configuration
22 # MSP432 SDK HAL configuration
28 # CC13X2 / CC26X2 SDK HAL configuration
|
| /Zephyr-latest/dts/bindings/counter/ |
| D | nxp,imx-tmr.yaml | 25 of the MCUXpresso SDK
40 of the MCUXpresso SDK
62 of the MCUXpresso SDK
|
| /Zephyr-latest/scripts/west_commands/zspdx/ |
| D | sbom.py | 32 # should also add an SPDX document for the SDK?
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")
|
| /Zephyr-latest/modules/hal_rpi_pico/pico/ |
| D | config_autogen.h | 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.
|
| /Zephyr-latest/tests/modules/thrift/ThriftTest/ |
| D | testcase.yaml | 9 # qemu_x86 exluded due to missing long double functions in SDK
10 # See https://github.com/zephyrproject-rtos/sdk-ng/issues/603
|
| /Zephyr-latest/soc/nxp/mcx/mcxn/ |
| D | CMakeLists.txt | 7 # Pass this flag so the SDK I2C, UART and SPI drivers do not init the LP
8 # Flexcomm SDK driver
|
| /Zephyr-latest/scripts/ |
| D | west-commands.yml | 82 - file: scripts/west_commands/sdk.py
84 - name: sdk
85 class: Sdk
86 help: manage Zephyr SDK
|
| /Zephyr-latest/boards/nxp/mimxrt1180_evk/ |
| D | board.cmake | 8 "${ZEPHYR_HAL_NXP_MODULE_DIR}/mcux/mcux-sdk/boards/evkmimxrt1180")
11 …n be referred on chapter 7 of getting start with Mcuxpresso SDK for MIMXRT1180-EVK doc in SDK pack…
|
| /Zephyr-latest/drivers/mipi_dbi/ |
| D | CMakeLists.txt | 11 # Data bus width is used by the SDK driver and processes it as a compile time option
16 # We pass a define to the SDK driver if we are using 8-bit mode.
|
| /Zephyr-latest/modules/hal_nxp/ |
| D | CMakeLists.txt | 13 …zephyr_sources_ifdef(CONFIG_PWM_MCUX_CTIMER ${ZEPHYR_CURRENT_MODULE_DIR}/mcux/mcux-sdk/drivers/cti…
15 ${ZEPHYR_CURRENT_MODULE_DIR}/mcux/mcux-sdk/drivers/ctimer/)
|
| /Zephyr-latest/doc/ |
| D | conf.py | 66 # parse SDK version from 'SDK_VERSION' file
141 SDK_URL_BASE="https://github.com/zephyrproject-rtos/sdk-ng/releases/download"
146 .. |sdk-version-literal| replace:: ``{sdk_version}``
147 .. |sdk-version-trim| unicode:: {sdk_version}
149 .. |sdk-version-ltrim| unicode:: {sdk_version}
151 .. _Zephyr SDK bundle: https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v{sdk_version}
152 .. |sdk-url-linux| replace::
153 `{SDK_URL_BASE}/v{sdk_version}/zephyr-sdk-{sdk_version}_linux-x86_64.tar.xz`
154 .. |sdk-url-linux-sha| replace::
156 .. |sdk-url-macos| replace::
[all …]
|
| /Zephyr-latest/scripts/west_commands/tests/ |
| D | test_bossac.py | 173 Any SDK
206 Any SDK
243 Any SDK
281 Any SDK
318 SDK >= 0.12.0
363 Any SDK
397 SDK >= 0.12.0
431 SDK >= 0.12.0
466 Any SDK
498 Test old SDK and ask user to upgrade
[all …]
|
| /Zephyr-latest/scripts/west_commands/completion/ |
| D | west-completion.fish | 183 "sdk" "manage SDKs"
498 …n "__zephyr_west_seen_subcommand_from spdx" -l include-sdk -d "also generate SPDX document for SDK"
506 # sdk
507 complete -c west -n "__zephyr_west_use_subcommand; and __zephyr_west_check_if_in_workspace" -ra sdk…
508 …_seen_subcommand_from sdk; and not __fish_seen_subcommand_from list install" -ra "list\t'list inst…
509 …zephyr_west_seen_subcommand_from sdk; and __fish_seen_subcommand_from install" -l version -d "vers…
510 …-n "__zephyr_west_seen_subcommand_from sdk; and __fish_seen_subcommand_from install" -o b -l insta…
511 … -n "__zephyr_west_seen_subcommand_from sdk; and __fish_seen_subcommand_from install" -o d -l inst…
512 complete -c west -n "__zephyr_west_seen_subcommand_from sdk; and __fish_seen_subcommand_from instal…
513 complete -c west -n "__zephyr_west_seen_subcommand_from sdk; and __fish_seen_subcommand_from instal…
[all …]
|
| /Zephyr-latest/doc/develop/ |
| D | beyond-GSG.rst | 67 You can install the :ref:`Zephyr SDK <toolchain_zephyr_sdk>` to get toolchains for all
79 Updating the Zephyr SDK toolchain
82 When updating Zephyr SDK, check whether the :envvar:`ZEPHYR_TOOLCHAIN_VARIANT`
85 * If the variables are not set, the latest compatible version of Zephyr SDK will be selected
89 at build time. Zephyr SDK is identified by the value ``zephyr``.
91 unset it or change its value to ``zephyr`` to make sure Zephyr SDK is selected.
94 the default lookup location for Zephyr SDK. If you install Zephyr SDK to one
252 installed the Zephyr SDK there is a copy of this rules file in the SDK
261 * or copy the rules file from the Zephyr SDK folder::
280 SDK installation.)
|
| /Zephyr-latest/boards/shields/frdm_kw41z/doc/ |
| D | index.rst | 25 #. Download the MCUXpresso SDK for FRDM-KW41Z from the `MCUXpresso SDK Builder
72 .. _MCUXpresso SDK Builder Website:
|
12345678910>>...14
