Searched refs:code (Results 26 – 50 of 2837) sorted by relevance
12345678910>>...114
15 .. code-block:: console28 [bcode <broadcast code> || bcode_str <broadcast code97 .. code-block:: console111 .. code-block:: console126 .. code-block:: console136 .. code-block:: console144 .. code-block:: console154 .. code-block:: console162 .. code-block:: console172 The command :code:`bap create_broadcast_sink` will either use existing periodic advertising[all …]
16 When the Bluetooth stack has been initialized (:code:`bt init`), the Acceptor can be registered by17 calling :code:`cap_acceptor init`, which will register the CAS and CSIS services, as well as20 .. code-block:: console42 :code:`bt adv-data` or :code:`bt advertise` must be called again to set the new advertising data.43 If :code:`CONFIG_BT_CSIP_SET_MEMBER_SIRK_NOTIFIABLE` is enabled, this will also notify connected46 .. code-block:: console56 .. code-block:: console75 When the Bluetooth stack has been initialized (:code:`bt init`), the Initiator can discover CAS and76 the optionally included CSIS instance by calling (:code:`cap_initiator discover`).79 .. code-block:: console[all …]
21 When the Bluetooth stack has been initialized (:code:`bt init`),23 the connected device calling :code:`bap_broadcast_assistant discover`, which27 .. code-block:: console45 broadcast_code : Send a string-based broadcast code of up to 16 bytes46 <src_id> <broadcast code>56 .. code-block:: console73 .. code-block:: console84 .. code-block:: console94 .. code-block:: console112 .. code-block:: console[all …]
1 .. zephyr:code-sample:: usb-hid-mouse38 .. code-block:: none58 .. code-block:: console76 .. code-block:: console85 Event code 272 (BTN_LEFT)86 Event code 273 (BTN_RIGHT)87 Event code 274 (BTN_MIDDLE)89 Event code 0 (REL_X)90 Event code 1 (REL_Y)91 Event code 8 (REL_WHEEL)[all …]
29 To use the RTC, set :code:`CONFIG_CORTEX_M_SYSTICK=n` and set30 :code:`CONFIG_SYS_CLOCK_TICKS_PER_SEC` to no more than 32 kHZ divided by 7,61 The SAMD51 has three PWM generators with up to six channels each. :code:`TCC_0`62 has a resolution of 24 bits and all other generators are 16 bit. :code:`TCC_1`70 more, such as the :zephyr:code-sample:`usb-cdc-acm` sample which sets up a virtual80 bootloader will be entered automatically when you run :code:`west flash`.85 #. Build the Zephyr kernel and the :zephyr:code-sample:`hello_world` sample application:100 terminal should be :code:`/dev/ttyUSB0`. For example:102 .. code-block:: console132 #. Connect the board to the probe by connecting the :code:`SWCLK`,[all …]
6 Coding style is enforced on any new or modified code, but contributors are7 not expected to correct the style on existing code that they are not12 the style of existing code in the tree, with higher importance given to13 "nearby" code (first look at the function, then the same file, then19 * Use `snake case`_ for code and variables.23 ``switch`` body, even for single-line code blocks.29 * Avoid using non-ASCII symbols in code, unless it significantly improves31 * Use proper capitalization of nouns in code comments (e.g. ``UART`` and not
20 .. code-block:: cmake39 .. code-block:: cmake50 .. code-block:: cmake68 .. code-block:: cmake76 .. code-block:: cmake83 .. code-block:: cmake94 .. code-block:: cmake105 .. code-block:: cmake115 .. code-block:: cmake125 .. code-block:: cmake[all …]
1 .. zephyr:code-sample:: code_relocation_nocopy4 Relocate code, data, or bss sections using a custom linker script.8 A simple example that demonstrates how relocation of code, data or bss sections11 Differently from the code relocation sample, this sample is relocating the12 content of the ext_code.c file to a different FLASH section and the code is XIP13 directly from there without the need to copy / relocate the code. All other code57 .. code-block:: console
5 # FindDeprecated module provides a single location for deprecated CMake build code.6 # Whenever CMake code is deprecated it should be moved to this module and7 # corresponding COMPONENTS should be created with name identifying the deprecated code.9 # This makes it easier to maintain deprecated code and cleanup such code when it13 # CMakeList.txt contains deprecated code, like:18 # such code can easily be around for a long time, so therefore such code should22 # # This code has been deprecated after Zephyr x.y28 # and then in the original CMakeLists.txt, this code is inserted instead:42 # This code was deprecated after Zephyr v3.1.058 # This code was deprecated after Zephyr v3.2.0[all …]
42 .. code-block:: none82 .. code-block:: none95 .. code-block:: none106 .. code-block:: none120 | "ret" | return code from shell command execution. |122 | "err" -> "group" | :c:enum:`mcumgr_group_t` group of the group-based error code. Only |125 | "err" -> "rc" | contains the index of the group-based error code. Only appears if |133 In older versions of Zephyr, "rc" was used for both the mcumgr status code134 and shell command execution return code, this legacy behaviour can be
50 .. code-block:: none84 .. code-block:: none97 .. code-block:: none108 .. code-block:: none128 | "err" -> "group" | :c:enum:`mcumgr_group_t` group of the group-based error code. Only |131 | "err" -> "rc" | contains the index of the group-based error code. Only appears if |154 .. code-block:: none193 .. code-block:: none204 .. code-block:: none216 | "err" -> "group" | :c:enum:`mcumgr_group_t` group of the group-based error code. Only |[all …]
55 .. code-block:: none88 .. code-block:: none100 .. code-block:: none111 .. code-block:: none125 | "err" -> "group" | :c:enum:`mcumgr_group_t` group of the group-based error code. Only |128 | "err" -> "rc" | contains the index of the group-based error code. Only appears if |173 .. code-block:: none198 .. code-block:: none209 .. code-block:: none241 | "err" -> "group" | :c:enum:`mcumgr_group_t` group of the group-based error code. Only |[all …]
69 zephyr,code = <INPUT_KEY_0>;75 zephyr,code = <INPUT_KEY_1>;81 zephyr,code = <INPUT_KEY_2>;87 zephyr,code = <INPUT_KEY_3>;93 zephyr,code = <INPUT_KEY_4>;99 zephyr,code = <INPUT_KEY_5>;105 zephyr,code = <INPUT_KEY_6>;
10 .. code-block:: console16 .. code-block:: console24 .. code-block:: console36 .. code-block:: console43 .. code-block:: console51 .. code-block:: console76 .. code-block:: console86 .. code-block:: console
1 .. zephyr:code-sample:: async-sockets-echo13 the :zephyr:code-sample:`sockets-echo` sample. It's a more involved application,17 The source code for this sample application can be found at:40 .. code-block:: console46 it. Unlike the above-mentioned :zephyr:code-sample:`sockets-echo` sample, this application50 by changing ``NUM_FDS`` defined in the source code.61 The same application source code can be built for a POSIX system, e.g.62 Linux. (Note: if you look at the source, you will see that the code is68 .. code-block:: console74 .. code-block:: console[all …]
6 To perform service discovery on the client side, use the :code:`gatt discover` command. This should9 On the server side, you can register pre-defined test services using the :code:`gatt register`16 .. code-block:: console21 The server can now notify the client with the command :code:`gatt notify`.24 :code:`gatt exchange-mtu` command. To update the shell maximum MTU, you need to update Kconfig26 :zephyr:code-sample:`bluetooth_mtu_update`.
14 layer code itself, to call defined network routines at any level in16 example, by using these APIs, application code can request a scan be done on a21 by eliminating code at build time for management routines that are not53 pair of layer and code, whereas on the command part it will be a mask of67 code. This makes it possible for different events to be handled by the73 layer and layer code. A callback handler function **must** check74 the event code (passed as an argument) against the specific network83 layer code.)87 .. code-block:: c134 .. code-block:: c[all …]
1 .. zephyr:code-sample:: shell-fs35 .. code-block:: console53 .. code-block:: console77 the :zephyr:code-sample:`littlefs` sample.101 .. code-block:: console110 .. code-block:: console124 .. code-block:: console130 .. code-block:: console146 .. code-block:: console155 .. code-block:: console[all …]
1 .. zephyr:code-sample:: eth-ivshmem20 .. code-block:: console29 .. code-block:: console42 .. code-block:: console61 .. code-block:: console70 .. code-block:: console79 .. code-block:: console85 .. code-block:: console96 .. code-block:: console108 .. code-block:: console[all …]
1 .. zephyr:code-sample:: tdk_apex46 .. code-block:: devicetree56 .. code-block:: devicetree72 .. code-block:: devicetree78 .. code-block:: console89 .. code-block:: devicetree95 .. code-block:: console104 .. code-block:: devicetree110 .. code-block:: console121 .. code-block:: devicetree[all …]
75 .. code-block:: bash81 .. code-block:: bash97 .. code-block:: console125 .. code-block:: bash131 .. code-block:: text137 .. code-block:: text144 .. code-block:: text150 .. code-block:: text156 GDB also shows where the code execution is stopped. In this case,161 .. code-block:: text[all …]
1 .. zephyr:code-sample:: mdns-responder39 .. code-block:: console45 .. code-block:: console51 .. code-block:: console57 .. code-block:: console63 .. code-block:: console69 .. code-block:: console
11 - Get the source code28 .. code-block:: bash84 .. code-block:: bash91 .. code-block:: bash105 .. code-block:: bash121 .. code-block:: bash130 .. code-block:: bash139 .. code-block:: bash146 .. code-block:: bash186 .. code-block:: bat[all …]
14 This node is meant for sample code and user applications. It should not be15 used in the upstream Zephyr source code for device drivers, subsystems, etc.25 .. code-block:: devicetree38 You can get the above property values in C/C++ code like this:40 .. code-block:: C60 .. code-block:: devicetree72 .. code-block:: C102 .. code-block:: devicetree113 gpio_dt_spec`` in your source code, then use it like this:115 .. code-block:: C
16 int linux_evdev_read(int fd, uint16_t *type, uint16_t *code, int32_t *value) in linux_evdev_read() argument35 *code = ev.code; in linux_evdev_read()
