Searched refs:starts (Results 101 – 125 of 131) sorted by relevance
123456
| /Zephyr-latest/boards/nxp/imx95_evk/doc/ |
| D | index.rst | 241 aspects of the hardware such as isolation mechanisms and then starts other cores in the
|
| /Zephyr-latest/drivers/wifi/nxp/ |
| D | Kconfig.nxp | 402 bool "Automatically starts STA connection"
431 bool "Automatically starts STA Reconnection"
438 bool "Automatically starts Power Save support"
|
| /Zephyr-latest/doc/services/storage/zms/ |
| D | zms.rst | 30 This behavior is repeated until it reaches the end of the partition. Then it starts again from
102 Mounting the storage system starts by getting the flash parameters, checking that the file system
|
| /Zephyr-latest/doc/hardware/peripherals/can/ |
| D | controller.rst | 64 and Extended identifiers concurrently. A CAN frame starts with a dominant
|
| /Zephyr-latest/doc/build/dts/ |
| D | phandles.rst | 122 Each "group" starts with a phandle (``&foo``, ``&bar``, ``&baz``). The values
|
| D | macros.bnf | 10 ; A dt-macro starts with uppercase "DT_", and is one of:
|
| /Zephyr-latest/doc/services/shell/ |
| D | index.rst | 572 When user starts writing a command and presses the :kbd:`Tab` button then
629 - Preserves the last command on the screen and starts a new command in
|
| /Zephyr-latest/drivers/wifi/esp32/ |
| D | Kconfig.esp32 | 49 bool "Automatically starts DHCP4 negotiation"
|
| /Zephyr-latest/boards/qemu/x86/ |
| D | qemu_x86_tiny.ld | 46 /* "kernel RAM" for linker VMA allocations starts at the offset */
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | access.rst | 263 * Between 20 to 500 milliseconds when the Bluetooth Mesh stack starts or when the publication is
|
| D | shell.rst | 316 Provision a nearby device into the mesh. The mesh node starts scanning for unprovisioned
332 Provision a nearby device into the mesh. The mesh node starts scanning for connectable
374 be set before provisioning starts to have any effect. The static OOB value must be same on
|
| /Zephyr-latest/subsys/shell/backends/ |
| D | Kconfig.backends | 226 data periodically. Period starts from 1-2 milliseconds and can be
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | memory_domain.rst | 177 domain membership from their parent thread. The main thread starts as a
|
| /Zephyr-latest/doc/project/ |
| D | release_process.rst | 93 At that point, the whole process starts over again.
|
| /Zephyr-latest/drivers/wifi/nrf_wifi/ |
| D | Kconfig.nrfwifi | 476 Note that if a frame is sent after the SP starts, it will be queued, and this
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | lwm2m.rst | 371 Lastly, we start the LwM2M RD client (which in turn starts the LwM2M engine).
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | index.rst | 432 The following code spawns a thread that starts immediately.
|
| /Zephyr-latest/dts/bindings/ |
| D | vendor-prefixes.txt | 8 # Anything that starts with a '#' is treated as a comment and ignored.
|
| /Zephyr-latest/doc/services/tracing/ |
| D | index.rst | 337 This decides when the tracing starts. With the option :guilabel:`Start`, the tracing begins directly
|
| /Zephyr-latest/doc/kernel/services/ |
| D | interrupts.rst | 139 thread A is swapped out and the next ready thread B starts to
|
| /Zephyr-latest/doc/services/logging/ |
| D | index.rst | 309 dedicated task which starts automatically. However, it might not be available
|
| /Zephyr-latest/arch/ |
| D | Kconfig | 844 If RAM starts at 0x0, the first page must remain un-mapped to catch NULL
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | Kconfig | 782 starts the first connection parameters update procedure after a
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-3.3.rst | 2813 - :github:`54705` - CDC USB shell receives garbage when application starts
2906 * :github:`54457` - DHCPv4 starts even when interface is not operationally up
3263 * :github:`52190` - [lpcxpresso55s28] flash range starts from Secure address which is not compatibl…
3663 * :github:`43330` - usb_dc_nrfx.c starts usbd_work_queue with no name
|
| D | release-notes-1.13.rst | 700 * :github:`3187` - frdm_k64f: Ethernet networking starts to respond ~10s after boot
|
123456
