Searched refs:should (Results 76 – 100 of 1262) sorted by relevance
12345678910>>...51
| /Zephyr-latest/tests/drivers/pinctrl/api/ |
| D | Kconfig | 12 This option should be selected by unit tests that want to store the
|
| /Zephyr-latest/doc/contribute/ |
| D | contributor_expectations.rst | 32 - Smaller PRs should encompass one self-contained logical change.
34 - When adding a new large feature or API, the PR should address only one part of
38 - PRs should include tests or samples under the following conditions:
44 - Fixing a hardware agnostic bug. The test should fail without the bug fixed
77 get reviewed and merged into the project. The RFC should also define the minimum
112 - Commits in a pull request should represent clear, logical units of change that are easy to review
117 Each commit should correspond to a self-contained, meaningful change. For example, adding a
118 feature, fixing a bug, or refactoring existing code should be separate commits. Avoid mixing
131 … temporary files, or debugging code). These should be squashed or rewritten before submitting the
160 The final commit history should be easy to understand for future maintainers. Logical units of
[all …]
|
| /Zephyr-latest/subsys/mgmt/mcumgr/util/ |
| D | CMakeLists.txt | 10 # and should not be exposed outside of mgmt_mcumgr.
|
| /Zephyr-latest/tests/cmake/sysbuild_snippets/ |
| D | Kconfig | 13 This option's value should be overridden by sysbuild.
|
| /Zephyr-latest/tests/drivers/pinctrl/nrf/ |
| D | Kconfig | 12 This option should be selected by unit tests that need to access the pin
|
| /Zephyr-latest/samples/net/secure_mqtt_sensor_actuator/ |
| D | Kconfig | 16 Port through which the application should connect to the MQTT broker.
20 string "The MQTT topic the application should publish data to"
|
| /Zephyr-latest/ |
| D | .gitattributes | 10 # Tell linguist that generated test pattern files should not be included in the
|
| /Zephyr-latest/tests/drivers/pinctrl/gd32/ |
| D | Kconfig | 12 This option should be selected by unit tests that need to access the pin
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfu_srv.rst | 20 started. Each firmware image in the image list must be independently updatable, and should have its
49 Distributor, and should indicate what effect the firmware update will have on the mesh state of the
58 unprovisioned, this should be communicated through the effect parameter of the metadata check.
103 After the BLOB transfer has finished, the application should verify the image in any way it can to
114 <bt_mesh_dfu_srv_cb.apply>` callback. The application should swap the image and start running with
115 the new firmware. The firmware image table should be updated to reflect the new firmware ID of the
120 After booting up with the new firmware, the firmware image table should be updated before the
|
| /Zephyr-latest/soc/microchip/miv/polarfire/ |
| D | Kconfig.defconfig | 8 # MPFS should be configured so that the mtimer clock is 1MHz independent of the CPU clock...
|
| /Zephyr-latest/boards/u-blox/ubx_bmd380eval/ |
| D | ubx_bmd380eval_nrf52840_defconfig | 6 # should be CKAA, but not available yet from Nordic Semiconductor
|
| /Zephyr-latest/samples/subsys/shell/shell_module/boards/ |
| D | intel_socfpga_agilex5_socdk.overlay | 7 * The overlay file should be used to enable any
|
| /Zephyr-latest/samples/bluetooth/mtu_update/ |
| D | README.rst | 67 The first one should be flashed with the central and the second one with the
81 If the devices are close enough, the central should connect to the peripheral
83 should subscribe and then the peripheral will send a large notification. Right
84 after receiving the notification the central should unsubscribe.
86 Here are the outputs you should have on the devices:
|
| /Zephyr-latest/cmake/emu/ |
| D | custom.cmake | 5 # The real 'run' custom_target should be defined in `board.cmake` instead.
|
| /Zephyr-latest/samples/application_development/ |
| D | application_development.rst | 7 For application development you should also consider looking at
|
| /Zephyr-latest/samples/drivers/video/capture/ |
| D | README.rst | 33 On :zephyr:board:`mimxrt1064_evk`, the MT9M114 camera module should be plugged in the
34 J35 camera connector. A USB cable should be connected from a host to the micro
37 On :zephyr:board:`mimxrt1170_evk`, the OV5640 camera module should be plugged into the
38 J2 camera connector. A USB cable should be connected from a host to the micro
|
| /Zephyr-latest/samples/subsys/fs/fs_sample/ |
| D | README.rst | 21 ``mimxrt1050_evk``, ``nrf52840_blip`` and ``olimexino_stm32``. The sample should be able
52 Where used example board ``nrf52840_blip`` should be replaced with desired board.
65 In case when board with SD card is used FAT microSD card should be present in the
88 After starting the sample a contents of a root directory should be printed on the console.
|
| /Zephyr-latest/subsys/mgmt/mcumgr/grp/img_mgmt/ |
| D | Kconfig | 9 # Options defined in this file should be prefixed:
42 operation, an issue that should also be addressed within application.
70 Normally it should not be allowed to confirm any slots of non-active
72 broken and may not boot in other slot; instead application should
80 Normally it should not be allowed to confirm any slots of non-active
82 broken and may not boot in other slot; instead application should
136 registered callbacks to check with the user application if an upload should be accepted
160 MCUboot images should be limited to the maximum size that the bootloader can swap, in
166 confirmed images, if support for that is required then this feature should be left as
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | qemu_setup.rst | 55 should be created.
135 When you are finished with network testing using QEMU, you should stop
156 board is connected to a dedicated router, it should not be needed.
159 a gateway should be set via DHCP or configured manually.
168 (masquerading) should be set up for QEMU's source address. Assuming ``192.0.2.1`` is
169 used and the Zephyr network interface is ``zeth``, the following command should be run as root:
177 Additionally, IPv4 forwarding should be enabled on the host, and you may need to
179 To enable IPv4 forwarding the following command should be run as root:
233 This will start a second QEMU instance, where you should see logging of data sent and
|
| /Zephyr-latest/boards/nordic/nrf52840dongle/ |
| D | nrf52840dongle_nrf52840_defconfig | 12 # Board Kconfig.defconfig enables USB CDC ACM and should disable USB remote
|
| /Zephyr-latest/boards/others/promicro_nrf52840/ |
| D | promicro_nrf52840_nrf52840_defconfig | 12 # Board Kconfig.defconfig enables USB CDC ACM and should disable USB remote
|
| /Zephyr-latest/boards/ct/ctcc/ |
| D | ctcc_nrf52840_defconfig | 12 # Board Kconfig.defconfig enables USB CDC ACM and should disable USB remote
|
| /Zephyr-latest/tests/subsys/nrfs/ |
| D | CMakeLists.txt | 13 " This is a multi-image application that should be built using sysbuild.\n"
|
| /Zephyr-latest/samples/subsys/sensing/simple/ |
| D | app.overlay | 8 * Names in this file should be chosen in a way that won't conflict
|
| /Zephyr-latest/doc/project/ |
| D | issues.rst | 9 Any changes that originate from a tracked feature or issue should contain a
13 At any time it should be possible to establish the origin of a change and the
|
12345678910>>...51
