Searched refs:start (Results 1051 – 1075 of 1113) sorted by relevance
1...<<4142434445
| /Zephyr-latest/boards/native/native_sim/doc/ |
| D | index.rst | 327 This RTC can also be set to start from time 0 with the ``--rtc-reset`` command
334 After start, this RTC advances with the simulated time, and is therefore
|
| /Zephyr-latest/subsys/net/lib/sockets/ |
| D | sockets_tls.c | 735 static inline int time_left(uint32_t start, uint32_t timeout) in time_left() argument
737 uint32_t elapsed = k_uptime_get_32() - start; in time_left()
|
| /Zephyr-latest/subsys/bluetooth/mesh/ |
| D | dfu_cli.c | 290 .start = tx_start,
|
| D | dfd_srv.c | 921 .start = upload_start,
|
| D | blob_cli.c | 582 .start = send_start, in tx()
|
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | harness.py | 503 reader_t.start()
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | mcp.rst | 127 <dbg> bt_mcc.bt_mcc_discover_mcs: start discovery of MCS primary service
|
| /Zephyr-latest/doc/services/ipc/ipc_service/backends/ |
| D | icbmsg_memory.svg | 165 …="display: flex; align-items: unsafe center; justify-content: unsafe flex-start; width: 148px; hei…
|
| /Zephyr-latest/boards/phytec/reel_board/doc/ |
| D | index.rst | 363 | J22 | open solder jumper | close to start adapter in bootloader mode |
|
| /Zephyr-latest/drivers/can/ |
| D | can_nxp_s32_canxl.c | 1085 .start = can_nxp_s32_start,
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/src/ |
| D | test_blob.c | 220 .start = blob_srv_start,
|
| D | test_dfu.c | 281 .start = target_dfu_start,
|
| /Zephyr-latest/cmake/modules/ |
| D | extensions.cmake | 1166 # Flags that start with -Wno-<warning> can not be tested by
1300 set(rom_start_path "${snippet_base}/snippets-rom-start.ld")
1482 # Note that this assumes windows absolute filenames start with a letter and colon, this does
4911 # SYMBOL <SECTION> : Specify that start symbol of the region should be identical
4912 # to the start address of the first section in the group.
5042 # ENDALIGN <alignment>: Align the end so that next output section will start aligned.
5227 # generate a symbol to mark the start of the objects array for
5325 …_section_configure(SYMBOLS [start_sym [end_sym]]) takes maximum two symbol names (start and end).")
5365 # To create a new symbol `bar` pointing to the start VMA address of section
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.14.rst | 116 * :github:`16080` - Zephyr UART shell crashes on start if main() is blocked
153 * :github:`16779` - [Zephyr v1.14] ARM: fix the start address of MPU guard in stack-fail checking (…
173 * :github:`17288` - Bluetooth: controller: Fix handling of L2CAP start frame with zero PDU length
353 * :github:`16779` - [Zephyr v1.14] ARM: fix the start address of MPU guard in stack-fail checking (…
371 * :github:`17288` - Bluetooth: controller: Fix handling of L2CAP start frame with zero PDU length
1273 * :github:`14663` - net: echo server sends unknown packets on start
1992 * :github:`10662` - "Quick start - Integration testing" does not work as intended.
2170 * :github:`9463` - bt_le_scan_start Fails with Error -5 after 128 scan start/stop cycles
|
| D | release-notes-2.3.rst | 194 interpreted relative to either current time or system start, and be
439 * Added "no auto start" option and local MAC address support to rf2xx
605 * Fixed LWM2M socket error handling, and pending and reply handling during start
1307 * :github:`20068` - Application doesn't start when SHELL-UART is enabled and UART is not connected …
|
| D | release-notes-3.4.rst | 397 * Implemented the CAP initiator broadcast audio start, stop and metadata
399 * Implemented the CAP unicast audio start, stop and metadata update procedures.
1093 * Added new radio API function to start continuous carrier wave transmission.
|
| D | release-notes-3.0.rst | 213 * :c:func:`uart_rx_enable_u16` to start receiving data.
873 * :github:`42778` - bluetooth: autopts: can't start on the board
925 * :github:`42214` - drivers: uart_nrfx_uarte: Cannot start another reception after reception is com…
|
| /Zephyr-latest/drivers/ieee802154/ |
| D | ieee802154_dw1000.c | 1667 .start = dwt_start,
|
| /Zephyr-latest/doc/build/dts/ |
| D | macros.bnf | 5 ; ones that start with DT_ and are directly generated.
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_MMU.txt | 173 start refilling.
|
| /Zephyr-latest/doc/_doxygen/ |
| D | doxygen-awesome.css | 897 align-items: flex-start;
1428 margin-inline-start: 0px;
2472 padding-inline-start: 0px;
|
| /Zephyr-latest/subsys/bluetooth/audio/ |
| D | ascs.c | 2542 if (unicast_server_cb != NULL && unicast_server_cb->start != NULL) { in ase_start()
2543 err = unicast_server_cb->start(ep->stream, &rsp); in ase_start()
|
| /Zephyr-latest/doc/contribute/documentation/ |
| D | guidelines.rst | 85 the start of a paragraph and indent continuation lines with two
93 start with a 1. or a. for example, and continue with autonumbering by
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | board_porting.rst | 206 :ref:`build_overview` is a good place to start learning about the build system.
227 Once you've found an existing board that uses your SoC, you can usually start
|
| /Zephyr-latest/doc/hardware/pinctrl/ |
| D | index.rst | 134 It is important that custom state identifiers start from
|
1...<<4142434445
