| /Zephyr-latest/samples/subsys/fs/format/ |
| D | README.rst | 5 Format different storage devices for different file systems.
10 This sample shows how to format different storage
11 devices for different file systems. There are 2 scenarios prepared for this
|
| /Zephyr-latest/tests/drivers/spi/spi_loopback/src/ |
| D | spi.c | 101 /* test transferring different buffers on the same dma channels */
143 LOG_ERR("Buffer contents are different: %s", buffer_print_tx); in spi_complete_multiple()
145 zassert_false(1, "Buffer contents are different"); in spi_complete_multiple()
152 LOG_ERR("Buffer 2 contents are different: %s", buffer_print_tx2); in spi_complete_multiple()
154 zassert_false(1, "Buffer 2 contents are different"); in spi_complete_multiple()
200 LOG_ERR("Buffer contents are different: %s", buffer_print_tx); in spi_complete_loop()
202 zassert_false(1, "Buffer contents are different"); in spi_complete_loop()
304 LOG_ERR("Buffer contents are different: %s", buffer_print_tx); in spi_rx_half_start()
306 zassert_false(1, "Buffer contents are different"); in spi_rx_half_start()
362 LOG_ERR("Buffer contents are different: %s", buffer_print_tx); in spi_rx_half_end()
[all …]
|
| D | spi_rtio.c | 81 /* test transferring different buffers on the same dma channels */
111 LOG_ERR("Buffer contents are different: %s", buffer_print_tx); in spi_complete_multiple()
113 zassert_false(1, "Buffer contents are different"); in spi_complete_multiple()
120 LOG_ERR("Buffer 2 contents are different: %s", buffer_print_tx2); in spi_complete_multiple()
122 zassert_false(1, "Buffer 2 contents are different"); in spi_complete_multiple()
157 LOG_ERR("Buffer contents are different: %s", buffer_print_tx); in spi_complete_loop()
159 zassert_false(1, "Buffer contents are different"); in spi_complete_loop()
243 LOG_ERR("Buffer contents are different: %s", buffer_print_tx); in spi_rx_half_start()
245 zassert_false(1, "Buffer contents are different"); in spi_rx_half_start()
298 LOG_ERR("Buffer contents are different: %s", buffer_print_tx); in spi_rx_half_end()
[all …]
|
| /Zephyr-latest/tests/subsys/fs/fcb/src/ |
| D | fcb_test_reset.c | 25 "fcb_walk: elements count read different than expected"); in ZTEST()
37 "fcb_walk: elements count read different than expected"); in ZTEST()
56 "fcb_walk: elements count read different than expected"); in ZTEST()
72 "fcb_walk: elements count read different than expected"); in ZTEST()
91 "fcb_walk: elements count read different than expected"); in ZTEST()
113 "fcb_walk: elements count read different than expected"); in ZTEST()
136 "fcb_walk: elements count read different than expected"); in ZTEST()
|
| D | fcb_test_append_fill.c | 63 "fcb_walk: elements count read different than expected"); in ZTEST()
65 "fcb_walk: elements count read different than expected"); in ZTEST()
75 "fcb_walk: elements count read different than expected"); in ZTEST()
77 "fcb_walk: elements count read different than expected"); in ZTEST()
|
| D | fcb_test_rotate.c | 69 "fcb_walk: entry count got different than expected"); in ZTEST()
71 "fcb_walk: entry count got different than expected"); in ZTEST()
96 "fcb_walk: entry count got different than expected"); in ZTEST()
98 "fcb_walk: entry count got different than expected"); in ZTEST()
|
| /Zephyr-latest/tests/benchmarks/sched_queues/ |
| D | README.rst | 4 A Zephyr application developer may choose between three different scheduling
5 algorithms: dumb, scalable and multiq. These different algorithms have
6 different performance characteristics that vary as the
|
| /Zephyr-latest/boards/nxp/frdm_rw612/ |
| D | CMakeLists.txt | 11 # for boards with different flash chips. If you flash this FCB
12 # onto a board with a different flash chip you may break it.
|
| /Zephyr-latest/samples/subsys/logging/syst/ |
| D | prj.conf | 6 # If using a different backend such as "ADSP"
8 # Note: If using different platforms, be sure to
|
| /Zephyr-latest/dts/bindings/dac/ |
| D | nxp,lpdac.yaml | 19 different for different SoCs.
|
| /Zephyr-latest/samples/tfm_integration/tfm_psa_test/ |
| D | README.rst | 78 [Check 7] Call get API for different UID 5
79 [Check 8] Call get_info API for different UID 5
80 [Check 9] Call remove API for different UID 5
90 [Check 7] Call get API for different UID 5
91 [Check 8] Call get_info API for different UID 5
92 [Check 9] Call remove API for different UID 5
|
| /Zephyr-latest/dts/bindings/pinctrl/ |
| D | nxp,imx-iomuxc.yaml | 55 different register layouts. This property can be set to indicate
62 different register layouts. This property can be set to indicate
69 different register layouts. This property can be set to indicate
76 different register layouts. This property can be set to indicate
|
| /Zephyr-latest/tests/subsys/logging/log_switch_format/ |
| D | prj.conf | 6 # If using a different backend such as "ADSP"
8 # Note: If using different platforms, be sure to
|
| /Zephyr-latest/samples/subsys/llext/edk/ |
| D | README.rst | 19 run in different contexts. Extensions ``ext1``, ``ext2`` and ``ext3`` run in
20 userspace, each demonstrating different application and Zephyr API usage, such as
25 The application also creates different memory domains for each extension, thus
40 One could build the extensions in different directories, not related to the
41 Zephyr application - even on different machines, using only the EDK. At the
43 different teams, using the EDK provided by the application developer.
|
| /Zephyr-latest/soc/atmel/sam0/common/ |
| D | gmac_fixup_samd5x.h | 9 * APB-specific symbols, in order to accommodate different SoC series with the
10 * GMAC core connected to different APBs.
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | hwinfo.rst | 13 example due to a watchdog timeout or due to power cycling. Different devices
14 support different subset of flags. Use
|
| /Zephyr-latest/tests/kernel/common/ |
| D | multilib.txt | 5 Some architectures support different ISA variants, each backed a different
|
| /Zephyr-latest/subsys/mgmt/mcumgr/grp/img_mgmt_client/ |
| D | Kconfig | 27 Change default value when platform needs different data alignment.
33 Change default value when platform needs a different time.
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | channels.rst | 9 Sensors may have multiple channels, either to represent different axes of
11 different properties altogether (ambient temperature, pressure and
|
| /Zephyr-latest/dts/bindings/rtc/ |
| D | nordic,nrf-rtc.yaml | 22 # If enabled, overflow different than full range (24 bits) is handled
25 # of counter period if top value is different than maximal.
|
| /Zephyr-latest/samples/basic/servo_motor/ |
| D | README.rst | 17 Different servomotors may require different PWM pulse widths, and you may need
18 to modify the source code if you are using a different servomotor.
|
| /Zephyr-latest/scripts/native_simulator/common/src/include/ |
| D | nsi_main.h | 22 * Note that other components may have requested a different
33 * Note that other components may have requested a different
|
| /Zephyr-latest/doc/develop/sca/ |
| D | sparse.rst | 10 spaces in C code with subsequent verification that pointers to different
12 attribute which should be used to cast pointers between different address
|
| /Zephyr-latest/include/zephyr/arch/arc/v2/mpu/ |
| D | arc_core_mpu.h | 18 * Each MPU is different and has a different set of attributes, hence instead
21 * An intent type (i.e. THREAD_STACK_GUARD) can correspond to a different set
|
| /Zephyr-latest/soc/nordic/ |
| D | CMakeLists.txt | 16 # DT values against the MDK, without having to conditionally include different
17 # headers for different SoCs.
|
