Searched +full:apt +full:- +full:get (Results 1 – 25 of 26) sorted by relevance
12
/Zephyr-Core-3.4.0/.github/workflows/ |
D | doc-build.yml | 2 # SPDX-License-Identifier: Apache-2.0 8 - cron: '0 */3 * * *' 11 - v* 14 - 'doc/**' 15 - '**.rst' 16 - 'include/**' 17 - 'kernel/include/kernel_arch_interface.h' 18 - 'lib/libc/**' 19 - 'subsys/testsuite/ztest/include/**' 20 - 'tests/**' [all …]
|
D | issue_count.yml | 5 - cron: '*/10 * * * *' 10 COMMITTER_NAME: github-actions 11 COMMITTER_USERNAME: github-actions 15 track-issues: 17 runs-on: ubuntu-22.04 18 if: github.repository == 'zephyrproject-rtos/zephyr' 21 - name: Download configuration file 23 …wget -q https://raw.githubusercontent.com/$GITHUB_REPOSITORY/main/.github/workflows/issues-report-… 25 - name: install-packages 27 sudo apt-get update [all …]
|
D | coding_guidelines.yml | 7 runs-on: ubuntu-22.04 10 - name: Checkout the code 14 fetch-depth: 0 16 - name: cache-pip 20 key: ${{ runner.os }}-doc-pip 22 - name: Install python dependencies 28 - name: Install Packages 30 sudo apt-get update 31 sudo apt-get install coccinelle 33 - name: Run Coding Guildeines Checks [all …]
|
D | footprint-tracking.yml | 6 - cron: '50 1/12 * * *' 9 - 'VERSION' 10 - '.github/workflows/footprint-tracking.yml' 12 - main 13 - v*-branch 15 # only publish v* tags, do not care about zephyr-v* which point to the 17 - 'v*' 20 group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.head_ref || github.ref }} 21 cancel-in-progress: true 24 footprint-tracking: [all …]
|
D | codecov.yaml | 5 - cron: '25 */3 * * 1-5' 8 group: ${{ github.workflow }}-${{ github.event_name }}-${{ github.head_ref || github.ref }} 9 cancel-in-progress: true 13 if: github.repository == 'zephyrproject-rtos/zephyr' 14 runs-on: zephyr-runner-linux-x64-4xlarge 16 image: ghcr.io/zephyrproject-rtos/ci:v0.26.4 17 options: '--entrypoint /bin/bash' 19 - /repo-cache/zephyrproject:/github/cache/zephyrproject 21 fail-fast: false 25 ZEPHYR_SDK_INSTALL_DIR: /opt/toolchains/zephyr-sdk-0.16.1 [all …]
|
/Zephyr-Core-3.4.0/doc/develop/getting_started/ |
D | installation_linux.rst | 21 ``http_proxy`` and ``https_proxy`` to get their proxy settings, some 22 use their own configuration files, most notably ``apt`` and 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 [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 16 .. rst-class:: numbered-step 25 .. group-tab:: Ubuntu 29 .. code-block:: bash 31 sudo apt update 32 sudo apt upgrade 34 .. group-tab:: macOS 40 <https://support.apple.com/en-us/HT201541>`_. [all …]
|
/Zephyr-Core-3.4.0/doc/services/tfm/ |
D | requirements.rst | 1 TF-M Requirements 4 The following are some of the boards that can be used with TF-M: 6 .. list-table:: 7 :header-rows: 1 9 * - Board 10 - NSPE board name 11 * - :ref:`mps2_an521_board` 12 - ``mps2_an521_ns`` (qemu supported) 13 * - :ref:`mps3_an547_board` 14 - ``mps3_an547_ns`` (qemu supported) [all …]
|
/Zephyr-Core-3.4.0/doc/develop/toolchains/ |
D | other_x_compilers.rst | 8 GNU-based cross toolchain. 15 toolchain set-up mechanism itself is supported.) 21 For example, you might install the ``gcc-arm-none-eabi`` package on 22 Debian-based Linux systems, or ``arm-none-eabi-newlib`` on Fedora or Red 25 .. code-block:: console 28 sudo apt-get install gcc-arm-none-eabi 30 sudo dnf install arm-none-eabi-newlib 34 - Set :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` to ``cross-compile``. 35 - Set ``CROSS_COMPILE`` to the common path prefix which your 43 .. code-block:: console [all …]
|
/Zephyr-Core-3.4.0/samples/drivers/ethernet/eth_ivshmem/ |
D | README.rst | 3 Inter-VM Shared Memory (ivshmem) Ethernet Sample Application 19 .. code-block:: console 21 git clone https://github.com/siemens/jailhouse-images.git 22 cd jailhouse-images 28 .. code-block:: console 30 ./kas-container menu 32 Edit "start-qemu.sh": 33 * change ``-cpu cortex-a57`` -> ``-cpu cortex-a53`` 35 * Enable SSH access by appending ``,hostfwd=tcp::2222-:22`` to 36 ``-netdev user,id=net`` in the QEMU process arguments [all …]
|
/Zephyr-Core-3.4.0/boards/xtensa/xt-sim/doc/ |
D | index.rst | 1 .. _xt-sim: 10 synthesizable 32-bit RISC processor core. Processor and SOC vendors can select 14 For more information, see https://ip.cadence.com/ipportfolio/tensilica-ip/xtensa-customizable 16 .. figure:: img/xt-sim.jpg 18 :alt: Xtensa Xplorer (Eclipse base frontend for xt-sim) 27 - sample_controller 44 Only Xtensa tools version ``RF-2016.4-linux`` or later are officially 47 In order to set up the Zephyr OS build system, a Linux 32-bit GCC compiler must 51 On Debian/Ubuntu systems, you can install ``gcc-multilib`` package as follows: 53 .. code-block:: console [all …]
|
/Zephyr-Core-3.4.0/doc/connectivity/networking/api/ |
D | coap.rst | 14 protocol for use with constrained nodes and constrained (e.g., low-power, 26 protocol, a simple, low-cost remote management and service enablement mechanism. 33 - `RFC7252: The Constrained Application Protocol (CoAP) <https://tools.ietf.org/html/rfc7252>`_ 34 - `RFC6690: Constrained RESTful Environments (CoRE) Link Format <https://tools.ietf.org/html/rfc669… 35 - `RFC7959: Block-Wise Transfers in the Constrained Application Protocol (CoAP) <https://tools.ietf… 36 - `RFC7641: Observing Resources in the Constrained Application Protocol (CoAP) <https://tools.ietf.… 47 The ``.well-known/core`` resource should be added before all other 48 resources that should be included in the responses of the ``.well-known/core`` 51 .. code-block:: c 54 { .get = well_known_core_get, [all …]
|
/Zephyr-Core-3.4.0/boards/riscv/litex_vexriscv/doc/ |
D | index.rst | 1 .. _litex-vexriscv: 10 <https://github.com/litex-hub/zephyr-on-litex-vexriscv>`_ 11 or `LiteX SoC Builder <https://github.com/enjoy-digital/litex>`_ 14 vendor-specific and open-source tools, including the 19 `Digilent Arty A7-35T or A7-100T Development Boards 20 <https://store.digilentinc.com/arty-a7-artix-7-fpga-development-board-for-makers-and-hobbyists>`_ 21 or `SDI-MIPI Video Converter <https://github.com/antmicro/sdi-mipi-video-converter>`_. 28 `Migen <https://m-labs.hk/gateware/migen/>`_/`MiSoC SoC builder <https://github.com/m-labs/misoc>`_ 29 and provides ready-made system components such as buses, streams, interconnects, 34 `LiteX's website <https://github.com/enjoy-digital/litex>`_. [all …]
|
/Zephyr-Core-3.4.0/doc/develop/optimizations/ |
D | tools.rst | 14 with features available through the compiler, we can also generate worst-case 28 pip3 install git+https://github.com/HBehrens/puncover --user 33 .. zephyr-app-commands:: 40 To view worst-case stack usage analysis, build this with the 43 .. zephyr-app-commands:: 48 :gen-args: -DCONFIG_STACK_USAGE=y 60 .. zephyr-app-commands:: 107 Use the ``rom_report`` to get the ROM report: 109 .. zephyr-app-commands:: 167 Poke-a-hole (pahole) is an object-file analysis tool to find the size of [all …]
|
/Zephyr-Core-3.4.0/boards/riscv/tlsr9518adk80d/doc/ |
D | index.rst | 24 The TLSR9518A SoC integrates a powerful 32-bit RISC-V MCU, DSP, AI Engine, 2.4 GHz ISM Radio, 256 35 - RF conducted antenna 36 - 1 MB External Flash memory with reset button 37 - Chip reset button 38 - Mini USB interface 39 - 4-wire JTAG 40 - 4 LEDs, Key matrix up to 4 keys 41 - 2 line-in function (Dual Analog microphone supported when switching jumper from microphone path) 42 - Dual Digital microphone 43 - Stereo line-out [all …]
|
/Zephyr-Core-3.4.0/boards/posix/native_posix/doc/ |
D | index.rst | 48 .. zephyr-app-commands:: 49 :zephyr-app: samples/hello_world 50 :host-os: unix 62 .. code-block:: console 69 You can run it with the ``--help`` command line switch to get a list of 72 $ ./build/zephyr/zephyr.exe --help 97 code multiple times and get the exact same result. Instrumenting the 101 (e.g., -O0) by setting :kconfig:option:`CONFIG_NO_OPTIMIZATIONS`. 151 LP64 ABI (x86-64 in x86 systems), where pointers and longs are 64 bits. 204 You can do this with the ``--rt`` and ``--no-rt`` options from the command line. [all …]
|
/Zephyr-Core-3.4.0/samples/modules/tflite-micro/magic_wand/train/ |
D | train_magic_wand_model.ipynb | 11 " http://www.apache.org/licenses/LICENSE-2.0\n", 43 "<table class=\"tfo-notebook-buttons\" align=\"left\">\n", 48 …ic_wand_model.ipynb\"><img src=\"https://www.tensorflow.org/images/GitHub-Mark-32px.png\" />View s… 60 …efore you proceed, ensure you are using a GPU runtime by going to **Runtime -> Change runtime type… 96 "!git clone --depth 1 -q https://github.com/tensorflow/tensorflow\n", 98 "!cp -r tensorflow/tensorflow/lite/micro/examples/magic_wand/train train" 126 "!tar xvzf data.tar.gz -C train 1>/dev/null" 161 "id": "5-cmVbFvhTvy" 181 "%tensorboard --logdir logs/scalars" 206 "!python train.py --model CNN --person true" [all …]
|
/Zephyr-Core-3.4.0/boards/xtensa/intel_adsp_cavs25/doc/ |
D | chromebooks_adsp.rst | 3 .. _zephyr-audio-dsp-development-on-chromebooks: 10 arbitrary user-developed firmware like Zephyr applications (of which 30 Hold Esc + Refresh (the arrow-in-a-circle "reload" key above "3") and 53 device ID (for example "DELBIN-XHVI D4B-H4D-G4G-Q9A-A9P" for the Asus 64 Linux's dm-verity feature) all access to the read-only root 66 for a custom kernel) requires that the dm-verity layer be turned off: 68 First open a terminal with Ctrl-Alt-T. Then at the "crosh> " prompt 69 issue the "shell" command to get a shell running as the "chronos" 70 user. Finally (in developer mode) a simple "sudo su -" will get you a 73 .. code-block:: console [all …]
|
/Zephyr-Core-3.4.0/boards/x86/ehl_crb/doc/ |
D | index.rst | 45 .. zephyr-app-commands:: 46 :zephyr-app: samples/hello_world 63 On Windows, open ``File Explorer``, and right-click on the USB flash drive. 72 .. code-block:: console 74 $ mkfs.vfat -F 32 <device-node> 102 .. code-block:: console 111 .. code-block:: console 119 ------------------ 124 ------------------ 128 .. code-block:: console [all …]
|
/Zephyr-Core-3.4.0/boards/arm/npcx9m6f_evb/doc/ |
D | index.rst | 20 - ARM Cortex-M4F Processor 21 - 256 KB RAM and 64 KB boot ROM 22 - ADC & GPIO headers 23 - UART0 and UART1 24 - FAN PWM interface 25 - Jtag interface 26 - Intel Modular Embedded Controller Card (MECC) headers 33 +-----------+------------+-------------------------------------+ 36 | NVIC | on-chip | nested vector interrupt controller | 37 +-----------+------------+-------------------------------------+ [all …]
|
/Zephyr-Core-3.4.0/boards/x86/up_squared/doc/ |
D | index.rst | 18 Up Squared (Credit: https://up-board.org) 35 ---- 39 connected to the on-board FPGA acting as level shifter. Therefore, 69 .. zephyr-app-commands:: 70 :zephyr-app: samples/hello_world 86 <https://wiki.up-community.org/Serial_console>`_ for instructions on how to 91 On Windows, open ``File Explorer``, and right-click on the USB flash drive. 100 .. code-block:: console 102 $ mkfs.vfat -F 32 <device-node> 120 https://wiki.up-community.org/Serial_console. [all …]
|
/Zephyr-Core-3.4.0/doc/contribute/documentation/ |
D | generation.rst | 11 .. _documentation-overview: 18 using Sphinx to create a formatted stand-alone website. Developers can 36 * Doxygen-generated material used to create all API-specific documents 39 * Script-generated material for kernel configuration options based on Kconfig 51 rtd [shape="rectangle" label="read-the-docs\ntheme"] 56 images -> sphinx 57 rst -> sphinx 58 conf -> sphinx 59 header -> doxygen 60 doxygen -> xml [all …]
|
/Zephyr-Core-3.4.0/doc/connectivity/bluetooth/autopts/ |
D | autopts-linux.rst | 1 .. _autopts-linux: 17 - Testing Zephyr Host Stack on QEMU 19 - Testing Zephyr Host Stack on native posix 21 - Testing Zephyr combined (controller + host) build on Real hardware (such as nRF52) 32 https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Command-Line-Tools/Download. 41 - JLink_Linux_V688a_x86_64.deb 43 - nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb 60 --------------- 64 Start -> Settings -> Update & Security -> Windows Update 67 ---------------- [all …]
|
/Zephyr-Core-3.4.0/boards/riscv/rv32m1_vega/doc/ |
D | index.rst | 11 The VEGAboard contains the RV32M1 SoC, featuring two RISC-V CPUs, 12 on-die XIP flash, and a full complement of peripherals, including a 13 2.4 GHz multi-protocol radio. It also has built-in sensors and 14 Arduino-style expansion connectors. 18 :alt: RV32M1-VEGA 20 OpenISA VEGAboard (image copyright: www.open-isa.org) 22 The two RISC-V CPUs are named RI5CY and ZERO-RISCY, and are 24 `RI5CY`_ and `ZERO-RISCY`_. RI5CY is the "main" core; it has more 25 flash and RAM as well as a more powerful CPU design. ZERO-RISCY is a 26 "secondary" core. The main ZERO-RISCY use-case is as a wireless [all …]
|
/Zephyr-Core-3.4.0/doc/develop/application/ |
D | index.rst | 10 …- your **application directory**, :file:`<app>`, is something like :file:`<home>/zephyrproject/app` 11 - its **build directory** is :file:`<app>/build` 19 <important-build-vars>` is set appropriately, though.) 26 The build system is application-centric, and requires Zephyr-based applications 37 application. This directory contains all application-specific files, such as 38 application-specific configuration files and source code. 42 .. code-block:: none 56 such as board-specific configuration files, the ability to run and 60 application-specific changes which should be applied to the base devicetree 69 * **prj.conf**: This is a Kconfig fragment that specifies application-specific [all …]
|
12