Searched +full:- +full:linux +full:- +full:x86_64 (Results 1 – 25 of 60) sorted by relevance
123
| /Zephyr-latest/doc/develop/getting_started/ |
| D | installation_linux.rst | 3 Install Linux Host Dependencies
6 Documentation is available for these Linux distributions:
10 * Clear Linux
11 * Arch Linux
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
[all …]
|
| /Zephyr-latest/doc/develop/toolchains/ |
| D | zephyr_sdk.rst | 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)
31 The Zephyr SDK bundle supports all major operating systems (Linux, macOS and
34 script. Additional OS-specific instructions are described in the sections below.
52 * ``/company/tools/zephyr-sdk-0.13.2``
53 * ``/company/tools/zephyr-sdk-a.b.c``
54 * ``/company/tools/zephyr-sdk-x.y.z``
[all …]
|
| /Zephyr-latest/arch/x86/zefi/ |
| D | README.txt | 5 (NOT a "zephyr.strip" intended for grub/multiboot loading -- we need
18 appropriate locations at startup, clear any zero-filled (BSS, etc...)
32 The code and link environment here is non-obvious. The simple rules
45 Linux toolchain. EFI binaries are relocatable PE-COFF files --
50 independent code. Non-static global variables and function addresses
52 time by a system binary (ld-linux.so). But there is no ld-linux.so in
57 via the x86_64 RIP-relative addressing mode and doesn't rely on any
59 the compiler (not the linker) knows a-priori will never be in
63 You might ask: why build a position-independent executable in the
64 first place? Why not just link to a specific address? The PE-COFF
[all …]
|
| /Zephyr-latest/samples/net/sockets/echo_client/ |
| D | README.rst | 1 .. zephyr:code-sample:: sockets-echo-client
3 :relevant-api: bsd_sockets tls_credentials
10 The echo-client sample application for Zephyr implements a UDP/TCP client
20 - :ref:`networking_with_host`
26 usage scenario is to run echo-client application inside QEMU. This is
30 echo-client directory:
32 - :file:`prj.conf`
35 - :file:`overlay-ot.conf`
38 - :file:`overlay-802154.conf`
44 - :file:`overlay-qemu_802154.conf`
[all …]
|
| /Zephyr-latest/cmake/toolchain/oneApi/ |
| D | generic.cmake | 1 # SPDX-License-Identifier: Apache-2.0
13 set(ONEAPI_LLVM_BIN_PATH ${ONEAPI_TOOLCHAIN_PATH}/compiler/latest/${system}/bin-llvm)
22 set(triple x86_64-pc-none-elf)
24 set(triple i686-pc-none-elf)
27 if(system STREQUAL "linux")
33 # icx compiler of oneApi will invoke clang-cl on windows,
41 list(APPEND CMAKE_REQUIRED_FLAGS --target=${triple})
42 add_compile_options(--target=${triple})
43 add_link_options(--target=${triple})
|
| /Zephyr-latest/arch/posix/ |
| D | CMakeLists.txt | 1 # SPDX-License-Identifier: Apache-2.0
4 message(FATAL_ERROR "The POSIX architecture only works on Linux. If on Windows or macOS "
5 "consider using a virtual machine to run a Linux guest.")
12 # For ex. target_compile_options(native_simulator INTERFACE "-m64")
16 # For ex. target_link_options(native_simulator INTERFACE "-lstdc++")
29 …roperty(TARGET native_simulator APPEND PROPERTY LOCALIZE_EXTRA_OPTIONS "--localize-symbol=spinel*")
45 else() # Linux.x86_64
47 # some gcc versions fail to build without -fPIC
48 zephyr_compile_options(-m64 -fPIC)
49 zephyr_link_libraries(-m64)
[all …]
|
| /Zephyr-latest/boards/native/native_posix/doc/ |
| D | index.rst | 21 which will set its configuration to mimic a native_posix-like configuration.
25 with the Zephyr kernel, creating a normal Linux executable with your host tooling,
26 and can debug and instrument it like any other Linux program.
64 .. zephyr-app-commands::
65 :zephyr-app: samples/hello_world
66 :host-os: unix
71 Now you have a Linux executable, ``./build/zephyr/zephyr.exe``, you can use just like any
72 other Linux program.
86 your code for the ILP32 ABI (i386 in a x86 or x86_64 system) where pointers
95 LP64 ABI (x86-64 in x86 systems), where pointers and longs are 64 bits.
|
| /Zephyr-latest/snippets/xen_dom0/ |
| D | README.rst | 16 * add correct memory and hypervisor nodes, based on regions Xen picked for Domain-0 on your setup.
25 .. code-block:: console
27 west build -b qemu_cortex_a53 -S xen_dom0 samples/synchronization
37 * fetch and build Xen (e.g. RELEASE-4.17.0) for arm64 platform
43 .. code-block:: console
45 <path to Zephyr SDK>/sysroots/x86_64-pokysdk-linux/usr/bin/qemu-system-aarch64 -cpu cortex-a53 \
46 -m 6G -nographic -machine virt,gic-version=3,virtualization=true -chardev stdio,id=con,mux=on \
47 -serial chardev:con -mon chardev=con,mode=readline -pidfile qemu.pid \
48 -device loader,file=<path to Zephyr app build>/zephyr.bin,addr=0x40600000 \
49 -dtb <path to DTB>/xen.dtb -kernel <path to Xen build>/xen
[all …]
|
| /Zephyr-latest/samples/subsys/debug/fuzz/ |
| D | README.rst | 1 .. zephyr:code-sample:: fuzzing
21 .. code-block:: console
23 $ clang --version
25 Target: x86_64-pc-linux-gnu
29 $ west build -t run -b native_sim/native/64 samples/subsys/debug/fuzz
31 Over 10-20 seconds or so (runtimes can be quite variable) you will see
38 .. code-block:: console
40 -- west build: running target run
44 INFO: Loaded 1 modules (2112 inline 8-bit counters): 2112 [0x55cbe336ec55, 0x55cbe336f495),
46 INFO: -max_len is not provided; libFuzzer will not generate inputs larger than 4096 bytes
[all …]
|
| /Zephyr-latest/boards/ti/msp_exp432p401r_launchxl/doc/ |
| D | index.rst | 6 The SimpleLink MSP‐EXP432P401R LaunchPad development kit is an easy-to-use evaluation
8 developing on the SimpleLink MSP432 low-power + performance ARM |reg| 32-bit Cortex |reg|-M4F
14 * Low-power ARM Cortex-M4F MSP432P401R
15 * 40-pin LaunchPad development kit standard that leverages the BoosterPack plug-in module ecosystem
16 * XDS110-ET, an open-source onboard debug probe featuring EnergyTrace+ technology and application
21 Details on the MSP-EXP432P401R LaunchXL development board can be found in the
22 MSP-EXP432P401R LaunchXL User's Guide.
27 * The on-board 32-kHz crystal allows for lower LPM3 sleep currents and a higher-precision clock sou…
28 …default internal 32-kHz REFOCLK. Therefore, the presence of the crystal allows the full range of l…
30 * The on-board 48-MHz crystal allows the device to run at its maximum operating speed for MCLK and …
[all …]
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | chromebooks_adsp.rst | 1 .. _zephyr-audio-dsp-development-on-chromebooks:
8 arbitrary user-developed firmware like Zephyr applications (of which
28 Hold Esc + Refresh (the arrow-in-a-circle "reload" key above "3") and
51 device ID (for example "DELBIN-XHVI D4B-H4D-G4G-Q9A-A9P" for the Asus
62 Linux's dm-verity feature) all access to the read-only root
64 for a custom kernel) requires that the dm-verity layer be turned off:
66 First open a terminal with Ctrl-Alt-T. Then at the "crosh> " prompt
68 user. Finally (in developer mode) a simple "sudo su -" will get you a
71 .. code-block:: console
74 chronos@localhost / $ sudo su -
[all …]
|
| /Zephyr-latest/samples/drivers/ipm/ipm_ivshmem/ |
| D | README.rst | 1 .. zephyr:code-sample:: ipm-ivshmem
3 :relevant-api: ipm_interface
5 Implement inter-processor mailbox (IPM) over IVSHMEM (Inter-VM shared memory)
12 ivshmem-server needs to be available and running. The server is available in
13 Zephyr SDK or pre-built in some distributions. Otherwise, it is available in
16 ivshmem-client needs to be available as it is employed in this sample as an
17 external application. The same conditions of ivshmem-server apply to the
18 ivshmem-server, as it is also available via QEMU.
22 #. The ivshmem-server utility for QEMU can be found into the Zephyr SDK
24 ``/path/to/your/zephyr-sdk/zephyr-<version>/sysroots/x86_64-pokysdk-linux/usr/xilinx/bin/``
[all …]
|
| /Zephyr-latest/boards/ti/cc1352p7_launchpad/doc/ |
| D | index.rst | 6 The Texas Instruments CC1352P7 LaunchPad |trade| (LP-CC1352P7) is a
7 development kit for the SimpleLink |trade| multi-Standard CC1352P7 wireless MCU.
20 The CC1352P7 wireless MCU has a 48 MHz Arm |reg| Cortex |reg|-M4F SoC and an
21 integrated sub-1GHz and 2.4 GHz transceiver with integrated 20dBm power amplifier
33 +-----------+------------+----------------------+
36 | GPIO | on-chip | gpio |
37 +-----------+------------+----------------------+
38 | MPU | on-chip | arch/arm |
39 +-----------+------------+----------------------+
40 | NVIC | on-chip | arch/arm |
[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
11 .. _python-pip:
22 ``--user`` flag to the ``pip3`` command when installing new packages. This is
25 information about pip\ [#pip]_, including `information on -\\-user`_.
27 - On Linux, make sure ``~/.local/bin`` is at the front of your :envvar:`PATH`
28 :ref:`environment variable <env_vars>`, or programs installed with ``--user``
29 won't be found. Installing with ``--user`` avoids conflicts between pip
30 and the system package manager, and is the default on Debian-based
[all …]
|
| /Zephyr-latest/doc/ |
| D | conf.py | 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 --------------------------------------------------------------
38 copyright = "2015-2024 Zephyr Project members and individual contributors"
62 version += "-" + extra
70 # -- General configuration ------------------------------------------------
82 "zephyr.dtcompatible-role",
83 "zephyr.link-roles",
103 if tags.has("convertimages"): # pylint: disable=undefined-variable # noqa: F821
[all …]
|
| /Zephyr-latest/boards/ti/cc3235sf_launchxl/doc/ |
| D | index.rst | 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
40 offloads Wi-Fi and internet protocols from the application MCU.
[all …]
|
| /Zephyr-latest/boards/ti/cc3220sf_launchxl/doc/ |
| D | index.rst | 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
40 offloads Wi-Fi and internet protocols from the application MCU.
[all …]
|
| /Zephyr-latest/boards/native/native_sim/doc/ |
| D | index.rst | 3 Native simulator - native_sim
16 the Zephyr kernel, and libraries, creating a normal Linux executable.
63 .. zephyr-app-commands::
64 :zephyr-app: samples/hello_world
65 :host-os: unix
75 Run the ``zephyr.exe`` executable as you would any other Linux console application.
77 .. code-block:: console
84 You can run it with the ``--help`` command line switch to get a list of
87 .. code-block:: console
89 $ ./build/zephyr/zephyr.exe --help
[all …]
|
| /Zephyr-latest/scripts/west_commands/ |
| D | sdk.py | 3 # SPDX-License-Identifier: Apache-2.0
42 See 'west sdk list --help' for details.
48 See 'west sdk install --help' for details.
82 Set --version option to install a specific version of the SDK.
86 You can specify the installation directory with --install-dir or --install-base.
89 --install-dir and --install-base.
91 Typically, Zephyr SDK archives contain only one directory named zephyr-sdk-<version>
93 … The SDK archive is extracted to the home directory if both --install-dir and --install-base
95 In this case, SDK will install into ${HOME}/zephyr-sdk-<version>.
96 … If --install-base is specified, the archive will be extracted under the specified path.
[all …]
|
| /Zephyr-latest/boards/snps/emsdp/doc/ |
| D | index.rst | 7 for rapid software development on ARC EM processor-based subsystems. It is intended
9 a wide range of ultra-low power embedded applications such as IoT, sensor fusion,
13 (EM SDP) <https://www.synopsys.com/dw/ipdir.php?ds=arc-em-software-development-platform>`__
27 +-----------+-----+-----+------+------+----------+------+-------+
31 +-----------+-----+-----+------+------+----------+------+-------+
33 +-----------+-----+-----+------+------+----------+------+-------+
35 +-----------+-----+-----+------+------+----------+------+-------+
37 +-----------+-----+-----+------+------+----------+------+-------+
41 +-----------+------------+-------+-----------------------+
44 | SDIO | on-chip | N | SD-card controller |
[all …]
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-2.2.rst | 18 * Fix CVE-2020-10028
19 * Fix CVE-2020-10060
20 * Fix CVE-2020-10063
21 * Fix CVE-2020-10066
32 * :github:`23494` - Bluetooth: LL/PAC/SLA/BV-01-C fails if Slave-initiated Feature Exchange is disa…
33 * :github:`23485` - BT: host: Service Change indication sent regardless of whether it is needed or …
34 * :github:`23482` - 2M PHY + DLE and timing calculations on an encrypted link are wrong
35 * :github:`23070` - Bluetooth: controller: Fix ticker implementation to avoid catch up
36 * :github:`22967` - Bluetooth: controller: ASSERTION FAIL on invalid packet sequence
37 * :github:`24183` - [v2.2] Bluetooth: controller: split: Regression slave latency during connection…
[all …]
|
| /Zephyr-latest/boards/native/doc/ |
| D | bsim_boards_design.rst | 22 and execute the embedded code natively on Linux.
50 The main purpose of these bsim boards is to be test-benches for
80 - Unit tests:
85 - Integration tests on real HW: Allows testing with the real SW
93 - Integration tests on workstation (what the POSIX arch and these boards enable)
95 - Using bsim boards: Allow testing the embedded SW (or a subset), including
98 - Using bsim boards with the BabbleSim Physical layer simulation allows
102 - Using bsim boards, and the `EDTT`_ framework: With the EDTT framework we can
108 - Using Zephyr's :ref:`native_sim <native_sim>` board: It also allows integration testing of
116 - Zephyr's ztest infrastructure and Zephyr's twister:
[all …]
|
| /Zephyr-latest/boards/ti/cc1352r1_launchxl/doc/ |
| D | index.rst | 6 The Texas Instruments CC1352R LaunchPad |trade| (LAUNCHXL-CC1352R1) is a
7 development kit for the SimpleLink |trade| multi-Standard CC1352R wireless MCU.
18 The CC13522 wireless MCU has a 48 MHz Arm |reg| Cortex |reg|-M4F SoC and an
19 integrated Sub-1 and 2.4 GHz transceiver supporting multiple protocols including
30 +-----------+------------+----------------------+
33 | GPIO | on-chip | gpio |
34 +-----------+------------+----------------------+
35 | MPU | on-chip | arch/arm |
36 +-----------+------------+----------------------+
37 | NVIC | on-chip | arch/arm |
[all …]
|
| /Zephyr-latest/boards/ti/cc1352p1_launchxl/doc/ |
| D | index.rst | 6 The Texas Instruments CC1352P LaunchPad |trade| (LAUNCHXL-CC1352P1) is a
7 development kit for the SimpleLink |trade| multi-Standard CC1352P wireless MCU.
19 The CC1352P wireless MCU has a 48 MHz Arm |reg| Cortex |reg|-M4F SoC and an
20 integrated sub-1GHz and 2.4 GHz transceiver with integrated 20dBm power amplifier
32 +-----------+------------+----------------------+
35 | GPIO | on-chip | gpio |
36 +-----------+------------+----------------------+
37 | MPU | on-chip | arch/arm |
38 +-----------+------------+----------------------+
39 | NVIC | on-chip | arch/arm |
[all …]
|
| /Zephyr-latest/doc/build/dts/ |
| D | zephyr_dt_i2c_high_level.svg | 1 <?xml version="1.0" encoding="UTF-8"?>
2 <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
3 …-color: rgb(255, 255, 255);" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" width="429px…
|
123
