Home
last modified time | relevance | path

Searched refs:will (Results 201 – 225 of 1633) sorted by relevance

12345678910>>...66

/Zephyr-latest/samples/bluetooth/mesh_provisioner/
DREADME.rst21 for the user to press the button, which will trigger provisioning using
22 PB-ADV. If the board doesn't have the push button, the sample will
24 node will be present in the CDB but not yet marked as configured. The
25 application will notice the unconfigured node and start configuring it.
/Zephyr-latest/modules/
DKconfig.mcuboot97 When signing with imgtool then this setting will be passed as version
147 MCUboot will only boot slot0_partition placed application and does
157 in DT and application will boot from slot0_partition.
166 to be present in DT, and application will boot from slot0_partition.
178 MCUboot will take contents of secondary slot of an image and will
183 that the overwrite will not happen unless the version of secondary
192 will select the image with the higher version number, copy it to RAM and begin execution
204 In this mode MCUboot can boot from either partition and will
219 In this mode MCUboot will boot the application with the higher version
222 for test it needs to confirm itself, on the first boot, or it will
[all …]
/Zephyr-latest/samples/boards/nxp/mimxrt595_evk/system_off/
DREADME.rst35 3. Device will turn on and idle for 2 seconds
36 4. Device will turn itself off using deep power down mode. RTC alarm
37 will wake device and restart the application from a warm reset.
57 This sample will not resume the application after waking from Deep Power
64 DPD because the MCU will set the PMIC_MODE pins to 0b00 requesting the
65 PMIC to enter the default boot mode, and the PMIC will enable the
66 regulator driving the VDDCORE rail at 1.0V. However, the MCU will not be
101 USB peripheral of the MCU, and will also power the EVK.
/Zephyr-latest/tests/cmake/snippets/extra_snippet_root/snippets/bar/
Dbar.overlay5 /* This node will be deleted by the `foo` snippet if applied. */
/Zephyr-latest/subsys/bluetooth/audio/
DKconfig.pbp11 Enabling this will enable PBP.
/Zephyr-latest/drivers/dma/
DKconfig.nxp_edma23 driver will return an error upon configuration.
31 the CPU will be interrupted when CITER = BITER and
/Zephyr-latest/boards/nxp/mimxrt1160_evk/
Dmimxrt1160_evk_mimxrt1166_cm4.dts20 * sram region is changed and DMA is in use, you will
51 * timer will be used instead of systick, as allows the core clock to
/Zephyr-latest/doc/develop/manifest/
Dindex.rst14 The projects below are enabled by default and will be downloaded when you
32 The projects below are optional and will not be downloaded when you
51 To use any of the projects below, you will need to define your own manifest
/Zephyr-latest/subsys/usb/device/class/dfu/
DKconfig54 When enabled the device will automatically reboot after a download
60 When enabled the image written to slot 1 will be marked as permanent.
62 Downloading the wrong image will cause a bricked device.
/Zephyr-latest/tests/bsim/bluetooth/
Dtests.nrf52bsim.txt1 # Search paths(s) for tests which will be run in the nrf52bsim
/Zephyr-latest/doc/develop/api/
Dterminology.rst18 if the function can be safely called and will have its specified
22 initialized and will have its specified effect when invoked from that
77 will not replace a running cooperative-only thread at a reschedule point
81 This attribute does not imply the function will sleep unconditionally,
100 that will not cause the invoking thread to sleep.
138 function will return a specific error (generally ``-EWOULDBLOCK``).
172 operation it initiates has completed. An asynchronous function will
177 will always be complete when the function returns. As most functions
190 no-wait path only guarantees that the function will not sleep. It does
191 not affect whether the operation will be completed before the function
/Zephyr-latest/samples/subsys/mgmt/hawkbit/
DREADME.rst22 an available update, it will install the update. You can access the sample
74 This will start the hawkbit server on the host system.Opening your browser to
100 The firmware will be signed automatically by the build system with the
113 Once the image is flashed and booted, the sample will print the image build
122 build the sample again, so that the build time will be different.
146 And then wait. The board will ping the server, check if there are any new
148 fine the message ``Update installed`` will be printed on the terminal.
150 Your board will reboot automatically and then start with the new image. After rebooting, the
151 board will print a different image build time then automatically ping the server
152 again and the message ``Image is already updated`` will be printed on the terminal.
[all …]
/Zephyr-latest/samples/userspace/shared_mem/boards/
Dnucleo_f756zg.overlay10 * Otherwise one region will be missing from the 8 MPU regions
/Zephyr-latest/tests/kernel/mem_protect/userspace/boards/
Dnucleo_f756zg.overlay10 * Otherwise one region will be missing from the 8 MPU regions
/Zephyr-latest/doc/kernel/services/timing/
Dclocks.rst56 For example: :c:func:`k_ms_to_ticks_ceil32` will convert a
59 :c:func:`k_cyc_to_us_floor64` will convert a measured cycle count
88 Conceptually, this indicates the time at which an event will occur.
93 routine will return with an error code if no data is available.
99 indicating when a work queue item will be added to the system queue.
112 time" will already have advanced. This is to ensure that timers scheduled from
113 within another timer's callback will always be calculated with a precise offset
123 :c:macro:`K_CYC()` specify timeout values that will expire after specified
127 being 32 bits. Large uptime counts in non-tick units will experience
129 timing-sensitive applications with long uptimes will be configured to
[all …]
/Zephyr-latest/soc/atmel/sam0/common/
DKconfig.samd5x26 clock and AHB clock, will be derived from.
31 This choice will leave all clocks to their current state.
DKconfig.saml2x15 If you are confident that you will never attach a debugger to the
51 Selects the clock that will be used for the DFLL48M's reference.
52 Main clocks, such as the CPU and AHB clocks will be derived from
83 keeping nRST pin low. When enabling this option, both CS and nRST will
/Zephyr-latest/include/zephyr/linker/
Dkobject-text.ld8 * The linker will error out complaining that the location pointer
26 /* In a valid build the MAX function will always evaluate to the
/Zephyr-latest/boards/nxp/mimxrt1170_evk/
Dmimxrt1170_evk_mimxrt1176_cm4.dts20 * sram region is changed and DMA is in use, you will
51 * timer will be used instead of systick, as allows the core clock to
/Zephyr-latest/samples/boards/phytec/reel_board/mesh_badge/
DREADME.rst31 #. Press "Send" - this will trigger pairing since this is a protected
32 characteristic. The passkey for the pairing will be shown on the board's
34 #. Once pairing is complete the board will show the text you sent. If
43 word (name) of the stored text will be sent to all other boards in
/Zephyr-latest/samples/basic/servo_motor/
DREADME.rst26 will need to do something like this:
49 You will need to connect the motor's red wire to external 5V, the black wire to
57 This sample can be built for multiple boards, in this example we will build it
/Zephyr-latest/kernel/
DKconfig.device10 When enabled, device dependencies will be stored so that they can be
12 devicetree. Enabling this option will increase ROM usage (or RAM if
32 If enabled, additional data from the devicetree will be stored for
/Zephyr-latest/tests/cmake/snippets/snippets/foo/
Dfoo.overlay5 /* This node will be deleted by the `bar` snippet if applied. */
/Zephyr-latest/doc/connectivity/networking/api/
Dnet_config.rst17 The following Kconfig options affect how configuration library will
38 ``net_config_init()`` will return error during the device startup."
42 If :kconfig:option:`CONFIG_NET_IPV4` is not enabled, then setting this option will
47 If :kconfig:option:`CONFIG_NET_IPV6` is not enabled, then setting this option will
71 the library will call ``net_config_init()`` automatically and the application
/Zephyr-latest/subsys/bluetooth/common/
DKconfig18 In a combined build this value will be set in both the Host and the
21 In a Host-only build the Host will read the maximum ACL size supported
26 will fragment L2CAP PDUs into ACL data packets.
27 The Controller will return this value in the HCI LE Read Buffer
29 Layer transmission size then the Controller will perform
32 then this will restrict the maximum Link Layer transmission size.
48 The Controller will return this value in the HCI LE Read Buffer Size
66 Host and the Controller will use this value for buffer sizes, making
70 the Host will inform the Controller about the maximum ACL data size it
77 In a Controller only build this will determine the maximum ACL size
[all …]

12345678910>>...66