Searched refs:using (Results 26 – 50 of 1710) sorted by relevance
12345678910>>...69
| /Zephyr-latest/samples/drivers/led/is31fl3733/ |
| D | README.rst | 15 - Dim each LED in sequence using :c:func:`led_set_brightness` API
16 - Toggle each LED in sequency using :c:func:`led_on` and :c:func:`led_of` APIs
17 - Toggle between low or high current limit using :c:func:`is31fl3733_current_limit`
23 The number of LEDs can be limited using the following sample specific Kconfigs:
|
| /Zephyr-latest/doc/services/storage/settings/ |
| D | index.rst | 8 provided behind a common API using FCB, NVS, ZMS or a file system. These
33 These are registered using a call to :c:func:`settings_register()` for
34 dynamic handlers or defined using a call to :c:macro:`SETTINGS_STATIC_HANDLER_DEFINE()`
38 This gets called when asking for a settings element value by its name using
43 :c:func:`settings_load()`, or when using :c:func:`settings_runtime_set()` from the
62 initializing a settings handler with a different priority is done using a call to
63 :c:func:`settings_register_with_cprio()` for dynamic handlers or using a call to
71 implement a set of handler functions. These are registered using a call to
78 This gets called when loading values from persistent storage using
82 This gets called when saving a single setting to persistent storage using
[all …]
|
| /Zephyr-latest/boards/sifive/hifive_unleashed/support/ |
| D | hifive_unleashed.resc | 6 using sysbus
11 using "platforms/cpus/sifive-fu540.repl"
|
| /Zephyr-latest/boards/shields/adafruit_data_logger/ |
| D | adafruit_data_logger.overlay | 15 * LED1 connection must be manually established using a jumper between
23 * LED2 connection must be manually established using a jumper between
61 * Interrupt connection must be manually established using a jumper wire between
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | atomic.rst | 32 An atomic variable is defined using a variable of type :c:type:`atomic_t`.
35 a different value using :c:macro:`ATOMIC_INIT`:
44 An atomic variable is manipulated using the APIs listed at the end of
70 However, you can also define an N-bit array of atomic variables using
73 A single bit in array of atomic variables can be manipulated using
77 using an array of atomic variables.
112 Using atomic variables is typically far more efficient than using
113 other techniques to implement critical sections such as using a mutex
|
| /Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_63.rst | 85 | | appears if an error is returned when using SMP version 2. |
88 | | non-zero (error condition) when using SMP version 2. |
91 | | using SMP version 1 or for SMP errors when using SMP version 2. |
|
| D | smp_group_2.rst | 126 | | appears if an error is returned when using SMP version 2. |
129 | | non-zero (error condition) when using SMP version 2. |
132 | | using SMP version 1 or for SMP errors when using SMP version 2. |
219 | | appears if an error is returned when using SMP version 2. |
222 | | non-zero (error condition) when using SMP version 2. |
225 | | using SMP version 1 or for SMP errors when using SMP version 2. |
|
| D | smp_group_8.rst | 40 of uploading/downloading files using fs_mgmt), but files are not exclusively
150 | | appears if an error is returned when using SMP version 2. |
153 | | non-zero (error condition) when using SMP version 2. |
156 | | using SMP version 1 or for SMP errors when using SMP version 2. |
172 does not make use of uploading/downloading files using fs_mgmt), but files are
289 | | appears if an error is returned when using SMP version 2. |
292 | | non-zero (error condition) when using SMP version 2. |
295 | | using SMP version 1 or for SMP errors when using SMP version 2. |
389 | | appears if an error is returned when using SMP version 2. |
392 | | non-zero (error condition) when using SMP version 2. |
[all …]
|
| /Zephyr-latest/drivers/pinctrl/ |
| D | Kconfig.gd32 | 9 GD32 AF pin controller driver. This driver is used by series using the
17 GD32 AFIO pin controller driver. This driver is used by series using the
|
| /Zephyr-latest/boards/st/nucleo_wba52cg/support/ |
| D | openocd.cfg | 1 # Note: Using OpenOCD using nucloe_wba52cg requires using STMicroelectronics
|
| /Zephyr-latest/boards/st/nucleo_wba55cg/support/ |
| D | openocd.cfg | 1 # Note: Using OpenOCD using nucloe_wba52cg requires using openocd fork.
|
| /Zephyr-latest/samples/subsys/console/echo/ |
| D | README.rst | 5 Echo an input character back to the output using the Console API.
23 board. Alternatively you can run this using QEMU, as described in
34 keyboard, and they will be echoed back to the terminal program you are using.
|
| /Zephyr-latest/samples/application_development/external_lib/ |
| D | README.rst | 11 The demonstrates both how to build the external library using a different build
18 your path. This can be setup using chocolatey or by manually installing it.
23 Install make using the following command:
|
| /Zephyr-latest/samples/bluetooth/hci_vs_scan_req/ |
| D | README.rst | 5 Use vendor-specific HCI commands to enable Scan Request events when using legacy advertising.
11 scan request events even using legacy advertisements, while may result in lower
12 RAM usage than using extended advertising.
|
| /Zephyr-latest/tests/subsys/fs/zms/ |
| D | Kconfig | 7 bool "Enable ZMS tests designed to be run using a flash-simulator"
10 If y, enables ZMS tests designed to be run using a flash-simulator,
|
| /Zephyr-latest/samples/drivers/led/lp50xx/ |
| D | README.rst | 12 First, for each LED information is retrieved using the led_get_info syscall
14 (described below) is applied to all the LEDs simultaneously (using the
15 :c:func:`led_write_channels` syscall) and then to each LED one by one (using the
21 For all the LEDs first (using channel API) and then for each LED one by one:
|
| /Zephyr-latest/boards/96boards/wistrio/doc/ |
| D | 96b_wistrio.rst | 126 96Boards WisTrio can be flashed by two methods, one using the ROM
127 bootloader and another using the SWD debug port (which requires additional
130 Flashing using the ROM bootloader requires a special activation pattern,
131 which can be triggered by using the BOOT0 pin. The ROM bootloader supports
139 1. Connect 96Boards WisTrio to your Linux PC using, USB-Micro to USB-A
151 …r building and flashing the :zephyr:code-sample:`hello_world` application using `stm32flash`_ comm…
162 be connected to the SWD pins exposed on the J22 header using its flying
175 Remote debugging using /dev/ttyACM0
184 After flashing 96Boards WisTrio, it can be debugged using the same
|
| /Zephyr-latest/modules/thrift/src/thrift/server/ |
| D | TServer.h | 41 using apache::thrift::TProcessor;
42 using apache::thrift::protocol::TBinaryProtocolFactory;
43 using apache::thrift::protocol::TProtocol;
44 using apache::thrift::protocol::TProtocolFactory;
45 using apache::thrift::transport::TServerTransport;
46 using apache::thrift::transport::TTransport;
47 using apache::thrift::transport::TTransportFactory;
|
| /Zephyr-latest/drivers/gpio/ |
| D | Kconfig.mmio32 | 8 memory-mapped i/o register using the same APIs as GPIO drivers. This
11 Zephyr normally expects to be specified using a GPIO pin, e.g. for
|
| /Zephyr-latest/samples/subsys/display/cfb/ |
| D | README.rst | 5 Display character strings using the Character Frame Buffer (CFB).
10 This sample displays character strings using the Character Frame Buffer
|
| /Zephyr-latest/drivers/spi/ |
| D | Kconfig.xmc4xxx | 30 int "Timeout in milliseconds for an SPI transaction to complete if using DMA"
33 Sets timeout in milliseconds for an SPI transaction to complete when using DMA.
|
| /Zephyr-latest/tests/boot/test_mcuboot/ |
| D | README.rst | 5 using sysbuild. The first application is the MCUBoot bootloader. The second
8 adjustment using CONFIG_BUILD_OUTPUT_ADJUST_LMA, and will be the application
|
| /Zephyr-latest/samples/basic/servo_motor/ |
| D | README.rst | 5 Drive a servomotor using the PWM API.
10 This is a sample app which drives a servomotor using the :ref:`PWM API <pwm_api>`.
18 to modify the source code if you are using a different servomotor.
24 by PWM. The servo must be defined in Devicetree using the ``pwm-servo``
|
| /Zephyr-latest/samples/sensor/grow_r502a/ |
| D | README.rst | 5 Store and match fingerprints using the GROW R502-A fingerprint sensor.
12 #. Sensor LED is controlled using led APIs from zephyr subsystem.
27 used to control the sensor. Sensor can be powered using mentioned optional GPIO.
39 build this sample app using:
|
| /Zephyr-latest/boards/nxp/mimxrt1024_evk/ |
| D | CMakeLists.txt | 11 message(WARNING "It appears you are using the board definition for "
34 message(WARNING "You are using SDRAM as RAM but no device "
41 message(WARNING "You appear to be using the GPT hardware timer. "
|
12345678910>>...69
