Searched refs:should (Results 51 – 75 of 1262) sorted by relevance
12345678910>>...51
| /Zephyr-latest/samples/boards/st/ccm/ |
| D | README.rst | 16 The __ccm_data_section prefix should be used for variables that
20 The __ccm_bss_section prefix should be used for variables that
21 should be initialized to 0. Like the normal bss section they
24 The __ccm_noinit_section prefix should be used for variables
93 uninitialized data. After writing to the variables, they all should hold the
139 it still should be considered uninitialized leftover data.
|
| /Zephyr-latest/drivers/ieee802154/ |
| D | Kconfig.rf2xx | 20 The default value should be sufficient, but in case it proves to be
29 be ready first (and sometime gpio should be the very first as spi
|
| D | Kconfig.dw1000 | 19 count. The SNIFF_ONT value should be in range of 1-15.
35 be ready first (and sometime gpio should be the very first as spi
|
| /Zephyr-latest/doc/develop/sca/ |
| D | sparse.rst | 12 attribute which should be used to cast pointers between different address
21 To run a sparse verification build :ref:`west build <west-building>` should be
|
| /Zephyr-latest/tests/bsim/bluetooth/host/misc/sample_test/ |
| D | CMakeLists.txt | 35 # the test and should be in the same file as the test entry point. Any other
40 # characteristic UUIDs, test data that should be verified by both parties,
43 # Ideally, main.c should only set up the test framework, and map the entry
|
| /Zephyr-latest/samples/drivers/soc_flash_nand/boards/ |
| D | intel_socfpga_agilex5_socdk.overlay | 6 /* The overlay file should be used to enable any
|
| /Zephyr-latest/tests/subsys/mgmt/mcumgr/handler_demo/example_as_module/ |
| D | CMakeLists.txt | 6 # The below should be updated with the real name of the file
|
| /Zephyr-latest/samples/subsys/shell/shell_module/boards/ |
| D | intel_socfpga_agilex_socdk.overlay | 7 * The overlay file should be used to enable any
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig.ipv6 | 10 Enable IPv6 support. This should be selected by default as there
46 The value should normally be 1280 which is the minimum IPv6 packet
66 The value should normally be > 0. The device receiving the IPv6
76 The value should normally be > 0. The device receiving the IPv6
95 should not cause issues normally as we support anyway the minimum
121 (RFC 2460 ch 5). This means that we should receive everything
143 The value depends on your network needs. MLD should normally
151 The value depends on your network needs. Neighbor cache should
160 The value depends on your network needs. ND should normally
168 The value depends on your network needs. DAD should normally
[all …]
|
| /Zephyr-latest/soc/nxp/imxrt/imxrt6xx/ |
| D | Kconfig | 49 Set the external oscillator frequency in Hz. This should be set by the
55 Set the board system oscillator settling time in us. This should be set by the
|
| /Zephyr-latest/doc/services/dsp/ |
| D | index.rst | 48 zDSP backend to better support it. To do that, a new Kconfig option should be
52 Next, the implementation should be added at ``subsys/dsp/<backend>/`` and
54 its corresponding Kconfig option should be added to :file:`subsys/dsp/Kconfig` and use
|
| /Zephyr-latest/samples/basic/custom_dts_binding/ |
| D | README.rst | 23 We assume that a load with high current demands should be switched on or off via a MOSFET. The
32 For each board that should be supported, a ``.overlay`` file has to be defined
48 The GPIO pin should be switched to active level after one second.
|
| /Zephyr-latest/boards/tdk/robokit1/doc/ |
| D | index.rst | 58 Both west flash and west debug commands should correctly work with both USB0 and USB1
65 terminal should be :code:`/dev/ttyACM0`. For example:
72 string. Connection should be configured as follows:
88 You should see "Hello World! robokit1" in your terminal.
|
| /Zephyr-latest/samples/subsys/modbus/tcp_gateway/ |
| D | README.rst | 17 but it should work with any board or shield that has a network interface.
27 The A+, B- lines of the RS-485 shields should be connected together.
59 Client should confirm successful communication and LED0 should light.
|
| /Zephyr-latest/samples/net/sockets/echo_client/boards/ |
| D | intel_socfpga_agilex5_socdk.overlay | 6 /* The overlay file should be used to enable any
|
| /Zephyr-latest/samples/net/sockets/echo_server/boards/ |
| D | intel_socfpga_agilex5_socdk.overlay | 6 /* The overlay file should be used to enable any
|
| /Zephyr-latest/doc/contribute/ |
| D | reviewer_expectations.rst | 35 reviewers should add suggestions as a comment to the :ref:`RFC <rfcs>`. This
40 requests as "Non-blocking" in the comment. Reviewers should approve PRs once
42 they address all non-blocking comments. PR authors should acknowledge every
51 - Whenever requesting style related changes, reviewers should be able to point
63 - Reviewers should not request changes for issues which are automatically
|
| /Zephyr-latest/doc/project/ |
| D | proposals.rst | 34 The following workflow should be used to process features:.
39 should assign the request to themselves.
59 by any project member or the community. You should contact an assigned owner if
67 they have very different purposes and should not be confused. A project roadmap
80 The project roadmap should serve as a high-level, visual summary of the
89 As such, the roadmap should contain only strategic-level details, major project
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | op_agg_cli.rst | 20 should be bound to the same application keys as the client models that are used to produce the
23 To be able to aggregate a message from a client model, it should support an asynchronous API, for
|
| /Zephyr-latest/samples/modules/mctp/mctp_endpoint/ |
| D | README.rst | 19 The listening UART pins should be wired to a board which will run the MCTP host
22 grounds should also be wired together.
|
| /Zephyr-latest/samples/modules/mctp/mctp_host/ |
| D | README.rst | 19 The UART pins should be wired to a board which will run the MCTP endpoint
22 boards' grounds should also be wired together.
|
| /Zephyr-latest/samples/posix/gettimeofday/ |
| D | README.rst | 20 - NAT/routing should be set up to allow connections to the Internet
21 - DNS server should be available on the host to resolve domain names
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/host/ |
| D | gatt.rst | 6 To perform service discovery on the client side, use the :code:`gatt discover` command. This should
10 command. When done, you should see the newly added services on the client side when running the
|
| /Zephyr-latest/samples/boards/st/power_mgmt/adc/ |
| D | README.rst | 18 The board should support enabling PM. For a STM32 based target, it means that
19 it should support a clock source alternative to Cortex Systick that can be used
|
| /Zephyr-latest/soc/xen/ |
| D | Kconfig.defconfig | 13 # 32M should be enough for basic use-cases
|
12345678910>>...51
