| /Zephyr-latest/samples/subsys/usb/hid-keyboard/ |
| D | README.rst | 1 .. zephyr:code-sample:: usb-hid-keyboard
3 :relevant-api: usbd_api usbd_hid_device input_interface
17 :ref:`input` API. There must be a :dtcompatible:`gpio-keys` group of buttons
19 At least one key is required and up to four can be used. The first three keys
23 The example can use up to three LEDs, configured via the devicetree alias such
24 as ``led0``, to indicate the state of the keyboard LEDs.
32 .. zephyr-app-commands::
33 :zephyr-app: samples/subsys/usb/hid-keyboard
|
| /Zephyr-latest/dts/bindings/dac/ |
| D | adi,ad569x-base.yaml | 2 # SPDX-License-Identifier: Apache-2.0
4 include: [dac-controller.yaml]
7 "#io-channel-cells":
10 voltage-reference:
14 - "internal"
15 - "external"
18 - Internal voltage reference - 2.5V (reg: 0).
19 - External voltage reference (reg: 1).
24 default: "gain-1"
26 - "gain-1"
[all …]
|
| /Zephyr-latest/dts/bindings/memory-controllers/ |
| D | st,stm32h7-fmc.yaml | 2 # SPDX-License-Identifier: Apache-2.0
7 The FMC allows to interface with static-memory mapped external devices such as
14 The flexible memory controller includes three memory controllers:
16 - NOR/PSRAM memory controller
17 - NAND memory controller (some devices also support PC Card)
18 - Synchronous DRAM (SDRAM/Mobile LPSDR SDRAM) controller
27 pinctrl-0 = <&fmc_nbl0_pe0 &fmc_nbl1_pe1 &fmc_nbl2_pi4...>;
30 compatible: "st,stm32h7-fmc"
32 include: ["st,stm32-fmc.yaml"]
35 st,mem-swap:
[all …]
|
| /Zephyr-latest/doc/services/smf/ |
| D | index.rst | 3 State Machine Framework
11 The State Machine Framework (SMF) is an application agnostic framework that
12 provides an easy way for developers to integrate state machines into their
16 State Creation
19 A state is represented by three functions, where one function implements the
23 defined structure that has the state machine context, :c:struct:`smf_ctx`, as
31 The :c:struct:`smf_ctx` member must be first because the state machine
38 By default, a state can have no ancestor states, resulting in a flat state
39 machine. But to enable the creation of a hierarchical state machine, the
42 By default, the hierarchical state machines do not support initial transitions
[all …]
|
| /Zephyr-latest/dts/bindings/regulator/ |
| D | regulator-gpio.yaml | 2 # SPDX-License-Identifier: Apache-2.0
5 GPIO-controlled voltage of regulators
8 vccq_sd0: regulator-vccq-sd0 {
9 compatible = "regulator-gpio";
11 regulator-name = "SD0 VccQ";
12 regulator-min-microvolt = <1800000>;
13 regulator-max-microvolt = <3300000>;
15 enable-gpios = <&gpio5 3 GPIO_ACTIVE_HIGH>;
20 regulator-boot-on;
23 In the above example, three GPIO pins are used for controlling the regulator:
[all …]
|
| /Zephyr-latest/samples/subsys/smf/smf_calculator/ |
| D | README.rst | 1 .. zephyr:code-sample:: smf_calculator
3 :relevant-api: smf
5 Create a simple desk calculator using the State Machine Framework.
10 This sample creates a basic desk calculator driven by a state machine written
11 with the :ref:`State Machine Framework <smf>`.
15 This uses a three-layer hierarchical statechart to handle situations such as
19 screen in the ``op_entered`` state depending on if a previous result is
25 :figclass: align-center
30 output, based on the sample in samples/drivers/display. The state machine updates
34 on RAM-constrained boards like the :zephyr:board:`disco_l475_iot1`.
[all …]
|
| /Zephyr-latest/dts/bindings/power/ |
| D | atmel,sam-supc.yaml | 2 # SPDX-License-Identifier: Apache-2.0
5 Atmel SAM SUPC (Supply-Controller) controller
8 monitoring of the device. It have a special feature that it can wake-up the
9 device from a low-power state using special peripherals as wake-up sources.
11 The dedicated peripherals that can wake-up the core supply domain are: RTC,
12 RTT, Supply Monitor and GPIOs. In the first three peripherals it is necessary
13 inform the wakeup-source-id property on their respective nodes.
17 wakeup-source-id = <&supc SUPC_WAKEUP_SOURCE_RTC>;
21 The special peripheral will wake-up the device only when the standard property
22 wakeup-source is defined, e.g.:
[all …]
|
| /Zephyr-latest/scripts/dts/python-devicetree/tests/ |
| D | test.dts | 4 * SPDX-License-Identifier: BSD-3-Clause
9 /dts-v1/;
16 interrupt-parent-test {
18 compatible = "interrupt-three-cell";
19 #interrupt-cells = <3>;
20 interrupt-controller;
24 interrupt-names = "foo", "bar";
25 interrupt-parent = <&{/interrupt-parent-test/controller}>;
28 interrupts-extended-test {
29 controller-0 {
[all …]
|
| /Zephyr-latest/tests/drivers/watchdog/wdt_basic_api/src/ |
| D | test_wdt.c | 4 * SPDX-License-Identifier: Apache-2.0
14 * There are three tests. Each test provide watchdog installation, setup and
15 * wait for reset. Three variables are placed in noinit section to prevent
17 * test case, current test state and value to check if test passed or not.
19 * - Test Steps - test_wdt_no_callback
20 * -# Get device.
21 * -# Check if the state was changed and test should be finished.
22 * -# Set callback to NULL value.
23 * -# Install watchdog with current configuration.
24 * -# Setup watchdog with no additions options.
[all …]
|
| /Zephyr-latest/tests/subsys/pm/power_domain/src/ |
| D | main.c | 4 * SPDX-License-Identifier: Apache-2.0
42 rc = -ENOTSUP; in domain_pm_action()
56 testing_domain_on_notitication--; in deva_pm_action()
60 testing_domain_off_notitication--; in deva_pm_action()
68 * Device B will return -ENOTSUP for TURN_ON and TURN_OFF actions.
69 * This way we can check if the subsystem properly handled its state.
80 ret = -ENOTSUP; in devb_pm_action()
81 testing_domain_on_notitication--; in devb_pm_action()
85 ret = -ENOTSUP; in devb_pm_action()
86 testing_domain_off_notitication--; in devb_pm_action()
[all …]
|
| /Zephyr-latest/samples/boards/phytec/reel_board/mesh_badge/ |
| D | README.rst | 1 .. zephyr:code-sample:: mesh_badge
3 :relevant-api: monochrome_character_framebuffer bt_mesh bt_gatt bluetooth
23 #. Connect to the device. You'll see a single service - select it
29 allows three rows of up to 12 characters
31 #. Press "Send" - this will trigger pairing since this is a protected
46 To reset a board to its initial state (disable mesh, erase the stored
|
| /Zephyr-latest/doc/project/ |
| D | code_flow.rst | 1 .. _code-flow-and-branches:
9 The zephyr Git repository has three types of branches:
12 Which contains the latest state of development
14 collab-\*
23 vx.y-branch
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.
56 - Force pushing a collaboration branch is only allowed when rebasing against the main branch.
57 - Review changes coming from team members and request review from branch owners
[all …]
|
| /Zephyr-latest/subsys/usb/usb_c/ |
| D | usbc_tc_snk_states.c | 4 * SPDX-License-Identifier: Apache-2.0
20 struct usbc_port_data *data = dev->data; in sink_power_sub_states()
24 struct tc_sm_t *tc = data->tc; in sink_power_sub_states()
27 cc = tc->cc_polarity ? tc->cc2 : tc->cc1; in sink_power_sub_states()
31 * This sub-state supports Sinks consuming current within the in sink_power_sub_states()
32 * lowest range (default) of Source-supplied current. in sink_power_sub_states()
38 * This sub-state supports Sinks consuming current within the in sink_power_sub_states()
39 * two lower ranges (default and 1.5 A) of Source-supplied in sink_power_sub_states()
46 * This sub-state supports Sinks consuming current within all in sink_power_sub_states()
47 * three ranges (default, 1.5 A and 3.0 A) of Source-supplied in sink_power_sub_states()
[all …]
|
| /Zephyr-latest/samples/subsys/modbus/tcp_server/ |
| D | README.rst | 1 .. zephyr:code-sample:: modbus-tcp-server
3 :relevant-api: modbus bsd_sockets
16 This sample has been tested with FRDM-K64F board,
18 Additionally the board should have three LEDs.
34 .. zephyr-app-commands::
35 :zephyr-app: samples/subsys/modbus/tcp_server
43 .. code-block:: console
45 # pymodbus.console tcp --host 192.0.2.1 --port 502
50 .. code-block:: console
57 .. code-block:: console
[all …]
|
| /Zephyr-latest/boards/st/nucleo_wba52cg/doc/ |
| D | nucleo_wba52cg.rst | 6 NUCLEO-WBA52CG is a Bluetooth® Low Energy wireless and ultra-low-power board
7 embedding a powerful and ultra-low-power radio compliant with the Bluetooth®
14 - Ultra-low-power wireless STM32WBA52CG microcontroller based on the Arm®
18 - MCU RF board (MB1863):
20 - 2.4 GHz RF transceiver supporting Bluetooth® specification v5.3
21 - Arm® Cortex® M33 CPU with TrustZone®, MPU, DSP, and FPU
22 - Integrated PCB antenna
24 - Three user LEDs
25 - Three user and one reset push-buttons
27 - Board connectors:
[all …]
|
| /Zephyr-latest/subsys/net/l2/wifi/ |
| D | Kconfig | 2 # SPDX-License-Identifier: Apache-2.0
39 even when it is awake intervals. Rejecting TWT setup till Wi-Fi
43 bool "Force passive Wi-Fi scanning"
64 There are approximately 100 channels allocated across the three supported bands.
68 int "Maximum number of APs and STAs that can be managed in Wi-Fi shell"
73 in Wi-Fi shell.
76 bool "Wi-Fi Network manager support"
78 This option enables using the Wi-Fi Network managers (e.g. wpa_supplicant) to
79 manage the Wi-Fi network interfaces.
84 int "Maximum number of managed interfaces per Wi-Fi network manager"
[all …]
|
| /Zephyr-latest/doc/security/ |
| D | reporting.rst | 16 .. _GitHub: https://github.com/zephyrproject-rtos/zephyr/security
41 init -> New;
42 New -> Triage;
43 Triage -> Rejected [dir = both];
44 Triage -> Assigned;
45 Assigned -> Review [dir = both];
46 Review -> Accepted;
47 Review -> Rejected;
48 Accepted -> Public;
52 - New: This state represents new reports that have been entered
[all …]
|
| /Zephyr-latest/boards/st/nucleo_wba55cg/doc/ |
| D | nucleo_wba55cg.rst | 6 NUCLEO-WBA55CG is a Bluetooth® Low Energy wireless and ultra-low-power board
7 embedding a powerful and ultra-low-power radio compliant with the Bluetooth®
14 - Ultra-low-power wireless STM32WBA55CG microcontroller based on the Arm®
18 - MCU RF board (MB1863):
20 - 2.4 GHz RF transceiver supporting Bluetooth® specification v5.3
21 - Arm® Cortex® M33 CPU with TrustZone®, MPU, DSP, and FPU
22 - Integrated PCB antenna
24 - Three user LEDs
25 - Three user and one reset push-buttons
27 - Board connectors:
[all …]
|
| /Zephyr-latest/dts/bindings/gpio/ |
| D | adi,max14916-gpio.yaml | 3 # SPDX-License-Identifier: Apache-2.0
7 compatible: "adi,max14916-gpio"
10 "#gpio-cells":
17 drdy-gpios:
19 High-Side Open-Drain Output. READY is passive low when the internal
22 type: phandle-array
23 fault-gpios:
25 Fault pin indicates when there is Fault state in either FAULT1 or FAULT2
27 type: phandle-array
28 sync-gpios:
[all …]
|
| D | adi,max14906-gpio.yaml | 3 # SPDX-License-Identifier: Apache-2.0
7 compatible: "adi,max14906-gpio"
10 "#gpio-cells":
17 drdy-gpios:
19 High-Side Open-Drain Output. READY is passive low when the internal
22 type: phandle-array
23 fault-gpios:
25 Fault pin indicates when there is Fault state in either FAULT1 or FAULT2
27 type: phandle-array
28 sync-gpios:
[all …]
|
| /Zephyr-latest/boards/adi/max32655fthr/doc/ |
| D | index.rst | 6 ultra low-power wireless solutions using MAX32655 Arm© Cortex®-M4F and Bluetooth® 5.2 Low Energy (L…
8 The form factor is a small 0.9in x 2.6in dual-row header footprint that is compatible
12 The MAX32655FTHR provides a power-optimized flexible platform for quick proof-of-concepts and
34 - MAX32655 MCU:
36 - Ultra-Low-Power Wireless Microcontroller
37 - Internal 100MHz Oscillator
38 - Flexible Low-Power Modes with 7.3728MHz System Clock Option
39 - 512KB Flash and 128KB SRAM (Optional ECC on One 32KB SRAM Bank)
40 - 16KB Instruction Cache
41 - Bluetooth 5.2 LE Radio
[all …]
|
| /Zephyr-latest/doc/services/tfm/ |
| D | overview.rst | 1 Trusted Firmware-M Overview
4 `Trusted Firmware-M (TF-M) <https://tf-m-user-guide.trustedfirmware.org/>`__
6 `IoT Security Framework <https://www.psacertified.org/what-is-psa-certified/>`__.
10 Zephyr RTOS has been PSA Certified since Zephyr 2.0.0 with TF-M 1.0, and
11 is currently integrated with TF-M 2.1.0.
13 What Does TF-M Offer?
16 Through a set of secure services and by design, TF-M provides:
18 * Isolation of secure and non-secure resources
19 * Embedded-appropriate crypto
22 * Protected off-chip data storage and retrieval
[all …]
|
| /Zephyr-latest/samples/subsys/modbus/rtu_server/ |
| D | README.rst | 1 .. zephyr:code-sample:: modbus-rtu-server
3 :relevant-api: modbus
16 This sample has been tested with the nRF52840-DK and FRDM-K64F boards,
18 device controller. Additionally the board should have three LEDs.
26 Using RS-485 transceiver
30 In addition to the evaluation board, an USB to RS-485 bus adapter and
31 a RS-485 shield are required. The shield converts UART TX, RX signals to RS-485.
32 An Arduino header compatible shield like `joy-it RS-485 shield for Arduino`_
34 on the JOY-IT shield. For other shields, ``de-gpios`` property must be adapted
38 The USB to RS-485 adapter connects to the USB port of a computer.
[all …]
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | kernelobjects.rst | 6 A kernel object can be one of three classes of data:
36 may be called to release any runtime-allocated buffers the object was using.
52 * The object must be declared as a top-level global at build time, such that it
54 with static scope. The post-build script :ref:`gen_kobject_list.py` scans the
60 must not be located in any memory partitions that are user-accessible.
71 information will be printed if the script is run with the ``--verbose`` flag,
101 The :ref:`gen_kobject_list.py` script is a post-build step which finds all the
110 with a constant-time lookup in this table.
130 initialization state and whether an object is public or not.
165 :c:func:`k_object_access_grant` API. The convenience pseudo-function
[all …]
|
| /Zephyr-latest/boards/beagle/beaglebone_ai64/doc/ |
| D | index.rst | 6 BeagleBone AI-64 is a computational platform powered by TI J721E SoC, which is
12 BeagleBone AI-64 is powered by TI J721E SoC, which has three domains (MAIN,
17 ----------------
24 --------------------------
27 32-bit input address into a 48-bit output address. Any input transaction that
32 ------------------------
36 a level or a pulse (both active-high). The VIM has two interrupt outputs per core
44 +-----------+------------+-----------------------+
47 | UART | on-chip | serial port-polling |
48 | | | serial port-interrupt |
[all …]
|
