Searched refs:should (Results 226 – 250 of 1262) sorted by relevance
12345678910>>...51
| /Zephyr-latest/tests/arch/arm/arm_thread_swap_tz/boards/ |
| D | nucleo_l552ze_q_stm32l552xx_ns.overlay | 8 /* This partition table should be used along with TFM configuration:
|
| /Zephyr-latest/drivers/entropy/ |
| D | Kconfig.nrf_cracen | 17 driver should be selected instead.
|
| /Zephyr-latest/tests/drivers/build_all/mdio/ |
| D | app.overlay | 8 * Names in this file should be chosen in a way that won't conflict
|
| /Zephyr-latest/samples/net/secure_mqtt_sensor_actuator/ |
| D | README.rst | 48 The temperature sensor should be aliased in devicetree as ``ambient-temp0``.
89 - By connecting the board to your internet router, it should automatically be assigned
95 The CA cert should be included in the build as described above.
96 ``CONFIG_NET_SAMPLE_MQTT_BROKER_HOSTNAME`` should be configured to match the
117 The device, gateway, and DNS server IP addresses should be set according to
133 broker (i.e. IP address of Ethernet port on host PC). These addresses should be in the
|
| /Zephyr-latest/boards/atmel/sam/sam4s_xplained/doc/ |
| D | index.rst | 104 terminal should be :code:`/dev/ttyACM0`. For example:
111 Connection should be configured as follows:
120 You should see "Hello World! sam4s_xplained" in your terminal.
|
| /Zephyr-latest/boards/atmel/sam0/samd21_xpro/doc/ |
| D | index.rst | 110 terminal should be :code:`/dev/ttyACM0`. For example:
117 string. Connection should be configured as follows:
132 You should see "Hello World! samd21_xpro" in your terminal.
|
| /Zephyr-latest/drivers/ieee802154/ |
| D | Kconfig.cc1200 | 17 The default value should be sufficient, but in case it proves to be
26 be ready first (and sometime gpio should be the very first as spi
72 This value should follow what has been set in the RF settings via
|
| /Zephyr-latest/boards/adafruit/trinket_m0/doc/ |
| D | index.rst | 97 terminal should be :code:`/dev/ttyACM0`. For example:
104 string. Connection should be configured as follows:
121 You should see "Hello World! adafruit_trinket_m0" in your terminal.
|
| /Zephyr-latest/subsys/ipc/ipc_service/backends/ |
| D | Kconfig.icbmsg | 24 so this value should be maximum number among all the instances.
|
| /Zephyr-latest/boards/bbc/microbit_v2/ |
| D | board.cmake | 9 # in which case the following line should be removed to default back to "jlink" OpenOCD interface
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | tmap.rst | 6 devices. Thus both the initiator and acceptor (or central and peripheral) should do a discovery of
|
| /Zephyr-latest/doc/project/ |
| D | communication.rst | 16 In general, bug reports and other issues should be reported as `GitHub Issues
|
| /Zephyr-latest/boards/nxp/common/ |
| D | segger-ecc-systemview.rst | 10 address provided to the tool should be the location of the ``_SEGGER_RTT``
|
| /Zephyr-latest/samples/subsys/debug/fuzz/ |
| D | Kconfig | 9 via interrupts. The IRQ should be otherwise unused, but can
|
| /Zephyr-latest/samples/boards/nxp/adsp/number_crunching/ |
| D | CMakeLists.txt | 18 # this should set the INCLUDE_DIR, LIB_DIR and LIB_NAME variables
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | syscalls.rst | 12 Private kernel data should never be made available to user mode threads
18 supervisor mode should never be exposed as system calls. Reserve these
67 ``int foo[]`` or ``int foo[12]`` is not allowed, but should instead be
80 unimplemented system calls. Data type definitions for APIs should not have
240 validation of any parameters is optional and should be done with assertions.
275 Verification functions should be declared using these macros.
316 fails. The latter should only be used for the most obvious of tests.
330 provided value, which should be the address of the specific driver's
429 bytes processed. This too should use a stack copy:
444 Many system calls pass in structures or even linked data structures. All should
[all …]
|
| /Zephyr-latest/boards/shields/frdm_kw41z/doc/ |
| D | index.rst | 40 storage device should enumerate.
51 The jumpers should be parallel to the Arduino headers. This configuration
|
| /Zephyr-latest/subsys/mgmt/mcumgr/transport/ |
| D | Kconfig | 10 # Options defined in this file should be prefixed:
48 In case when MCUMGR_TRANSPORT_SHELL is enabled this value should be set to
|
| /Zephyr-latest/ |
| D | .gitlint | 5 # verbosity should be a value between 1 and 3, the commandline -v flags take precedence over this
32 # Comma-separated list of words that should not occur in the title. Matching is case
|
| /Zephyr-latest/arch/arm/core/mpu/ |
| D | Kconfig | 51 SoC definition should likely provide its own custom MPU regions.
67 it should consume less alignment memory. Although this alignment
|
| /Zephyr-latest/dts/arm/st/f3/ |
| D | stm32f302.dtsi | 26 /* I2C clock source should always be defined,
42 /* I2C clock source should always be defined,
|
| /Zephyr-latest/samples/basic/rgb_led/ |
| D | README.rst | 14 indicated in Devicetree. Such period should be fast enough to be above the
51 Otherwise, LEDs should be connected to the appropriate PWM channels.
|
| /Zephyr-latest/boards/cypress/cy8ckit_062_ble/doc/ |
| D | index.rst | 159 terminal should be :code:`/dev/ttyACM0`. For example:
166 string. Connection should be configured as follows:
181 You should see "Hello World! cy8ckit_062_ble" in your terminal.
195 header. Schematic should be checked for connections. Run your favorite
197 terminal should be :code:`/dev/ttyUSB0`. For example:
204 string. Connection should be configured as follows:
268 The P9 pins are available at J2. Those signals should be routed to J6.
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | shields.rst | 32 the default shield configuration here should be consistent with those in
37 shield configuration should be done by keeping in mind that features
77 This should be done at two different level:
79 * Pinmux: Connector pins should be correctly configured to match shield pins
82 :file:`BOARD.dts` should define an alternate nodelabel for each connector interface.
|
| /Zephyr-latest/doc/safety/ |
| D | safety_overview.rst | 113 as an existing pre-condition and therefore the "quality managed" status should be pursued for any
166 should not limit compliance to initial scope. This step requires tooling,
195 technical level what the software should do, and on the other hand, it is an important and
258 functionalities should be able to be turned off. The Zephyr Project already offers such a
277 #. On the main branch, the safety scope of the project should be identified, which typically
278 represents a small subset of the entire code base. This subset should then be made auditable
285 fall within the safety scope, the safety architect should ideally be involved in the discussions
289 safety architect should bring it to the attention of the Safety Committee or the Technical
294 "auditable" state, and ideally no further changes should be necessary or made to the code base.
298 safety architect, must decide whether this bug fix or change should be integrated into the LTS
[all …]
|
12345678910>>...51
