Home
last modified time | relevance | path

Searched refs:should (Results 476 – 500 of 1262) sorted by relevance

1...<<11121314151617181920>>...51

/Zephyr-latest/boards/adafruit/macropad_rp2040/doc/
Dindex.rst47 A "RPI-RP2" drive should appear on your host machine.
/Zephyr-latest/subsys/usb/device/class/hid/
DKconfig55 This configuration value should correspond to the number of Input
/Zephyr-latest/doc/hardware/peripherals/
Dstepper.rst53 A common set of functions which should be implemented by all stepper drivers.
/Zephyr-latest/samples/drivers/led/lp50xx/
DREADME.rst36 the device type binding should be defined in the board DTS files.
/Zephyr-latest/boards/native/doc/
Dbsim_boards_design.rst270 one should in general not call Zephyr APIs from the board code itself.
271 In particular, one should not call Zephyr APIs from the original/HW models
275 In general board code should be considered as lower level than the Zephyr OS,
277 For example, board code should not use the printk API as that anyhow would
280 should be used directly.
307 which test (if any) should be executed. When a test is selected its registered
330 the tests should not be registering initialization or callback functions using
333 Instead the equivalent ``bs_tests`` provided hooks should be used.
/Zephyr-latest/doc/develop/flash_debug/
Dhost-tools.rst51 For these devices, the user should:
63 For these devices, the user should:
71 relocation. The board :file:`.defconfig` file should have
81 The :kconfig:option:`CONFIG_BOOTLOADER_BOSSA_LEGACY` Kconfig option should be used
91 special case, the boot partition should be omitted and code_partition should
231 To use LinkServer with West commands, the install folder should be added to the
334 Windows users should use the following steps to install
/Zephyr-latest/doc/hardware/pinctrl/
Dindex.rst138 perform dynamic pin control, custom identifiers should be placed in a header
150 one should in theory remove the ``sleep`` state from Devicetree to not waste ROM
177 Dynamic pin control should only be used on devices that have not been
180 de-initialization yet, this functionality should only be used during early
349 peripheral working conditions, so the decision should be made by the board.
386 option is better for their devices. However, the following guidelines should be
401 In this section you will find some tips on how a device driver should use the
418 should be used for this purpose. Second, a reference to
/Zephyr-latest/arch/arm/
DKconfig54 In general this option should be chosen if the zephyr,flash chosen node
59 secondary core, this option should be disabled.
108 the specified files and places it in SRAM. The files should be specified
/Zephyr-latest/boards/nxp/lpcxpresso55s36/doc/
Dindex.rst172 The :ref:`jlink-debug-host-tools` should be available in this case.
196 Open a serial terminal, reset the board (press the RESET button), and you should
215 should see the following message in the terminal:
/Zephyr-latest/boards/st/stm32wb5mm_dk/doc/
Dstm32wb5mm_dk.rst114 To operate bluetooth on STM32WB5MMG, Cortex-M0 core should be flashed with
123 compatible anymore for a use in Zephyr and only "HCI Only" versions should be
208 Reset the board and you should see the following messages on the console:
/Zephyr-latest/samples/drivers/virtualization/ivshmem/doorbell/
DREADME.rst109 # assumption: "ivshmem" group should be the only allowed to access ivshmem
184 The guest application should be started before the host one, even though the
196 once the memory is set during PCI configuration, it should not be tampered
/Zephyr-latest/doc/releases/
Dmigration-guide-3.6.rst22 this should switch to using board Kconfig fragments instead (``boards/<board>.conf``).
34 * Build type by setting ``CONF_FILE`` to ``prj_<build>.conf`` is now deprecated, users should
49 * STM32H7 and STM32F7 should now activate the cache (Icache and Dcache) by setting explicitly
56 applications that use this should switch to using the :ref:`boot_mode_api` instead.
80 erase is needed when flashing MCUboot, this should now be provided directly to the ``west``
197 Drivers and applications that are supposed to work in multilevel-interrupt configurations should
238 * The :dtcompatible:`st,hci-spi-v1` should be used instead of :dtcompatible:`zephyr,bt-hci-spi`
456 they now instead should be configured through :kconfig:option:`CONFIG_BT_ATT_TX_COUNT`.
465 call to :c:func:`bt_enable`, and should no longer be re-registered after a :c:func:`bt_disable`
474 application should register the `alloc_seg` channel callback and allocate from the same pool as
[all …]
/Zephyr-latest/doc/services/ipc/ipc_service/backends/
Dipc_service_icbmsg.rst359 …ding message before it starts the binding procedure on that endpoint, it should store the message …
360 It should not send the ``MSG_RELEASE_BOUND`` yet.
385 The newer implementations should be able to work with older ones in backward compatible mode.
388 * If the receiver receives a longer control message, it should use only the first three bytes and i…
389 …e starting with a byte that does not match any of the messages described here, it should ignore it.
390 * If the receiver receives a binding message with additional bytes at the end, it should ignore the…
/Zephyr-latest/boards/arduino/portenta_h7/doc/
Dindex.rst71 Applications for the ``arduino_portenta_h7`` board should be built per core target,
106 You should see the following message on the console:
/Zephyr-latest/boards/arduino/nicla_vision/doc/
Dindex.rst70 Applications for the ``arduino_nicla_vision`` board should be built per core target,
106 You should see the following message on the console:
/Zephyr-latest/include/zephyr/arch/x86/intel64/
Dlinker.ld54 * no sensitive data should be here as Meltdown exploits may read it.
154 /* This should be put here before BSS section, otherwise the .bss.__gcov will
/Zephyr-latest/boards/weact/stm32g431_core/doc/
Dindex.rst19 After these modifications have been made, PA9, PA10, PB2, PB4, and PB6 should be
93 Connect a USB-C cable and the board should power ON. Force the board into DFU mode by
/Zephyr-latest/boards/others/black_f407zg_pro/doc/
Dindex.rst131 In order to enable console output you should use a serial cable and connect
166 You should see user led "LD1" blinking.
/Zephyr-latest/boards/digilent/zybo/doc/
Dindex.rst93 You should see the following message in the terminal:
132 Step through the application in your debugger, and you should see the following message in the
/Zephyr-latest/boards/nxp/frdm_mcxw72/doc/
Dindex.rst118 Open a serial terminal, reset the board (press the RESET button), and you should
137 should see the following message in the terminal:
/Zephyr-latest/boards/adafruit/feather_nrf52840/doc/
Dindex.rst146 ``FTHRSNSBOOT`` (Sense) should appear on the host. Ensure this is
186 #. You should see the red LED blink.
/Zephyr-latest/samples/modules/chre/
DREADME.rst42 Once built and run, the sample application should:
61 community. These should each have their own Kconfig to enable them and set the appropriate
/Zephyr-latest/samples/net/sockets/big_http_download/
DREADME.rst26 - NAT/routing should be set up to allow connections to the Internet
27 - DNS server should be available on the host to resolve domain names
/Zephyr-latest/samples/boards/96boards/argonkey/microphone/
DREADME.rst64 The microphone PDM requested clock should lead the MP34DT05 driver to select an
89 .. note:: The "cat /dev/ttyUSB0 > /tmp/sound.raw" command should be launched after the audio
/Zephyr-latest/doc/kernel/drivers/
Dindex.rst47 values. :ref:`Entropy functions <entropy_api>` should not be
57 should support an interrupt-based implementation, rather than polling, unless
62 these calls should be blocking.
70 are intended for use in device drivers only and should not be used in
257 Public API for device-specific extensions should be prefixed with the
424 pathological/unrecoverable failures, etc., should be handled by
428 check, 0 should be returned on success and a POSIX :file:`errno.h` code

1...<<11121314151617181920>>...51