Searched refs:should (Results 101 – 125 of 1262) sorted by relevance
12345678910>>...51
/Zephyr-latest/doc/develop/sca/ |
D | cpptest.rst | 17 :ref:`west build <west-building>` should be called with a ``-DZEPHYR_SCA_VARIANT=cpptest`` 32 To import and generate a report file, something like the following should work.
|
/Zephyr-latest/drivers/dma/ |
D | Kconfig.dw_common | 17 then this should be increased to match the need. 28 bool "channels should be suspended and drained on stop"
|
/Zephyr-latest/tests/lib/devicetree/api_ext/ |
D | app.overlay | 9 * Names in this file should be chosen in a way that won't conflict 67 /* there should only be one of these */
|
/Zephyr-latest/samples/boards/st/power_mgmt/suspend_to_ram/ |
D | README.rst | 21 The board should support enabling PM. For a STM32 based target, it means that 22 it should support a clock source alternative to Cortex Systick that can be used
|
/Zephyr-latest/boards/gd/gd32vf103c_starter/doc/ |
D | index.rst | 66 terminal should be something like ``/dev/ttyUSB0``. For example: 73 string. Connection should be configured as follows: 88 You should see "Hello World! gd32vf103c_starter" in your terminal.
|
/Zephyr-latest/cmake/modules/ |
D | user_cache.cmake | 7 # The user cache can be used for caching of data that should be persistent 11 # Only data that can be safely re-generated should be placed in this cache. 42 # Determine which env vars should be checked
|
/Zephyr-latest/subsys/sensing/ |
D | Kconfig | 62 to notify dispatch thread, runtime thread priority should lower than 84 Ring buffer data should be fetched ASAP, so Dispatch 85 thread priority should be higher than runtime thread
|
/Zephyr-latest/tests/cmake/sysbuild_snippets/ |
D | Kconfig.sysbuild | 8 This option's value should be overridden by the 'foo' snippet config overlay.
|
/Zephyr-latest/doc/services/device_mgmt/ |
D | smp_protocol.rst | 45 The original specification states that SMP should support receiving 66 | | used, this should be set to 0b01 to use the newer | 70 | | 0b11 are reserved for future use and should not | 79 | | yet, the field should be set to 0 | 90 | | The Sequence Num of a response should match | 158 other side of a request, a response should be issued containing the header
|
/Zephyr-latest/boards/shields/mikroe_wifi_bt_click/doc/ |
D | index.rst | 25 | RST# | Reset pin, in most of the boards it should | 44 This shield should be loaded with the `ESP32 AT Bin`_ software which is 79 terminal configured as 115200, 8, N, 1 and perform a board reset. You should see an 80 initial log and last message should be the version of the AT firmware flashed.
|
/Zephyr-latest/doc/project/ |
D | documentation.rst | 44 :ref:`Ztest framework <test-framework>`. Test documentation should only be done 50 Test documentation should not interfere with the actual API documentation and 56 - All test code documentation should be grouped under the ``all_tests`` doxygen 58 - All test documentation should be under doxygen groups that are prefixed
|
/Zephyr-latest/boards/peregrine/sam4l_wm400_cape/ |
D | Kconfig.defconfig | 15 # the code_partition. This should be disabled when using the whole flash without
|
/Zephyr-latest/boards/ite/it8xxx2_evb/doc/ |
D | index.rst | 145 #. Turn on the it8xxx2_evb board switch, you should see ``"Hello World! it8xxx2_evb"`` 147 message should appear. 153 Under Linux the terminal should be :code:`/dev/ttyUSB0`. Do not close it. 171 You should see ``"Hello World! it8xxx2_evb"`` in the first terminal window. 172 If you don't see this message, press the Reset button and the message should appear.
|
/Zephyr-latest/boards/ite/it82xx2_evb/doc/ |
D | index.rst | 142 #. Turn on the it82xx2_evb board switch, you should see ``"Hello World! it82xx2_evb"`` 144 message should appear. 150 Under Linux the terminal should be :code:`/dev/ttyUSB0`. Do not close it. 168 You should see ``"Hello World! it82xx2_evb"`` in the first terminal window. 169 If you don't see this message, press the Reset button and the message should appear.
|
/Zephyr-latest/doc/develop/test/ |
D | twister_statuses.rst | 42 Such grouped Cases should have enough in common 114 Those should not appear in the final Twister report. 184 ✕ indicates that such a combination should not happen in a proper Twister run. In other words, 185 no Suite of a status indicated by the table column should contain any Cases of a status indicated 195 out of a given Twister run. Thus, any Case within it should also have such a status.
|
/Zephyr-latest/samples/boards/st/power_mgmt/standby_shutdown/ |
D | README.rst | 23 The board should support enabling PM. For a STM32 based target, it means that 24 it should support a clock source alternative to Cortex Systick that can be used
|
/Zephyr-latest/boards/particle/argon/dts/ |
D | mesh_feather_i2c1_twi1.dtsi | 10 * Changes should be made in all instances. */
|
/Zephyr-latest/boards/particle/xenon/dts/ |
D | mesh_feather_i2c1_twi1.dtsi | 10 * Changes should be made in all instances. */
|
/Zephyr-latest/doc/contribute/style/ |
D | kconfig.rst | 7 * Indent with tabs, except for ``help`` entry text which should be placed at
|
/Zephyr-latest/soc/openisa/rv32m1/ |
D | Kconfig.soc | 9 option should not be used to target either Arm core.
|
/Zephyr-latest/drivers/counter/ |
D | Kconfig.mcux_lptmr | 20 The compatible string "nxp,kinetis-lptmr" should
|
/Zephyr-latest/boards/gd/gd32f350r_eval/doc/ |
D | index.rst | 70 terminal should be something like ``/dev/ttyUSB0``. For example: 77 string. Connection should be configured as follows: 92 You should see "Hello World! gd32f350r_eval" in your terminal.
|
/Zephyr-latest/boards/gd/gd32f450v_start/doc/ |
D | index.rst | 67 terminal should be something like ``/dev/ttyUSB0``. For example: 74 string. Connection should be configured as follows: 89 You should see "Hello World! gd32f450v_start" in your terminal.
|
/Zephyr-latest/boards/gd/gd32l233r_eval/doc/ |
D | index.rst | 65 terminal should be something like ``/dev/ttyUSB0``. For example: 72 string. Connection should be configured as follows: 87 You should see "Hello World! gd32l233r_eval" in your terminal.
|
/Zephyr-latest/boards/gd/gd32vf103v_eval/doc/ |
D | index.rst | 73 terminal should be something like ``/dev/ttyUSB0``. For example: 80 string. Connection should be configured as follows: 95 You should see "Hello World! gd32vf103v_eval" in your terminal.
|
12345678910>>...51