Searched refs:Next (Results 1 – 25 of 71) sorted by relevance
123
| /Zephyr-latest/samples/sensor/isl29035/ |
| D | README.rst | 42 Next alert outside 315 .. 415
46 Next alert outside 252 .. 352
49 Next alert outside 197 .. 297
52 Next alert outside 137 .. 237
55 Next alert outside 76 .. 176
58 Next alert outside 131 .. 231
61 Next alert outside 185 .. 285
64 Next alert outside 251 .. 351
67 Next alert outside 303 .. 403
|
| /Zephyr-latest/boards/dragino/nbsn95/ |
| D | Kconfig.dragino_nbsn95 | 1 # Copyright (c) 2021 Next Big Thing AG
|
| D | dragino_nbsn95.dts | 2 * Copyright (c) 2021 Next Big Thing AG
|
| /Zephyr-latest/tests/drivers/console/line_splitting/ |
| D | line_splitting.robot | 10 Wait For Next Line On Uart
|
| /Zephyr-latest/boards/dragino/nbsn95/support/ |
| D | openocd.cfg | 3 # Copyright (c) 2021 Next Big Thing AG
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | bap.rst | 75 :header: "Command", "Depends", "Allowed States", "Next States"
306 :header: "Depends", "Allowed States", "Next States"
322 :header: "Depends", "Allowed States", "Next States"
497 :header: "Depends", "Allowed States", "Next States"
528 :header: "Depends", "Allowed States", "Next States"
543 :header: "Depends", "Allowed States", "Next States"
561 :header: "Depends", "Allowed States", "Next States"
576 :header: "Depends", "Allowed States", "Next States"
593 :header: "Depends", "Allowed States", "Next States"
609 :header: "Depends", "Allowed States", "Next States"
[all …]
|
| /Zephyr-latest/soc/st/stm32/stm32wbax/hci_if/ |
| D | stm32_timer.c | 30 timer_object->Next = NULL; in UTIL_TIMER_Create()
|
| /Zephyr-latest/doc/develop/tools/ |
| D | stm32cubeide.rst | 35 #. Select :guilabel:`Project with existing CMake sources`, then click :guilabel:`Next`.
37 #. Select :menuselection:`Next` and browse to the location of your sources. The
40 #. Select :menuselection:`Next` and select the appropriate MCU.
103 #. Select :menuselection:`C/C++ --> STM32 Cortex-M Executable`, then click :guilabel:`Next`:
|
| /Zephyr-latest/samples/boards/st/backup_sram/ |
| D | README.rst | 40 Next reported value should be: 12
|
| /Zephyr-latest/samples/net/cellular_modem/ |
| D | README.rst | 54 Next, the UART API must be specified using ``CONFIG_UART_INTERRUPT_DRIVEN=y`` or
|
| /Zephyr-latest/lib/cpp/ |
| D | Kconfig | 66 Next revision of the C++ standard, which is expected to be published in 2020.
76 Next revision of the C++ standard, which is expected to be published in 2023.
|
| /Zephyr-latest/tests/bluetooth/tester/ |
| D | README | 48 Next, build and flash tester application by employing the "flash" build
|
| /Zephyr-latest/samples/drivers/led/lp50xx/ |
| D | README.rst | 13 and printed in the log messages. Next, from an infinite loop, a test pattern
|
| /Zephyr-latest/boards/digilent/zybo/doc/ |
| D | index.rst | 86 Next, upload and run the Zephyr application:
125 Next, upload and debug the Zephyr application:
|
| /Zephyr-latest/boards/silabs/radio_boards/xg29_rb4412a/doc/ |
| D | index.rst | 41 Next, build and flash the sample by running the following command:
|
| /Zephyr-latest/boards/nordic/nrf54l09pdk/doc/ |
| D | index.rst | 80 Next, build the sample by running the following command:
|
| /Zephyr-latest/doc/services/dsp/ |
| D | index.rst | 52 Next, the implementation should be added at ``subsys/dsp/<backend>/`` and
|
| /Zephyr-latest/boards/nordic/nrf54l20pdk/doc/ |
| D | index.rst | 81 Next, build the sample by running the following command:
|
| /Zephyr-latest/boards/arm/fvp_baser_aemv8r/doc/ |
| D | debug-with-arm-ds.rst | 69 1. Choose ``Iris`` for ``Model Interface``, then ``Next >``.
70 2. Choose ``Launch and connect to specific model``, then ``Next >``.
|
| /Zephyr-latest/boards/xen/xenvm/doc/ |
| D | index.rst | 112 This will build an image with the synchronization sample app. Next, you need to
134 Next you need to attach to PV console:
|
| /Zephyr-latest/tests/drivers/can/host/ |
| D | README.rst | 60 Next, python-can needs to be configured for the ``zcan0`` interface. One option is to use a
101 Next, python-can needs to be configured for the ``can0`` interface. One option is to use a dedicated
|
| /Zephyr-latest/samples/drivers/counter/maxim_ds3231/ |
| D | README.rst | 27 Next, information about the device as a counter is displayed. The
43 Next, if the sample application option ``CONFIG_APP_SET_ALIGNED_CLOCK``
|
| /Zephyr-latest/boards/amd/acp_6_0_adsp/doc/ |
| D | index.rst | 57 Next, set the following environment variables:
|
| /Zephyr-latest/samples/boards/espressif/flash_memory_mapped/ |
| D | README.rst | 46 Next, it prints that region content using flash API read and also using memory-mapped pointer.
|
| /Zephyr-latest/samples/net/capture/ |
| D | README.rst | 143 Next the monitoring is setup so that captured packets are sent as a payload
162 Next enable network packet capturing for interface 2.
|
123
