Searched refs:should (Results 301 – 325 of 1262) sorted by relevance
1...<<11121314151617181920>>...51
| /Zephyr-latest/subsys/mgmt/mcumgr/grp/img_mgmt_client/ |
| D | Kconfig | 8 # Options defined in this file should be prefixed:
|
| /Zephyr-latest/tests/drivers/build_all/fpga/ |
| D | app.overlay | 8 * Names in this file should be chosen in a way that won't conflict
|
| /Zephyr-latest/samples/subsys/display/cfb_custom_font/ |
| D | README.rst | 26 Generic config file, normally you should use this.
|
| /Zephyr-latest/samples/sensor/ms5837/ |
| D | README.rst | 22 The nrf52840 Preview development kit should be connected as follows to the
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-4.1.rst | 32 with ``SB_CONFIG_MCUBOOT_MODE_SWAP_USING_MOVE``, applications should be updated to select this
94 * Shield ``mikroe_weather_click`` now supports both I2C and SPI interfaces. Users should select
181 The :c:macro:`DEVICE_API()` macro should be used by out-of-tree driver implementations for
213 ``mipi-mode`` property in devicetree should now use a string property of
358 Pinctrl should now be configured like this:
554 introduced which should be selected by the respective link layer Kconfig options (e.g. a
574 it should be unprovisioned first and reprovisioned after update again.
580 Applications should be built with :kconfig:option:`CONFIG_SECURE_STORAGE` enabled.
621 :kconfig:option:`CONFIG_BT_BUF_ACL_RX_COUNT_EXTRA` should be set to ``7 - (3 + 1) = 3``.
629 pairing, it should disable :kconfig:option:`CONFIG_BT_SMP_SC_PAIR_ONLY` manually.
[all …]
|
| /Zephyr-latest/samples/subsys/usb/midi/ |
| D | README.rst | 50 The "USBD MIDI Sample" interface should also appear in any program with MIDI
71 These events should then appear in the first shell (dump)
|
| /Zephyr-latest/samples/bluetooth/extended_adv/ |
| D | README.rst | 43 The two devices should automatically connect if they are close enough.
45 Here are the outputs you should get by default:
|
| /Zephyr-latest/doc/build/dts/ |
| D | bindings-upstream.rst | 22 is an existing binding for your device in an authoritative location, you should
111 should have a vendor prefix.
119 properties, and compatibles should not include them unless they refer to an
125 binding and a devicetree using the vendor prefix, and should ideally include
150 create a consistent configuration, then those properties should be made
162 Driver developers should use their best judgment as to whether a value can be
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | soc_porting.rst | 37 you should probably improve the existing SoC instead of creating a new one.
59 Your SoC directory should look like this:
158 In general, :file:`<soc>.dtsi` should look like this:
198 CPU cluster :file:`.dtsi` files should follow the naming scheme
267 :file:`Kconfig.defconfig` should be used instead.
274 The entire file should be inside a pair of ``if SOC_<SOC_NAME>`` / ``endif``
|
| /Zephyr-latest/boards/arduino/nano_33_ble/doc/ |
| D | index.rst | 76 Double-tap the RESET button on your board. Your board should disconnect, reconnect,
77 and there should be a pulsing orange LED near the USB port.
81 You should see the red LED blink.
118 After installing the TRACE32, You should set the environmental variable ``T32_DIR``.
|
| /Zephyr-latest/subsys/net/lib/ptp/ |
| D | Kconfig | 43 in the standard are taken. The value should be selected carefully.
105 Specify the accuracy of the clock. This setting should reflect
202 Defines mean time interval between successive Announce messages. The value should be
263 is bigger than 1 the option value should be adjusted accordingly.
|
| /Zephyr-latest/include/zephyr/arch/x86/ia32/scripts/ |
| D | shared_kernel_pages.ld | 14 * no sensitive data should be here as Meltdown exploits may read it.
|
| /Zephyr-latest/drivers/interrupt_controller/ |
| D | Kconfig.intel_vtd | 35 This device should be initialized as soon as possible, before any
|
| /Zephyr-latest/cmake/linker_script/common/ |
| D | thread-local-storage.cmake | 25 # /* The "master copy" of tdata should be only in flash on XIP systems */
|
| /Zephyr-latest/doc/build/snippets/ |
| D | using.rst | 44 If an application should always be compiled with a given snippet, it
|
| /Zephyr-latest/boards/raspberrypi/rpi_4b/doc/ |
| D | index.rst | 40 Insert the card and power on the board. You should see the following output on
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | regulators.rst | 18 infrastructure is not justified, and ``*-gpios`` devicetree properties should be
|
| /Zephyr-latest/tests/drivers/build_all/w1/ |
| D | app.overlay | 8 * Names in this file should be chosen in a way that won't conflict
|
| /Zephyr-latest/samples/subsys/input/draw_touch_events/ |
| D | README.rst | 14 While this is a generic sample and it should work with any boards with both display controllers
|
| /Zephyr-latest/samples/subsys/console/echo/ |
| D | README.rst | 41 You should see another line with instructions below. If not,
|
| /Zephyr-latest/samples/boards/st/uart/single_wire/ |
| D | README.rst | 33 After flashing the console output should not show any failure reports,
|
| /Zephyr-latest/samples/basic/fade_led/ |
| D | README.rst | 15 period is taken from Devicetree. It should be fast enough to be above the
|
| /Zephyr-latest/samples/boards/quicklogic/qomu/ |
| D | README.rst | 38 After connecting to the shell console you should see the following output:
|
| /Zephyr-latest/samples/sensor/ina219/ |
| D | README.rst | 36 you should get a similar output as below, repeated every 2 seconds:
|
| /Zephyr-latest/samples/subsys/usb/testusb/ |
| D | README.rst | 28 The ``usbtest`` module should claim the device:
52 #. To run all the tests the Zephyr's VID / PID should be inserted to USB
|
1...<<11121314151617181920>>...51
