| /Zephyr-latest/doc/templates/ |
| D | sample.tmpl | 1 .. zephyr:code-sample:: a_unique_id_for_the_sample
6 the sentence "This code sample shows how to ...").
29 [When showing code-blocks with sample build command instructions, use the
31 hand-written code-block.]
|
| /Zephyr-latest/boards/nordic/nrf9151dk/ |
| D | Kconfig.defconfig | 9 # of the flash, or into the code-partition defined in DT if it is intended to
12 # be restricted to the size of its code partition.
14 # must be linked into the code-partition (non-secure) defined in DT, regardless.
19 DT_CHOSEN_Z_CODE_PARTITION := zephyr,code-partition
|
| /Zephyr-latest/boards/nordic/nrf9161dk/ |
| D | Kconfig.defconfig | 9 # of the flash, or into the code-partition defined in DT if it is intended to
12 # be restricted to the size of its code partition.
14 # must be linked into the code-partition (non-secure) defined in DT, regardless.
19 DT_CHOSEN_Z_CODE_PARTITION := zephyr,code-partition
|
| /Zephyr-latest/samples/net/syslog_net/ |
| D | README.rst | 1 .. zephyr:code-sample:: syslog-net
15 The source code for this sample application can be found at:
29 .. code-block:: cfg
38 .. code-block:: console
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | mcp.rst | 28 explorable from the mcc shell and the mpl shell, by typing :code:`mcc`
29 or :code:`mpl` and pressing TAB. A help text for each command can be
83 command :code:`mcc init`.
85 To achieve a connection to the peer, the :code:`bt` commands must be
86 used - :code:`bt init` followed by :code:`bt advertise on` (or
87 :code:`bt connect` if the server is advertising).
91 giving the command :code:`mcc discover_mcs`. This will store the
106 .. code-block:: console
124 .. code-block:: console
166 .. code-block:: console
[all …]
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | native_sim_setup.rst | 16 In this example, the :zephyr:code-sample:`sockets-echo-server` sample application from
28 .. code-block:: console
53 .. code-block:: console
60 .. code-block:: console
87 .. code-block:: console
93 .. code-block:: console
124 .. code-block:: console
132 sockets API. This means that :zephyr:code-sample:`sockets-echo-server` and
138 .. code-block:: console
144 .. code-block:: console
[all …]
|
| /Zephyr-latest/samples/sensor/accel_polling/ |
| D | README.rst | 1 .. zephyr:code-sample:: accel_polling
18 .. code-block:: devicetree
37 .. code-block:: console
|
| /Zephyr-latest/samples/drivers/lora/send/ |
| D | README.rst | 1 .. zephyr:code-sample:: lora-send
14 LoRa receive sample :zephyr:code-sample:`lora-receive` on another board within
33 .. code-block:: console
|
| /Zephyr-latest/boards/ezurio/bl653_dvk/doc/ |
| D | bl653_dvk.rst | 77 Here is an example for the :zephyr:code-sample:`hello_world` application.
83 .. code-block:: console
87 Replace :code:`<tty_device>` with the port where the BL653 development kit
88 can be found. For example, under Linux, :code:`/dev/ttyUSB0`.
108 * :zephyr:code-sample:`ble_peripheral`
109 * :zephyr:code-sample:`bluetooth_eddystone`
110 * :zephyr:code-sample:`bluetooth_ibeacon`
119 * :zephyr:code-sample:`blinky`
120 * :zephyr:code-sample:`button`
134 .. code-block:: devicetree
|
| /Zephyr-latest/boards/ezurio/bl654_dvk/doc/ |
| D | bl654_dvk.rst | 88 Here is an example for the :zephyr:code-sample:`hello_world` application.
94 .. code-block:: console
98 Replace :code:`<tty_device>` with the port where the board nRF52 DK
99 can be found. For example, under Linux, :code:`/dev/ttyUSB0`.
119 * :zephyr:code-sample:`ble_peripheral`
120 * :zephyr:code-sample:`bluetooth_eddystone`
121 * :zephyr:code-sample:`bluetooth_ibeacon`
130 * :zephyr:code-sample:`blinky`
131 * :zephyr:code-sample:`button`
|
| /Zephyr-latest/doc/kernel/services/synchronization/ |
| D | semaphores.rst | 60 The following code defines a semaphore, then configures it as a binary
63 .. code-block:: c
72 The following code has the same effect as the code segment above.
74 .. code-block:: c
83 The following code builds on the example above, and gives the semaphore to
86 .. code-block:: c
101 The following code builds on the example above, and waits up to 50 milliseconds
105 .. code-block:: c
|
| /Zephyr-latest/boards/ezurio/bl652_dvk/doc/ |
| D | bl652_dvk.rst | 174 Here is an example for the :zephyr:code-sample:`hello_world` application.
180 .. code-block:: console
184 Replace :code:`<tty_device>` with the port where the BL652 DVK
185 can be found. For example, under Linux, :code:`/dev/ttyUSB0`.
205 * :zephyr:code-sample:`ble_peripheral`
206 * :zephyr:code-sample:`bluetooth_eddystone`
207 * :zephyr:code-sample:`bluetooth_ibeacon`
215 * :zephyr:code-sample:`blinky`
216 * :zephyr:code-sample:`button`
|
| /Zephyr-latest/boards/adafruit/itsybitsy/doc/ |
| D | index.rst | 72 Logging is done using the USB-CDC port. See the :zephyr:code-sample:`logging` sample
73 or the :zephyr:code-sample:`usb-cdc-acm-console` sample applications to see how this works.
77 The :zephyr:code-sample:`button` sample lets you test the buttons (switches) and the red LED.
78 The :zephyr:code-sample:`blinky` sample lets you test the red LED.
81 with the :zephyr:code-sample:`led-strip` sample application.
107 into the :code:`ITSY840BOOT` drive.
109 #. Build the Zephyr kernel and the :zephyr:code-sample:`blinky`
124 Drag and drop the file :code:`samples/basic/blinky/build/zephyr/zephyr.uf2`
125 into :code:`ITSY840BOOT`
|
| /Zephyr-latest/samples/drivers/ipm/ipm_ivshmem/ |
| D | README.rst | 1 .. zephyr:code-sample:: ipm-ivshmem
35 .. code-block:: console
39 $ *** Example code, do not use in production ***
44 .. code-block:: console
57 .. code-block:: console
63 .. code-block:: console
94 .. code-block:: console
110 .. code-block:: console
125 .. code-block:: console
|
| /Zephyr-latest/doc/contribute/ |
| D | index.rst | 6 Contributions from the community are the backbone of the project. Whether it is by submitting code,
43 readability across the code base.
47 readability across the code base.
60 The Zephyr project thrives on good documentation. Whether it is as part of a code contribution or
92 available in other open source projects, and it is recommended and encouraged to reuse such code.
93 This page describes in more details when and how to import external source code into Zephyr.
96 Similarly, external tooling used during compilation, code analysis, testing or simulation, can be
100 As some functionality might only be made available with the help of executable code distributed
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | ota.rst | 19 into an unoccupied code partition, usually named ``slot1_partition``, then
47 There is a :zephyr:code-sample:`hawkbit-api` sample included in the
48 Zephyr :zephyr:code-sample-category:`mgmt` section.
58 There is an :zephyr:code-sample:`updatehub-fota` sample included in the Zephyr
59 :zephyr:code-sample-category:`mgmt` section.
69 There is an :zephyr:code-sample:`smp-svr` sample included in the Zephyr
70 :zephyr:code-sample-category:`mgmt` section.
77 connect to an LwM2M server using DTLS. A :zephyr:code-sample:`lwm2m-client` sample is
|
| /Zephyr-latest/subsys/input/ |
| D | input_longpress.c | 40 uint16_t code; in longpress_deferred() local
42 code = cfg->long_codes[entry->index]; in longpress_deferred()
44 input_report_key(dev, code, 1, true, K_FOREVER); in longpress_deferred()
61 if (evt->code == cfg->input_codes[i]) { in longpress_cb()
66 LOG_DBG("ignored code %d", evt->code); in longpress_cb()
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | tips.rst | 79 to other nodes in the system. Search the source code for drivers using these
86 For applications, see :zephyr:code-sample:`blinky` for a devicetree-based alternative.
92 symbol is ``y``. For example, the following code forces ``CONSOLE`` to ``y``
95 .. code-block:: kconfig
119 .. code-block:: kconfig
131 .. code-block:: kconfig
149 .. code-block:: kconfig
184 .. code-block:: kconfig
201 .. code-block:: cfg
209 .. code-block:: kconfig
[all …]
|
| /Zephyr-latest/boards/andestech/adp_xc7k_ae350/ |
| D | adp_xc7k_ae350.dts | 110 zephyr,code = <INPUT_KEY_0>;
115 zephyr,code = <INPUT_KEY_1>;
120 zephyr,code = <INPUT_KEY_2>;
125 zephyr,code = <INPUT_KEY_3>;
130 zephyr,code = <INPUT_KEY_4>;
135 zephyr,code = <INPUT_KEY_5>;
140 zephyr,code = <INPUT_KEY_6>;
|
| /Zephyr-latest/samples/kernel/bootargs/ |
| D | README.rst | 1 .. zephyr:code-sample:: bootargs
35 .. code-block:: console
56 .. code-block:: console
63 .. code-block:: console
69 .. code-block:: console
90 .. code-block:: console
105 .. code-block:: console
|
| /Zephyr-latest/samples/sensor/proximity_polling/ |
| D | README.rst | 1 .. zephyr:code-sample:: proximity_polling
21 .. code-block:: devicetree
40 .. code-block:: console
|
| /Zephyr-latest/samples/modules/canopennode/ |
| D | README.rst | 1 .. zephyr:code-sample:: canopennode
31 .. code-block:: console
134 .. code-block:: console
142 .. code-block:: console
157 .. code-block:: console
167 .. code-block:: console
174 accomplished using the following Python code:
176 .. code-block:: py
216 Running the above Python code will update the NMT state of the node
223 name) can be accomplished using the following Python code:
[all …]
|
| /Zephyr-latest/boards/gd/gd32f403z_eval/ |
| D | gd32f403z_eval.dts | 49 zephyr,code = <INPUT_KEY_WAKEUP>;
54 zephyr,code = <INPUT_KEY_0>;
59 zephyr,code = <INPUT_KEY_1>;
64 zephyr,code = <INPUT_KEY_2>;
|
| /Zephyr-latest/boards/khadas/edgev/doc/ |
| D | index.rst | 25 kernel tests on Khadas Edge-V board. For example, with the :zephyr:code-sample:`hello_world`:
39 .. code-block:: console
45 .. code-block:: console
51 .. code-block:: console
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/host/ |
| D | l2cap.rst | 4 The :code:`l2cap` command exposes parts of the L2CAP API. The following example shows how to
11 .. code-block:: console
18 .. code-block:: console
35 .. code-block:: console
|
