Searched +full:development +full:- +full:tools (Results 1 – 25 of 285) sorted by relevance
12345678910>>...12
| /Zephyr-latest/doc/develop/toolchains/ |
| D | arm_compiler.rst | 6 #. Download and install a development suite containing the `Arm Compiler 6`_
11 - Set :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` to ``armclang``.
12 - Set :envvar:`ARMCLANG_TOOLCHAIN_PATH` to the toolchain installation
20 .. code-block:: bash
27 .. code-block:: batch
34 #. If the Arm Compiler 6 was installed as part of an Arm Development Studio, then
36 …n <https://developer.arm.com/tools-and-software/software-development-tools/license-management/reso…
37 For example if the Arm Development Studio is installed in:
38 ``/opt/armds-2020-1`` with a Gold license, then set :envvar:`ARM_PRODUCT_DEF`
39 to point to ``/opt/armds-2020-1/gold.elmap``.
[all …]
|
| D | host.rst | 6 In some specific configurations, like when building for non-MCU x86 targets on
7 a Linux host, you may be able to reuse the native development tools provided
|
| D | designware_arc_mwdt.rst | 3 DesignWare ARC MetaWare Development Toolkit (MWDT)
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.
17 of separate tarballs. It installs and registers toolchain and host tools in the system,
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 | cadence_xcc.rst | 6 #. Obtain Tensilica Software Development Toolkit targeting the specific SoC
12 * A SoC-specific add-on to be installed on top of Xtensa Xplorer.
14 * This add-on allows the compiler to generate code for the SoC on hand.
16 #. Install Xtensa Xplorer and then the SoC add-on.
22 * GCC-based compiler: ``xt-xcc`` and its friends.
24 * Clang-based compiler: ``xt-clang`` and its friends.
31 * Set :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` to ``xcc`` or ``xt-clang``.
52 using the SDK for application development on ``intel_adsp/ace15_mtpm``,
57 .. code-block:: console
60 export ZEPHYR_TOOLCHAIN_VARIANT=xt-clang
[all …]
|
| /Zephyr-latest/doc/project/ |
| D | index.rst | 24 The Zephyr project defines a development process workflow using GitHub
30 `program management overview <https://wiki.zephyrproject.org/Program-Management>`_.
35 project's :ref:`development processes and tools <dev-environment-and-tools>`
40 with respect to the development process workflow.
46 - mainline: The main tree where the core functionality and core features are
48 - subsystem/feature branch: is a branch within the same repository. In our case,
51 - upstream: A parent branch the source code is based on. This is the branch you
53 - LTS: Long Term Support
|
| D | code_flow.rst | 1 .. _code-flow-and-branches:
12 Which contains the latest state of development
14 collab-\*
15 Collaboration branches that are used for shared development
19 branch shall target the main development branch. For released versions of
23 vx.y-branch
27 Development in collaboration branches before features go to mainline allows teams to
37 possible to initiate in-depth discussions around new additions before
54 - Use the infrastructure and tools provided by the project (GitHub, Git)
55 - All changes to collaboration branches shall come in form of github pull requests.
[all …]
|
| /Zephyr-latest/doc/develop/west/ |
| D | why.rst | 1 .. _west-history:
9 * The ability to provide an extensible and user-friendly command-line interface
12 During the development of west, a set of :ref:`west-design-constraints` were
13 identified to avoid the common pitfalls of tools of this kind.
20 along with a clear justification of the choice not to use existing tools and
32 * **R4**: Support both continuous tracking and commit-based (bisectable) project
40 `Git Submodules <https://git-scm.com/book/en/v2/Git-Tools-Submodules>`_ and
41 Google's `repo <https://gerrit.googlesource.com/git-repo/>`_.
43 Existing tools were considered during west's initial design and development.
49 - Does not cleanly support using zephyr as the manifest repository (**R4**)
[all …]
|
| /Zephyr-latest/doc/develop/flash_debug/ |
| D | host-tools.rst | 1 .. _flash-debug-host-tools:
3 Flash & Debug Host Tools
6 This guide describes the software tools you can run on your host workstation to
9 Zephyr's west tool has built-in support for all of these in its ``flash``,
12 file declares that support properly. See :ref:`west-build-flash-debug` for
17 SAM Boot Assistant (SAM-BA)
20 Atmel SAM Boot Assistant (Atmel SAM-BA) allows In-System Programming (ISP)
22 allows users to develop and program boards with SAM-BA support using
23 :ref:`west <west-flashing>`. Zephyr supports devices with/without ROM
29 .. code-block:: console
[all …]
|
| D | nordic_segger.rst | 5 Nordic nRF5x Segger J-Link
11 All Nordic nRF5x Development Kits, Preview Development Kits and Dongles are equipped
14 * Segger J-Link firmware and desktop tools
16 * Mass Storage device for drag-and-drop image flashing
21 Segger J-Link Software Installation
24 To install the J-Link Software and documentation pack, follow the steps below:
26 #. Download the appropriate package from the `J-Link Software and documentation pack`_ website
28 #. When connecting a J-Link-enabled board such as an nRF5x DK, PDK or dongle, a
31 nRF5x Command-Line Tools Installation
34 The nRF5x command-line Tools allow you to control your nRF5x device from the command line,
[all …]
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | qemu_setup.rst | 16 In this example, the :zephyr:code-sample:`sockets-echo-server` sample application from
25 On the Linux Host, find the Zephyr `net-tools`_ project, which can either be
26 found in a Zephyr standard installation under the ``tools/net-tools`` directory
29 .. code-block:: console
31 sudo apt install -y socat libpcap-dev
32 git clone https://github.com/zephyrproject-rtos/net-tools
33 cd net-tools
39 ``autoconf-archive`` package on Debian/Ubuntu.
46 * Terminal #1 is your usual Zephyr development terminal, with the Zephyr environment
48 * Terminals #2, #3, and #4 are terminal windows with net-tools being the current
[all …]
|
| D | qemu_eth_setup.rst | 13 In this example, the :zephyr:code-sample:`sockets-echo-server` sample application from
21 On the Linux Host, find the Zephyr `net-tools`_ project, which can either be
22 found in a Zephyr standard installation under the ``tools/net-tools`` directory
25 .. code-block:: console
27 git clone https://github.com/zephyrproject-rtos/net-tools
35 * Terminal #1 is terminal window with net-tools being the current
36 directory (``cd net-tools``)
37 * Terminal #2 is your usual Zephyr development terminal,
52 Step 1 - Create Ethernet interface
60 .. code-block:: console
[all …]
|
| D | native_sim_setup.rst | 16 In this example, the :zephyr:code-sample:`sockets-echo-server` sample application from
24 On the Linux Host, find the Zephyr `net-tools`_ project, which can either be
25 found in a Zephyr standard installation under the ``tools/net-tools`` directory
28 .. code-block:: console
30 git clone https://github.com/zephyrproject-rtos/net-tools
38 * Terminal #1 is terminal window with net-tools being the current
39 directory (``cd net-tools``)
40 * Terminal #2 is your usual Zephyr development terminal,
45 Step 1 - Create Ethernet interface
46 ----------------------------------
[all …]
|
| /Zephyr-latest/boards/panasonic/pan1783/doc/ |
| D | index.rst | 6 The PAN1783, PAN1783A and PAN1783A-PA Evaluation Boards (pan1783_evb,
7 pan1783a_evb, pan1783a_pa_evb) are development tools for the PAN1783,
8 PAN1783A and PAN1783A-PA Modules which are based on the nRF5340 chipset
11 More information about the PAN1783, PAN1783A, PAN1783A-PA Modules and
25 PAN1783A-PA EVB
28 The PAN1783A-PA EVB essentially resembles a PAN1783 EVB, with the addition
36 for the Evaluation Boards in the `Panasonic Wireless Connectivity Development Hub`_.
44 * software development
46 The schematics for the PAN1783/PAN1783A/PAN1783A-PA Evaluation Boards are
47 …in the `download section PAN1783`_ / `download section PAN1783A`_ / `download section PAN1783A-PA`_
[all …]
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | installation_linux.rst | 20 done so already. While some tools use the environment variables
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
[all …]
|
| /Zephyr-latest/dts/bindings/gpio/ |
| D | atmel-xplained-header.yaml | 2 # SPDX-License-Identifier: Apache-2.0
29 https://www.microchip.com/development-tools/xplained-boards
30 …http://ww1.microchip.com/downloads/en/DeviceDoc/Atmel-42091-Atmel-Xplained-Pro-Hardware-Developmen…
43 compatible: "atmel-xplained-header"
45 include: [gpio-nexus.yaml, base.yaml]
|
| D | atmel-xplained-pro-header.yaml | 2 # SPDX-License-Identifier: Apache-2.0
28 https://www.microchip.com/development-tools/xplained-boards
29 …http://ww1.microchip.com/downloads/en/DeviceDoc/Atmel-42091-Atmel-Xplained-Pro-Hardware-Developmen…
37 0 ADC(+) 3 4 ADC(-) 1
39 4 PWM(+) 7 8 PWM(-) 5
47 compatible: "atmel-xplained-pro-header"
49 include: [gpio-nexus.yaml, base.yaml]
|
| /Zephyr-latest/boards/microchip/m2gl025_miv/doc/ |
| D | index.rst | 6 The Microchip M2GL025 board is an IGLOO2 FPGA based development board.
7 The Mi-V RISC-V soft CPU can be deployed on the MGL025 board.
9 …icrochip's website <https://www.microchip.com/en-us/products/fpgas-and-plds/fpga-and-soc-design-to…
20 .. zephyr-app-commands::
28 with RISC-V support.
32 <https://www.microchip.com/en-us/products/fpgas-and-plds/fpga-and-soc-design-tools/soc-fpga/softcon…
34 With the necessary tools installed, you can connect to the board using OpenOCD.
37 .. code-block:: bash
40 <softconsole_path>/openocd/bin/openocd --file \
41 <softconsole_path>/openocd/share/openocd/scripts/board/microsemi-riscv.cfg
[all …]
|
| /Zephyr-latest/cmake/modules/ |
| D | FindHostTools.cmake | 1 # SPDX-License-Identifier: Apache-2.0
5 # FindHostTools module for locating a set of tools to use on the host for
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.
[all …]
|
| D | FindTargetTools.cmake | 1 # SPDX-License-Identifier: Apache-2.0
3 # FindTargetTools module for locating a set of tools to use on the host but
4 # targeting a remote target for Zephyr development.
6 # This module will lookup following target tools for Zephyr development:
7 # +---------------------------------------------------------------+
9 # +---------------------------------------------------------------+
10 # | Target C-compiler | Yes | |
13 # +---------------------------------------------------------------+
19 # Set to 'CMAKE_C_COMPILER-NOTFOUND' if no C compiler was found.
22 # True if all required host tools were found.
[all …]
|
| /Zephyr-latest/boards/st/stm32h750b_dk/doc/ |
| D | index.rst | 6 The STM32H750B-DK Discovery kit is a complete demonstration and development
7 platform for Arm® Cortex®-M7 core-based STM32H750XBH6 microcontroller, with
10 The STM32H750B-DK Discovery kit is used as a reference design for user
11 application development before porting to the final product, thus simplifying
12 the application development.
15 their application development by an evaluation of all the peripherals (such as
18 Octo-SPI Flash memory, RGB interface LCD with capacitive touch panel, and others).
22 STLINK-V3E is integrated into the board, as the embedded in-circuit debugger and
23 programmer for the STM32 MCU and USB Virtual COM port bridge. STM32H750B-DK board
27 More information about the board can be found at the `STM32H750B-DK website`_.
[all …]
|
| /Zephyr-latest/boards/mediatek/ |
| D | index.rst | 1 .. _boards-mtk_adsp:
12 Development has been done on and validation performed on at least
27 single-core devices, no parallel SMP is available, but at the same
37 There is comparatively little on-device hardware. The architecture is
38 that interaction with the off-chip audio hardware (e.g. I2S codecs,
42 Beyond that the Zephyr-visible hardware is limited to a bounty of
56 interpreter. A chromebook in development mode with the dev packages
60 * `Developer mode <https://www.chromium.org/chromium-os/developer-library/guides/device/developer-m…
61 …-Install: Installing Developer and Test packages onto a Chrome OS device <https://www.chromium.org…
68 .. code-block:: console
[all …]
|
| /Zephyr-latest/samples/modules/tflite-micro/tflm_ethosu/ |
| D | README.rst | 1 .. zephyr:code-sample:: tflite-ethosu
2 :name: TensorFlow Lite for Microcontrollers on Arm Ethos-U
4 Run an inference using an optimized TFLite model on Arm Ethos-U NPU.
10 framework and the Arm Ethos-U NPU.
13 `Arm model zoo <https://github.com/ARM-software/ML-zoo>`_. This model has then
15 `Vela compiler <https://git.mlplatform.org/ml/ethos-u/ethos-u-vela.git>`_.
18 where the operators supported by Ethos-U have been replaced by an Ethos-U custom
20 Ethos-U custom operator.
25 Add the tflite-micro module to your West manifest and pull it:
27 .. code-block:: console
[all …]
|
| /Zephyr-latest/boards/st/nucleo_l4r5zi/doc/ |
| D | index.rst | 6 The Nucleo L4R5ZI board features an ARM Cortex-M4 based STM32L4R5ZI MCU
11 - STM32 microcontroller in LQFP144 package
12 - Two types of extension resources:
14 - Arduino Uno V3 connectivity
15 - ST morpho extension pin headers for full access to all STM32 I/Os
17 - On-board ST-LINK/V2-1 debugger/programmer with SWD connector
18 - Flexible board power supply:
20 - USB VBUS or external source(3.3V, 5V, 7 - 12V)
21 - Power management access point
23 - Three User LEDs: LD1 (Green), LD2 (Blue), LD3 (Red)
[all …]
|
| /Zephyr-latest/boards/microchip/mpfs_icicle/doc/ |
| D | index.rst | 6 The Microchip mpfs_icicle board is a PolarFire SoC FPGA based development board with a Microchip MP…
7 The E51 RISC-V CPU can be deployed on the mpfs_icicle board.
8 More information can be found on the `Microchip website <https://www.microchip.com/en-us/product/MP…
19 .. zephyr-app-commands::
25 .. zephyr-app-commands::
33 with RISC-V support.
37 <https://www.microchip.com/en-us/products/fpgas-and-plds/fpga-and-soc-design-tools/programming-and-…
39 With the necessary tools installed, you can connect to the board using OpenOCD.
42 .. code-block:: bash
45 <softconsole_path>/openocd/bin/openocd --command "set DEVICE MPFS" --file \
[all …]
|
| /Zephyr-latest/boards/st/steval_stwinbx1/doc/ |
| D | index.rst | 6 The STWIN.box (STEVAL-STWINBX1) is a development kit that features an Arm|reg| Cortex|reg|-M33 base…
10 The STEVAL-STWINBX1 kit consists of an STWIN.box core system, a 480mAh LiPo battery, an adapter for…
13 More information about the board can be found at the `STEVAL-STWINBX1 Development kit website`_.
19 The STEVAL-STWINBX1 provides motion, environmental, and audio
20 sensor data through either the built-in RS485 transceiver, BLE, Wi-Fi, and
23 - Multisensing wireless platform for vibration monitoring and ultrasound detection
24 - Baby crying detection with Cloud AI learning
25 - Barometer / environmental monitoring
26 - Vehicle / goods tracking
27 - Vibration monitoring
[all …]
|
12345678910>>...12
