| /Zephyr-latest/doc/build/dts/ |
| D | bindings-upstream.rst | 1 .. _dt-writing-bindings:
21 Zephyr aims for devicetree :ref:`dt-source-compatibility`. Therefore, if there
24 justify any Zephyr-specific divergences.
28 - There is an existing binding in the mainline Linux kernel. See
30 bindings and the `Linux devicetree documentation`_ for more information.
32 - Your hardware vendor provides an official binding outside of the Linux
36 https://github.com/torvalds/linux/
45 the same `design guidelines laid out by Linux`_.
47 .. _design guidelines laid out by Linux:
48 https://docs.kernel.org/devicetree/bindings/writing-bindings.html
[all …]
|
| D | bindings.rst | 1 .. _dt-bindings:
13 dt-schema tools used by the Linux kernel).
15 These pages introduce bindings, describe what they do, note where they are
26 bindings-intro.rst
27 bindings-syntax.rst
28 bindings-upstream.rst
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | installation_win.rst | 1 .. _win-setup-alts:
6 .. _win-wsl:
8 Windows 10 WSL (Windows Subsystem for Linux)
12 built-in functionality to natively run Ubuntu binaries directly on a standard
13 command-prompt. This allows you to use software such as the :ref:`Zephyr SDK
21 #. `Install the Windows Subsystem for Linux (WSL)`_.
32 .. NOTE FOR DOCS AUTHORS: as a reminder, do *NOT* put dependencies for building
35 .. _Install the Windows Subsystem for Linux (WSL): https://msdn.microsoft.com/en-us/commandline/wsl… argument
|
| 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/samples/net/sockets/websocket_client/ |
| D | README.rst | 1 .. zephyr:code-sample:: sockets-websocket-client
3 :relevant-api: bsd_sockets websocket
10 This sample application implements a Websocket client that will do an HTTP
20 - :ref:`networking_with_host`
28 Build websocket-client sample application like this:
30 .. zephyr-app-commands::
31 :zephyr-app: samples/net/sockets/websocket_client
41 ``overlay-tls.conf`` overlay file enabled using these commands:
43 .. zephyr-app-commands::
44 :zephyr-app: samples/net/sockets/websocket_client
[all …]
|
| /Zephyr-latest/samples/net/gptp/ |
| D | Kconfig | 4 # SPDX-License-Identifier: Apache-2.0
7 # gPTP protocol will run in the non-VLAN interface and then there
9 # how to do this kind of setup. See also VLAN sample application
10 # for vlan-setup-linux.sh script that can be used to setup the
11 # VLAN IP addressing in Linux side (if that is desired).
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-dev.rst | 1 .. _bluetooth-dev:
26 .. _bluetooth-hw-setup:
38 #. :ref:`Embedded <bluetooth-hw-setup-embedded>`
39 #. :ref:`External controller <bluetooth-hw-setup-external-ll>`
41 - :ref:`QEMU host <bluetooth-hw-setup-qemu-host>`
42 - :ref:`native_sim host <bluetooth-hw-setup-native-sim-host>`
44 #. :ref:`Simulated nRF5x with BabbleSim <bluetooth-hw-setup-bsim>`
46 .. _bluetooth-hw-setup-embedded:
53 All the :ref:`bluetooth-configs` and :ref:`bluetooth-build-types` are supported
54 but you might need to build Zephyr more than once if you are using a dual-chip
[all …]
|
| /Zephyr-latest/drivers/can/ |
| D | can_native_linux_adapt.c | 5 * SPDX-License-Identifier: Apache-2.0
22 /* Linux host include files. */
30 #include <linux/if.h>
31 #include <linux/can.h>
32 #include <linux/can/raw.h>
34 #error "This driver can only be built on Linux systems"
40 /* Linux kernels before v5.14 do not define CANFD_FDF */
48 int fd, opt, ret = -EINVAL; in linux_socketcan_iface_open()
52 return -errno; in linux_socketcan_iface_open()
58 strncpy(ifr.ifr_name, if_name, IFNAMSIZ - 1); in linux_socketcan_iface_open()
[all …]
|
| /Zephyr-latest/samples/bluetooth/hci_uart_async/ |
| D | README.rst | 1 .. zephyr:code-sample:: bluetooth_hci_uart_async
3 :relevant-api: hci_raw bluetooth uart_interface
40 controller and expose it to Linux's BlueZ.
52 .. zephyr-app-commands::
53 :zephyr-app: samples/bluetooth/hci_uart_async
57 .. _bluetooth-hci-uart-async-qemu-posix:
63 to attach it to the Linux Host first. To do so simply build the sample and
64 connect the UART to the Linux machine, and then attach it with this command:
66 .. code-block:: console
68 sudo btattach -B /dev/ttyACM0 -S 1000000 -R
[all …]
|
| /Zephyr-latest/samples/net/sockets/http_client/ |
| D | README.rst | 1 .. zephyr:code-sample:: sockets-http-client
3 :relevant-api: bsd_sockets http_client tls_credentials secure_sockets_options
10 This sample application implements an HTTP(S) client that will do an HTTP
19 - :ref:`networking_with_host`
27 Build the http-client sample application like this:
29 .. zephyr-app-commands::
30 :zephyr-app: samples/net/sockets/http_client
40 ``overlay-tls.conf`` overlay file enabled using these commands:
42 .. zephyr-app-commands::
43 :zephyr-app: samples/net/sockets/http_client
[all …]
|
| /Zephyr-latest/samples/bluetooth/hci_uart_3wire/ |
| D | README.rst | 1 .. zephyr:code-sample:: bluetooth_hci_uart_3wire
2 :name: HCI 3-wire (H:5)
3 :relevant-api: hci_raw bluetooth uart_interface
37 controller and expose it to Linux's BlueZ. This can be very useful for testing
39 provide a modern Bluetooth LE 5.0 controller to a Linux-based machine for native
40 BLE support or QEMU-based development.
52 .. zephyr-app-commands::
53 :zephyr-app: samples/bluetooth/hci_uart_3wire
57 .. _bluetooth-hci-uart-3wire-qemu-posix:
63 need to attach it to the Linux Host first. To do so simply build the sample and
[all …]
|
| /Zephyr-latest/samples/bluetooth/hci_uart/ |
| D | README.rst | 1 .. zephyr:code-sample:: bluetooth_hci_uart
3 :relevant-api: hci_raw bluetooth uart_interface
37 controller and expose it to Linux's BlueZ. This can be very useful for testing
39 provide a modern Bluetooth LE 5.0 controller to a Linux-based machine for native
40 BLE support or QEMU-based development.
52 .. zephyr-app-commands::
53 :zephyr-app: samples/bluetooth/hci_uart
57 .. _bluetooth-hci-uart-qemu-posix:
63 to attach it to the Linux Host first. To do so simply build the sample and
64 connect the UART to the Linux machine, and then attach it with this command:
[all …]
|
| /Zephyr-latest/doc/develop/ |
| D | env_vars.rst | 6 Various pages in this documentation refer to setting Zephyr-specific
13 -------------------
20 .. group-tab:: Linux/macOS
22 .. code-block:: console
26 .. group-tab:: Windows
28 .. code-block:: console
41 --------------------------
45 .. group-tab:: Linux/macOS
48 your home directory. For Bash, this is usually :file:`~/.bashrc` on Linux
53 .. group-tab:: Windows
[all …]
|
| /Zephyr-latest/dts/arm/renesas/rcar/gen4/ |
| D | r8a779f0.dtsi | 4 * SPDX-License-Identifier: Apache-2.0
8 #include <zephyr/dt-bindings/gpio/gpio.h>
9 #include <zephyr/dt-bindings/clock/r8a779f0_cpg_mssr.h>
17 pfc: pin-controller@e6050000 {
18 compatible = "renesas,rcar-pfc";
26 * Using domain 0 as Linux
28 cpg: clock-controller@e6150000 {
29 compatible = "renesas,r8a779f0-cpg-mssr";
31 #clock-cells = <2>;
35 compatible = "renesas,rcar-gpio";
[all …]
|
| /Zephyr-latest/boards/microchip/mec172xevb_assy6906/support/ |
| D | mec172x_remote_flasher.py | 5 # SPDX-License-Identifier: Apache-2.0
12 west flash -r misc-flasher -- mec172x_remote_flasher.py <remote host>
17 to setup public key authentication and ssh-agent.
27 - connected: true
32 runner: misc-flasher
34 - <ZEPHYR_BASE>/boards/microchip/mec172xevb_assy6906/support/mec172x_remote_flasher.py
35 - <remote host>
42 ./scripts/twister --hardware-map <hw map file> --device-testing
76 sha256.update(now.encode("utf-8"))
94 remote.add_argument("--remote-tmp", required=False,
[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/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/soc/mediatek/mt8xxx/ |
| D | mbox.c | 2 * SPDX-License-Identifier: Apache-2.0
12 /* Mailbox: a simple interrupt source. Each direction has a 5-bit
14 * non-zero. The interrupt bits get cleared/acknowledged by writing
23 * There is an array of the devices. Linux's device-tree defines two.
25 * using the third (no linux driver though?). The upstream headers
36 * aren't used by the Linux kernel at all (which has a single driver
38 * otherwise ignored. In practice they don't do anything that simple
71 struct mbox_data *data = ((struct device *)mbox)->data; in mtk_adsp_mbox_set_handler()
74 data->handlers[chan] = handler; in mtk_adsp_mbox_set_handler()
75 data->handler_arg[chan] = arg; in mtk_adsp_mbox_set_handler()
[all …]
|
| /Zephyr-latest/boards/gardena/sgrm/doc/ |
| D | index.rst | 9 .. _FOSS parts: https://github.com/husqvarnagroup/smart-garden-gateway-public
14 - Silicon Labs SiM3U167-B-GM_ SoC
15 - Silicon Labs Si4467_ transceiver (via SPI)
16 - Controls an RGB LED via high drive pins. It's expected to mirror the state of 3 low-drive pins
17 coming from the Linux SoC.
18 - UART is connected to the Linux SoC. Usually it's used for PPP, but it can also be used for
21 .. _SiM3U167-B-GM: https://www.silabs.com/mcu/32-bit-microcontrollers/precision32-sim3u1xx/device.S…
22 .. _Si4467: https://www.silabs.com/wireless/proprietary/ezradiopro-sub-ghz-ics/device.si4467?tab=sp…
29 +-----------+------------+-------------------------------------+
32 | NVIC | on-chip | nested vector interrupt controller |
[all …]
|
| /Zephyr-latest/samples/net/dhcpv4_client/ |
| D | README.rst | 1 .. zephyr:code-sample:: dhcpv4-client
3 :relevant-api: dhcpv4 net_mgmt
17 - :ref:`networking_with_host`
22 Running DHCPv4 client in Linux Host
26 QEMU on a Linux host to negotiate IP address from DHCPv4 server (kea) running
27 on Linux host.
31 Here's a sample server configuration file '/etc/kea/kea-dhcp4.conf'
34 .. code-block:: console
38 "interfaces-config": {
40 "dhcp-socket-type": "raw"
[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/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
49 You can actually do this on any machine (and any OS) with Chrome
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
[all …]
|
| /Zephyr-latest/tests/net/lib/coap_client/src/ |
| D | stubs.h | 4 * SPDX-License-Identifier: Apache-2.0
24 /* ZSOCK_POLL* values are compatible with Linux */
51 do { \
|
| /Zephyr-latest/boards/microchip/mec172xmodular_assy6930/doc/ |
| D | mec172xmodular_assy6930.rst | 12 - MEC172x (MEC1723, MEC1727 and MEC1728) ARM Cortex-M4 Processor
13 - 416 KB RAM and 128 KB boot ROM
14 - UART1 using microUSB
15 - PECI interface 3.0
16 - FAN, PWM and TACHO pins
17 - 5 SMBus instances
18 - eSPI header
19 - VCI interface
20 - 1 hardware driven PS/2 ports
21 - Keyboard interface headers
[all …]
|
| /Zephyr-latest/doc/connectivity/bluetooth/autopts/ |
| D | autopts-linux.rst | 1 .. _autopts-linux:
3 AutoPTS on Linux
6 This tutorial shows how to setup AutoPTS client on Linux with AutoPTS server running on Windows 10
7 virtual machine. Tested with Ubuntu 20.4 and Linux Mint 20.4.
14 - Testing Zephyr Host Stack on QEMU
16 - Testing Zephyr Host Stack on :ref:`native_sim <native_sim>`
18 - Testing Zephyr combined (controller + host) build on Real hardware (such as nRF52)
26 Setup Linux
33 https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Command-Line-Tools/Download.
42 - JLink_Linux_V688a_x86_64.deb
[all …]
|
