Searched refs:will (Results 276 – 300 of 1633) sorted by relevance
1...<<11121314151617181920>>...66
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig.debug | 11 Specific debugging options to other sub-menus will be unlocked
40 This MUST not be used unless you have an hard to catch bug. This will
42 will not segfault, but just bail out and hopefully it will enable you
|
| /Zephyr-latest/cmake/linker/lld/ |
| D | target.cmake | 14 # NOTE: ${linker_script_gen} will be produced at build-time; not at configure-time
23 # for Makefile generators and will be ignored by other generators.
43 # NB: 'linker_script_dep' will use a keyword that ends 'DEPENDS'
112 # This function will generate the correct CMAKE_C_LINK_EXECUTABLE / CMAKE_CXX_LINK_EXECUTABLE
|
| /Zephyr-latest/drivers/counter/ |
| D | Kconfig.xec | 12 will expose the basic timer devices present on the MCU.
|
| /Zephyr-latest/samples/drivers/led/led_strip/boards/ |
| D | bbc_microbit.overlay | 14 chain-length = <16>; /* arbitrary; change at will */
|
| /Zephyr-latest/share/sysbuild/cmake/modules/ |
| D | sysbuild_root.cmake | 7 # This CMake module will convert all relative paths in existing ROOT lists to
17 # If a root is defined it will check the list of paths in the root and convert
19 # If a root is undefined it will still be undefined when this module has loaded.
|
| /Zephyr-latest/soc/atmel/sam0/common/ |
| D | Kconfig.samd2x | 64 Selects the clock that will be used for the DFLL48M's reference.
65 Main clocks, such as the CPU and AHB clocks will be derived from
71 This choice will leave all clocks to their current state.
|
| /Zephyr-latest/samples/sensor/lps22hh_i3c/ |
| D | README.rst | 35 Since IBI is initiated by the sensor, it will take over the I3C
37 to reset the sensor so that it will not generate IBIs anymore.
38 Or else the I3C controller will not be able to be initialized,
|
| /Zephyr-latest/cmake/modules/ |
| D | soc_v1.cmake | 7 # This CMake module will set the following variables in the build system based
10 # If no implementation is available for the selected SoC an error will be raised.
13 # The following variables will be defined when this CMake module completes:
|
| /Zephyr-latest/samples/drivers/ipm/ipm_mhu_dual_core/ |
| D | README.rst | 14 1. CPU 0 will wake up CPU 1 after initialization
15 2. CPU 1 will send to CPU 0 an interrupt over MHU0
64 Reset the board and the following message will appear on the corresponding
|
| /Zephyr-latest/samples/net/sockets/echo/ |
| D | README.rst | 43 After a connection is made, the application will echo back any line sent
52 Linux. (Note: if you look at the source, you will see that the code is
82 the IP address will be printed to the console upon running this echo
|
| /Zephyr-latest/boards/native/doc/ |
| D | arch_soc.rst | 90 Therefore interrupts, including timer interrupts, will not arrive
104 If busy wait loops do exist, they will behave as infinite loops and
105 will stall the execution. For example, the following busy wait loop code,
106 which could be interrupted on actual hardware, will stall the execution of
114 updated by an interrupt handler or another thread, will also stall
123 - Code that depends on its own execution speed will normally not
124 work as expected. For example, code such as shown below, will likely not
147 If a busy wait loop exists, it will become evident as the application will be
149 pause it after the execution is stuck; it will be paused in
180 :kconfig:option:`CONFIG_USERSPACE` will always be disabled,
[all …]
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | memory_domain.rst | 11 All of the discussion below will be using MPU terminology; systems with MMUs
16 Zephyr memory protection features are enabled, which we will describe here:
37 this will require an additional MPU region. This is required so that
60 will either crash in mysterious ways or behave in an undefined manner when the
66 exception will be generated.
72 and no extra MPU regions will be required.
77 Any thread running in user mode will need access to its own stack buffer.
79 page table entries will be programmed with the bounds of the stack buffer.
80 A thread exceeding its stack buffer will start pushing data onto memory
81 it doesn't have access to and a memory access violation exception will be
[all …]
|
| /Zephyr-latest/subsys/bluetooth/crypto/ |
| D | CMakeLists.txt | 15 Private security keys such as the Long Term Key will be printed out.
|
| /Zephyr-latest/drivers/misc/grove_lcd_rgb/ |
| D | Kconfig | 9 Setting this value will enable driver support for the Grove-LCD RGB
|
| /Zephyr-latest/arch/xtensa/ |
| D | CMakeLists.txt | 10 will spill registers on behalf of the userspace. Use it carefully.")
|
| /Zephyr-latest/samples/net/capture/ |
| D | README.rst | 10 This application will setup the device so that net-shell can be used
51 The script will create following network interfaces:
151 The ``net capture`` command will show current configuration. As we have not
168 The tunneling interface will be UP and the captured packets will be sent to
202 packet will be sent to ``192.0.2.2`` in tunnel to ``2001:db8:200::2``
206 The actual captured network packets received at the end of the tunnel will look
|
| /Zephyr-latest/samples/net/gptp/ |
| D | README.rst | 10 The gPTP sample application for Zephyr will enable gPTP support, registers
42 The net-shell command "**net gptp**" will print out general gPTP information.
43 For port 1, the command "**net gptp 1**" will print detailed information about
55 the ``net-setup.sh`` will create VLAN setup automatically with this command:
63 the IEEE 801.1AS network. Note that OpenAVNU will not work with
125 By default gPTP in Zephyr will not print any gPTP debug messages to console.
152 will create multiple TSN ports. This configuration is currently only supported
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | main.rst | 98 /* Callback struct where the callback will be stored */
237 …uch as :c:func:`conn_mgr_if_connect` or :c:func:`conn_mgr_if_disconnect`) will be routed to the co…
250 If association succeeds, the connectivity implementation will mark the iface as operational-up (see…
252 …nrecoverably, the :ref:`fatal error event <conn_mgr_control_events_fatal_error>` will be triggered.
266 If connectivity is lost due to external factors, the connectivity implementation will mark the ifac…
277 In this case, the connectivity implementation will disassociate the iface from its network and mark…
278 A new connection attempt will not be initiated, regardless of whether persistence is enabled.
306 In that case, the connection attempt will be abandoned if the timeout elapses before it succeeds.
318 If persistence is enabled, any unintentional connection loss will initiate a new connection attempt…
320 Otherwise, the iface will not attempt to reconnect.
[all …]
|
| /Zephyr-latest/drivers/i2s/ |
| D | Kconfig.sam_ssc | 30 If enabled RF signal is connected to RF pin. It will be configured as
41 If enabled RK signal is connected to RK pin. It will be configured as
|
| /Zephyr-latest/drivers/sensor/ams/tsl2591/ |
| D | Kconfig | 16 If set, the driver will automatically wait for the duration of an integration cycle
22 If set, the driver will warn if the sensor ADC is
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | installation_win.rst | 17 Windows 10 version 1803 has an issue that will cause CMake to not work
24 For the Zephyr SDK to function properly you will need Windows 10
|
| /Zephyr-latest/samples/sensor/mhz19b/ |
| D | README.rst | 37 The application will perform runtime configuration of the sensor, then
38 read back the sensor configuration data. After that it will read the CO2
|
| /Zephyr-latest/cmake/linker/ld/ |
| D | linker_libraries.cmake | 9 # Keeping default include dir empty. The linker will then select libraries
11 # specific location, for example gcc infrastructure will set the value based
|
| /Zephyr-latest/samples/boards/st/power_mgmt/wkup_pins/ |
| D | README.rst | 13 The system will power off automatically ``WAIT_TIME_US`` us after boot.
38 The LED will be turned off when the system is powered off.
|
| /Zephyr-latest/samples/net/sockets/coap_client/ |
| D | README.rst | 16 This sample will make a GET request with path 'test' to the IPv6
27 This project will print all the octets of the response received, more context can
|
1...<<11121314151617181920>>...66
