Searched refs:will (Results 176 – 200 of 1633) sorted by relevance
12345678910>>...66
| /Zephyr-latest/share/sysbuild/cmake/modules/ |
| D | sysbuild_extensions.cmake | 8 # This function will load the CMakeCache.txt file from the binary directory
25 # Using a regex for matching whole 'VAR_NAME:TYPE=VALUE' will strip semi-colons
49 # This function will return the variable found in the CMakeCache.txt file
51 # If `VAR` is provided, the name given as parameter will be looked up, but if
52 # `VAR` is not given, the `<variable>` name provided will be used both for
55 # The result will be returned in `<variable>`.
59 # will lookup PROJECT_NAME from the CMakeCache identified by `my_sample` and
63 # will lookup PROJECT_NAME from the CMakeCache identified by `my_sample` and
67 # will lookup CONFIG_FOO from the KConfig identified by `my_sample` and
161 # The sysbuild BOARD is exported through sysbuild cache, and will be used
[all …]
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | Kconfig | 57 # needed e.g. for unit tests. This default will also server as
82 or bt_recv_prio(). The choice will influence RAM usage and how fast incoming HCI
88 When this option is selected, the host will process incoming low priority HCI packets
90 High priority HCI packets will processed in the context of the caller of bt_recv().
93 Note: When this option is used, other users of the system work queue will influence the
99 When this option is selected, the host will process incoming low priority HCI packets
101 High priority HCI packets will processed in the context of the caller of bt_recv().
187 When selected, will use PSA Crypto API library for random number generation.
188 This will consume additional ram, but may speed up the generation of random
191 Otherwise, random numbers will be generated through multiple HCI calls,
[all …]
|
| /Zephyr-latest/samples/subsys/display/cfb_shell/ |
| D | README.rst | 110 of the display the remaining characters will be displayed on the next line. The
111 previous printed text will be overwritten.
122 remaining characters will be displayed in the next line. The text will scroll
124 for vertical direction. The text passed with the scroll command will be moved
|
| /Zephyr-latest/soc/nordic/nrf54l/ |
| D | Kconfig | 59 will copy all the trimming values from FICR into the target
73 will be constant and kept at a minimum. This is secured by forcing a set
75 and predictable latency will be at the cost of having increased power consumption.
|
| /Zephyr-latest/cmake/modules/ |
| D | arch_v1.cmake | 11 # This CMake module will set the following variables in the build system based
14 # If no implementation is available for the current arch an error will be raised.
17 # The following variables will be defined when this CMake module completes:
|
| /Zephyr-latest/drivers/display/ |
| D | Kconfig.mcux_dcnano_lcdif | 23 Note that hardware will likely perform best if zero driver
47 does not overlap with other data. Each allocated LCDIF buffer will
49 and buffers will be allocated contiguously.
|
| /Zephyr-latest/samples/net/gptp/ |
| D | Kconfig | 6 # This sample application will have three network interfaces.
7 # gPTP protocol will run in the non-VLAN interface and then there
8 # will be two VLAN interface for other use. This is just an example
|
| /Zephyr-latest/samples/boards/ti/cc13x2_cc26x2/system_off/ |
| D | README.rst | 42 4. Device will turn off the external flash, which is on by default, to
44 5. Device will demonstrate active, idle and standby modes.
45 6. Device will explicitly turn itself off by going into shutdown mode.
|
| /Zephyr-latest/ |
| D | .gitignore | 24 # The .cache directory will be used to cache toolchain capabilities if
69 # Normal west builds will place the Rust target directory under the build directory. However,
70 # sometimes IDEs and such will litter these target directories as well.
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | overview.rst | 38 - Access to thread stack buffers will be controlled with a policy which
41 - A user thread will by default have read/write access to its own stack
44 - A user thread will never by default have access to user thread stacks
47 - A user thread will never by default have access to thread stacks owned
124 simultaneously, after which creation of new user threads will fail.
135 - Any user thread will only have access to a subset of memory:
168 space will generate a hardware fault. The way this is done specifically
176 kernel objects will need to go through pre-defined pools of available objects.
181 - Loaded object code will not be able to define any kernel objects that will be
182 recognized by the kernel. This code will instead need to use APIs for
[all …]
|
| /Zephyr-latest/drivers/i3c/ |
| D | Kconfig.stm32 | 31 storing status FIFO and control FIFO words which will be used by the DMA.
32 This value depends on the maximum number of messages that will be sent
|
| /Zephyr-latest/drivers/sensor/microchip/mchp_tach_xec/ |
| D | Kconfig | 22 will be used to determine the interval for which the number of
23 100KHz pulses will be counted.
|
| /Zephyr-latest/drivers/gpio/ |
| D | Kconfig.pca_series | 39 When disabled, only output registers will be cached.
40 On devices w/o interrupt status, it will also cache
|
| /Zephyr-latest/samples/bluetooth/iso_receive/ |
| D | README.rst | 29 another board that will start periodic advertising, create BIG to which this
30 sample will establish periodic advertising synchronization and synchronize to
|
| /Zephyr-latest/boards/ezurio/bl654_usb/ |
| D | Kconfig.defconfig | 16 # When building MCUBoot, MCUBoot itself will select USE_DT_CODE_PARTITION
17 # which will make it link into the correct partition specified in DTS file,
|
| /Zephyr-latest/boards/microchip/mec172xmodular_assy6930/ |
| D | CMakeLists.txt | 15 …message(WARNING "Microchip SPI Image Generation tool is not available. SPI Image will not be gener…
23 …p SPI Image Generation tool configuration file is not available. SPI Image will not be generated.")
|
| /Zephyr-latest/boards/nordic/nrf7002dk/ |
| D | Kconfig | 26 The board which will be used for CPUNET domain when creating a multi
43 The board which will be used for CPUAPP domain when creating a multi
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | net-stack-architecture.rst | 76 :ref:`BSD socket API <bsd_sockets_interface>`, the following things will
94 These queues will process incoming packets with different priority.
115 7. The application will then receive the data and can process it as needed.
118 that will receive the data.
142 5. The network stack will check that the network interface is properly set
143 for the network packet, and also will make sure that the network interface
149 transmit queues. These queues will process the sent packets with different
152 correct L2 layer module. The L2 module will do additional checks for the
153 data and it will also create any L2 headers for the network packet.
157 7. The device driver will send the packet to the network.
|
| /Zephyr-latest/doc/services/llext/ |
| D | build.rst | 11 <llext_build_native_>`_. This will result in a single build providing both the
12 main Zephyr application and the extension(s), which will all automatically be
49 - ``<target_name>`` is the name of the final CMake target that will result in
51 - ``<ext_file.llext>`` is the name of the output file that will contain the
53 - ``<src1> [<src2>...]`` is the list of source files that will be compiled to
96 that will be executed during the extension build process. The command will be
128 Anything else after ``COMMAND`` will be passed to ``add_custom_command()`` as-is
208 If set, the EDK will include headers that do not contain code to route
209 syscalls to the kernel. This is useful when building extensions that will
|
| /Zephyr-latest/samples/net/cloud/aws_iot_mqtt/ |
| D | README.rst | 41 script, which will generate files ``ca.c``, ``cert.c`` and ``key.c``.
47 console. This will be specific if running a test suite using device advisor.
50 with the certificate it will be used as the client id. We will use
71 topic. The device console will display the payload received by your device, and
72 the AWS console will show the JSON message sent by the device under the
107 The sample can be run in QEMU x86. To do so, you will need to configure
|
| /Zephyr-latest/arch/x86/zefi/ |
| D | README.txt | 6 the symbol table) for the target as its sole argument. It will emit a
17 Instead, the stub code will copy the embedded zephyr sections to the
22 binary into memory and copy it vs. a bootloader like grub that will
38 And if you forget this and use a global by mistake, the build will
59 the compiler (not the linker) knows a-priori will never be in
67 they ignore the preferred load address and will put the image at
80 that the EFI environment will load our image at an address that
|
| /Zephyr-latest/drivers/flash/ |
| D | Kconfig.mcux | 18 WARNING: This driver will disable the system interrupts for
19 the duration of the flash erase/write operations. This will
21 this is acceptable or not will depend on the use case.
31 devices will crash when reading an erased or wrongly programmed area.
|
| D | Kconfig.stm32 | 48 If enabled, all requests to disable flash write protection will be
67 With this option enabled it will be possible to disable readout
68 protection. On STM32 devices it will trigger flash mass erase!
75 With this option enabled it will be possible to enable readout
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig.native_posix | 33 then this value is used as a prefix and the interface names will be
61 Native posix ethernet driver will strip of VLAN tag from
73 means the code will make 00:00:5E:00:53:XX, where XX will be
|
| /Zephyr-latest/samples/bluetooth/mesh/ |
| D | README.rst | 19 On boards with buttons, a Generic OnOff Client model will send Onoff messages
63 When self-provisioning, the device will take a random unicast address and
66 Once provisioned, messages to the Generic OnOff Server will be used to turn
67 the LED on or off, and button presses will be used to broadcast OnOff
|
12345678910>>...66
