Searched refs:should (Results 376 – 400 of 1262) sorted by relevance
1...<<11121314151617181920>>...51
| /Zephyr-latest/samples/subsys/console/getchar/ |
| D | README.rst | 12 character or blocks waiting for one. Using this function, it should be
|
| /Zephyr-latest/samples/subsys/console/getline/ |
| D | README.rst | 12 line or blocks waiting for one. Using this function, it should be fairly
|
| /Zephyr-latest/samples/boards/st/power_mgmt/wkup_pins/ |
| D | README.rst | 21 The SoC should support POWEROFF functionality & have a wake-up pin that corresponds
|
| /Zephyr-latest/doc/develop/tools/ |
| D | coccinelle.rst | 101 It should be used with the C option (described later)
257 The ``<headerfile.h>`` should contain the complete prototype of
301 developers. For sake of clarity, they should be organized in the
304 The cocci script should have the following properties:
308 * The first few lines should state the purpose of the script
344 in the script. The virtual rule specified in the script should have
571 coccilib.org.print_todo(p[0], "WARNING should use ARRAY_SIZE")
580 …r/src/cborvalidation.c::face=ovl-face1::linb=328::colb=52::cole=53][WARNING should use ARRAY_SIZE]]
|
| /Zephyr-latest/soc/nxp/imxrt/ |
| D | Kconfig | 22 # should be set elsewhere, since the determination of which SOC core
133 setting should be enabled when the application uses SDRAM, or
141 This setting should be enabled when the application uses HYPERRAM,
|
| /Zephyr-latest/doc/project/ |
| D | working_groups.rst | 28 - A working group should aim to have at least five to seven members to
30 - The structure of each working group within the Zephyr Project should be
115 group should cover:
|
| /Zephyr-latest/boards/cdns/xt-sim/doc/ |
| D | index.rst | 121 sections that should be added to the default linker script linker.ld (inside
123 and add these sections. The memory segment and PHDR should be replaced by
126 The linker script should be named ``linker.ld`` and placed in the directory
|
| /Zephyr-latest/drivers/wifi/esp32/ |
| D | Kconfig.esp32 | 111 it should be at least the number of static RX buffers.
129 If PSRAM is enabled, "Static" should be selected to guarantee enough
130 WiFi TX buffers. If PSRAM is disabled, "Dynamic" should be selected
221 …In order to prevent memory fragmentation, the management buffer type should be set to static first.
246 higher throughput but more memory. Most of time we should NOT change the
267 we should NOT change the default value unless special reason,
271 should be 16 to achieve better throughput and compatibility with both
|
| /Zephyr-latest/arch/x86/ |
| D | Kconfig | 13 # CPU Families - the SoC configuration should select the right one.
364 This hidden option should be set on a per-SOC basis to indicate that
371 This hidden option should be set on a per-SOC basis to indicate that
379 This hidden option should be set on a per-SOC basis to indicate that
386 This hidden option should be set on a per-SOC basis to indicate that
393 This hidden option should be set on a per-SOC basis to indicate
405 This hidden option should be set on a per-SOC basis to indicate that
|
| /Zephyr-latest/doc/connectivity/usb/device_next/ |
| D | usb_device.rst | 84 descriptors. To instantiate these string descriptors, the application should
107 The application should use :c:macro:`USBD_CONFIGURATION_DEFINE` to instantiate
155 steps, which should be performed prior to initializing the USB device.
193 host. A generic application should use :c:func:`usbd_can_detect_vbus` to check
243 should be called from the interrupt handler, see
252 Simplified, the interrupt handler should look something like:
|
| /Zephyr-latest/doc/develop/test/ |
| D | bsim.rst | 182 - Scripts expect that the binaries they require are already built. They should not compile binaries.
186 - Neither the scripts nor the images should modify the workstation filesystem content beyond the
188 That is, they should not leave stray files behind.
190 off, and powering up after as a new simulation) should use separate simulation ids for each
198 - Tests should not be overly verbose: less than a hundred lines are expected on the outputs. Do make
|
| /Zephyr-latest/boards/nxp/frdm_mcxn947/doc/ |
| D | index.rst | 238 Open a serial terminal, reset the board (press the RESET button), and you should
277 In order to load Zephyr application from QSPI you should program a bootloader like
285 Open a serial terminal, reset the board (press the RESET button), and you should
313 should see the following message in the terminal:
323 For dual core builds, the secondary core should be placed into a loop,
|
| /Zephyr-latest/samples/subsys/smf/smf_calculator/ |
| D | README.rst | 39 The GUI should work with any touchscreen display supported by Zephyr. The shield
49 The demo should also work on STM32 Discovery Kits with built-in touchscreens e.g.
|
| /Zephyr-latest/samples/boards/nordic/dynamic_pinctrl/ |
| D | README.rst | 80 #. Turn on the board. You should see a ``Hello World!`` message printed on
88 nRF52840 DK) and press the board reset button. You now should see a
|
| /Zephyr-latest/drivers/flash/ |
| D | Kconfig | 39 This option should be selected by drivers that serve devices with
59 This option should be selected by drivers that serve
64 This option should be selected for any device that
137 Value selected here should be a multiple of the largest write-block-size
|
| /Zephyr-latest/boards/microchip/mec172xmodular_assy6930/doc/ |
| D | mec172xmodular_assy6930.rst | 215 Under Linux the terminal should be :code:`/dev/ttyUSB0`. Do not close it.
224 string. Connection should be configured as follows:
241 #. You should see ``"Hello World! mec172xmodular_assy6930"`` in the first terminal window.
242 If you don't see this message, press the Reset button and the message should appear.
|
| /Zephyr-latest/doc/hardware/emulator/ |
| D | bus_emulators.rst | 45 works, we should expect the application and peripheral drivers to work on the
167 address ``0x20`` should be sent to ``i2c1`` with the same address. This allows
172 The ``#forward-cells`` attribute should always be 1. Each entry in the
177 should remain 1.
|
| /Zephyr-latest/doc/develop/west/ |
| D | basics.rst | 48 Here are the basic concepts you should understand about this structure.
168 should run ``west update`` to make sure your workspace contains the
180 It then uses the manifest file to decide where missing projects should be
182 revisions should be checked out locally. Project repositories which already
|
| /Zephyr-latest/soc/infineon/cat1a/ |
| D | Kconfig | 37 Cortex-M0 CPU should boot Cortex-M4
|
| /Zephyr-latest/samples/subsys/usb/uac2_implicit_feedback/ |
| D | README.rst | 30 Theoretically it should be possible to obtain the timing information based on
|
| /Zephyr-latest/scripts/ci/ |
| D | twister_ignore.txt | 37 # if we change this file or associated script, it should not trigger a full
|
| /Zephyr-latest/scripts/coccinelle/ |
| D | array_size.cocci | 79 coccilib.org.print_todo(p[0], "WARNING should use ARRAY_SIZE")
|
| /Zephyr-latest/subsys/dsp/ |
| D | Kconfig | 39 Rely on the application to provide a custom DSP backend. The implementation should be
|
| /Zephyr-latest/doc/services/ |
| D | notify.rst | 31 from a user mode thread the subsystem or driver should provide a syscall
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/host/ |
| D | l2cap.rst | 33 On device A, you should have received the data:
|
1...<<11121314151617181920>>...51
