Home
last modified time | relevance | path

Searched refs:will (Results 101 – 125 of 1633) sorted by relevance

12345678910>>...66

/Zephyr-latest/doc/develop/test/
Dztest.rst21 test will run. The predicate will get a pointer to the global state passed in through
24 will be called and run once per test suite run.
25 * :c:type:`ztest_suite_before_t` - An optional before function which will run before every single
27 * :c:type:`ztest_suite_after_t` - An optional after function which will run after every single
29 * :c:type:`ztest_suite_teardown_t` - An optional teardown function which will run at the end of
57 that when :kconfig:option:`CONFIG_USERSPACE` is enabled, then the test will be run in a userspace
60 that the test function will already include a variable named ``fixture`` with the type
69 the same suite will require some initial setup followed by some form of reset between each test.
137 /** This will fail the test */
144 /** This will skip the test */
[all …]
/Zephyr-latest/samples/subsys/usb/hid-mouse/
DREADME.rst16 will be performed on every button click if the bus is in suspended state.
25 the board level that can generate input events, otherwise the example will build
45 This sample can be built for multiple boards, in this example we will build it
56 The board will be detected as shown by the Linux dmesg command:
97 When you press the button on your board, it will act as if the left
98 mouse button was pressed, and this information will be displayed
110 If your board has more than one button, they will act as right mouse button,
/Zephyr-latest/samples/bluetooth/peripheral_accept_list/
DREADME.rst11 If no device is bonded to the peripheral, casual advertising will be performed.
12 Once a device is bonded, on subsequent boots, connection requests will only be
14 data will only be sent to devices that are on the accept list. As a result, some
/Zephyr-latest/boards/qemu/arc/
Dboard.cmake22 # to 'virt' board. It will be renamed in ARC QEMU in the nearest Zephyr SDK
23 # (where ARCv3 HS6x support will be added to QEMU)
25 # until the updated Zephyr SDK will be set as default. By that we keep both SDKs
/Zephyr-latest/tests/benchmarks/wait_queues/
DREADME.rst17 times. However, if the verbose option is enabled then the raw timings will also
18 be displayed. The following will build this project with verbose support:
28 the summary statistics will be parsed as data records.
/Zephyr-latest/samples/subsys/fs/fs_sample/
DKconfig15 "some.dir" directory and "other.txt" file will be created
16 and list will run again to show them. This is useful when
/Zephyr-latest/samples/subsys/llext/modules/
DKconfig16 If you select 'm', the hello_world function will be built as an llext
17 "module". If you select 'y', the hello_world function will be directly
/Zephyr-latest/samples/bluetooth/direction_finding_central/boards/
Dnrf52833dk_nrf52820.overlay13 /* This is an example switch pattern that will be used to set an
19 * Radio peripheral. The pins will be acquired by Radio to
/Zephyr-latest/samples/bluetooth/direction_finding_connectionless_rx/boards/
Dnrf52833dk_nrf52820.overlay13 /* This is an example switch pattern that will be used to set an
19 * Radio peripheral. The pins will be acquired by Radio to
Dnrf52833dk_nrf52833.overlay13 /* This is an example switch pattern that will be used to set an
19 * Radio peripheral. The pins will be acquired by Radio to
/Zephyr-latest/samples/bluetooth/direction_finding_peripheral/boards/
Dnrf52833dk_nrf52820.overlay13 /* This is an example switch pattern that will be used to set an
19 * Radio peripheral. The pins will be acquired by Radio to
/Zephyr-latest/samples/bluetooth/hci_ipc/
Dnrf5340_cpunet_df-bt_ll_sw_split.overlay13 /* This is an example switch pattern that will be used to set an
19 * Radio peripheral. The pins will be acquired by Radio to
/Zephyr-latest/boards/raytac/mdbt53_db_40/
DKconfig12 The board which will be used for CPUNET domain when creating a multi
25 The board which will be used for CPUAPP domain when creating a multi
/Zephyr-latest/boards/raytac/mdbt53v_db_40/
DKconfig12 The board which will be used for CPUNET domain when creating a multi
25 The board which will be used for CPUAPP domain when creating a multi
/Zephyr-latest/boards/nordic/nrf5340dk/
DKconfig12 The board which will be used for CPUNET domain when creating a multi
24 The board which will be used for CPUAPP domain when creating a multi
/Zephyr-latest/samples/bluetooth/direction_finding_connectionless_tx/boards/
Dnrf52833dk_nrf52820.overlay13 /* This is an example switch pattern that will be used to set an
19 * Radio peripheral. The pins will be acquired by Radio to
Dnrf52833dk_nrf52833.overlay13 /* This is an example switch pattern that will be used to set an
19 * Radio peripheral. The pins will be acquired by Radio to
/Zephyr-latest/boards/nordic/nrf5340_audio_dk/
DKconfig12 The board which will be used for CPUNET domain when creating a multi
25 The board which will be used for CPUAPP domain when creating a multi
/Zephyr-latest/samples/net/vlan/
DREADME.rst10 The VLAN sample application for Zephyr will setup two virtual LAN networks.
57 If everything is configured correctly, you will be able to successfully execute
67 The network packets to ``2001:db8:100::1`` or ``198.51.100.1`` will have VLAN
68 tag 100 set to them. The vlan tag 200 will be set to network packets to
/Zephyr-latest/doc/kernel/services/other/
Dfatal.rst49 perform optional runtime checks which will induce a fatal error if the
50 check does not pass. The macro takes a string message which will be printed
51 to provide context to the assertion. In addition, the kernel will print
130 ``static_assert``. If the evaluation fails, a build error will be generated by
131 the compiler. If the compiler supports it, the provided message will be printed
162 The fatal error reason code generated will be ``K_ERR_KERNEL_OOPS``.
174 and doing so will generate a kernel oops instead. Otherwise, the fatal error
175 reason code generated will be ``K_ERR_KERNEL_PANIC``.
185 then the kernel will generate a fatal error with the reason code
196 as the thread will simply not have permission to write to adjacent memory
[all …]
/Zephyr-latest/soc/espressif/esp32s3/
DKconfig25 then the other 16KB will be managed by heap allocator.
76 If enabled, instruction cache will use wrap mode to read spi flash or spi ram.
86 the other 32KB will be added to the heap.
98 # For 16KB the actual configuration is 32kb cache, but 16kb will be reserved for heap at startup
144 If enabled, data cache will use wrap mode to read spi flash or spi ram.
153 If enabled, the MAC and baseband of Wi-Fi and Bluetooth will be powered
/Zephyr-latest/doc/develop/west/
Dwithout-west.rst8 particular, you will have to do work "by hand" to replace these
27 Otherwise, Zephyr's build system will find it and may try to use
34 you will need to manually clone the additional projects listed in the
45 As you pull changes in the zephyr repository, you will also need to
62 When building with west installed, the Zephyr build system will use it to set
66 these repositories, the build will still work.
75 west, you will need to download and place those blobs in the right places
85 those targets will fail. You can of course still flash and debug using
/Zephyr-latest/doc/kernel/services/smp/
Dsmp.rst14 a supported dual processor device, they will both run simultaneously.
18 a uniprocessor kernel will be built. In general the platform default
19 will have enabled this anywhere it's supported. When enabled, the
21 :kconfig:option:`CONFIG_MP_MAX_NUM_CPUS`. Likewise, the default for this will be the
23 typical apps will change it. But it is legal and supported to set
40 does not: the fact that your CPU will not be interrupted while you are
42 will be running simultaneously and be inspecting or modifying the same
65 re-acquire it or it will deadlock (it is perfectly legal to nest
83 threads. The kernel will ensure that only one thread across all CPUs
86 when a thread is switched in. Other CPUs will spin waiting for the
[all …]
/Zephyr-latest/drivers/serial/
DKconfig.altera_jtag18 Enabling this will disable poll_in and interrupt driven api.
26 This is a helper config. Altera JTAG UART driver will support interrupt,
/Zephyr-latest/soc/nxp/imx/imx6sx/
DKconfig.defconfig.mcimx6x_m415 #-Disable this option if you use the bin format as this choice will enlarge it.
18 # will be filled in the bin file.

12345678910>>...66