Home
last modified time | relevance | path

Searched refs:start (Results 301 – 325 of 1113) sorted by relevance

1...<<11121314151617181920>>...45

/Zephyr-latest/arch/arm/core/
Dvector_table.ld9 * In an MCU with VTOR, the VTOR.TBLOFF is set to the start address of the
43 * For AArch32 (M), VTOR has Bits [6:0] = RES0. Thus, vector start address
/Zephyr-latest/drivers/sensor/maxim/
DKconfig4 # zephyr-keep-sorted-start
/Zephyr-latest/drivers/sensor/nxp/
DKconfig4 # zephyr-keep-sorted-start
/Zephyr-latest/drivers/watchdog/
DKconfig.rpi_pico16 Sets the default watchdog timeout at start-up, the feed function must
/Zephyr-latest/tests/drivers/uart/uart_async_api/boards/
Dxmc45_relax_kit.overlay15 fifo-start-offset = <0>;
Dxmc47_relax_kit.overlay20 fifo-start-offset = <0>;
/Zephyr-latest/lib/utils/
Donoff.c145 || (transitions->start == NULL) in onoff_manager_init()
345 transit = mgr->transitions->start; in process_event()
425 bool start = false; /* trigger a start transition */ in onoff_request() local
451 start = (state == ONOFF_STATE_OFF); in onoff_request()
465 if (start) { in onoff_request()
/Zephyr-latest/samples/subsys/usb/testusb/
DREADME.rst10 The userspace tool ``testusb`` is needed to start the tests.
43 to start the tests.
64 to start the tests.
/Zephyr-latest/doc/kernel/usermode/
Dmpu_stack_objects.rst25 about the start, end, size, and access attributes to be enforced on that
53 Some ARM MPUs use start and end addresses to define MPU regions and both the
54 start and end addresses require 32 byte alignment. An example of this kind of
/Zephyr-latest/subsys/bluetooth/mesh/shell/
Dop_agg.c59 SHELL_CMD_ARG(seq-start, NULL, "<ElemAddr>", cmd_seq_start, 2, 0),
/Zephyr-latest/subsys/logging/backends/
DKconfig.semihost23 Enable semihost backend to start automatically.
/Zephyr-latest/soc/andestech/ae350/
DCMakeLists.txt7 start.S
/Zephyr-latest/soc/espressif/common/
DKconfig.amp10 This hidden configuration lets PROCPU core to map and start APPCPU whenever IPM is enabled.
/Zephyr-latest/drivers/mspi/
DKconfig.ambiq21 This option specifies the mspi buffer/heap start address
/Zephyr-latest/drivers/spi/
DCMakeLists.txt7 # zephyr-keep-sorted-start
14 # zephyr-keep-sorted-start
/Zephyr-latest/drivers/flash/
Dflash_max32.c76 static int api_erase(const struct device *dev, off_t start, size_t len) in api_erase() argument
80 uint32_t addr = (start + cfg->flash_base); in api_erase()
Dflash_sam0.c261 off_t start = offset % sizeof(ctx->buf); in flash_sam0_write() local
262 off_t base = offset - start; in flash_sam0_write()
263 size_t len_step = sizeof(ctx->buf) - start; in flash_sam0_write()
269 memcpy(&(ctx->buf[start]), &(pdata[pos]), len_copy); in flash_sam0_write()
/Zephyr-latest/drivers/coredump/
Dcoredump_impl.c72 coredump_memory_dump(region->start, region->start + region->size); in coredump_impl_dump()
/Zephyr-latest/cmake/sca/eclair/ECL/
Dextra.ecl71 …k_mem_slab|k_mem_pool|k_heap|k_mutex|k_stack|k_msgq|k_mbox|k_pipe|k_sem|k_queue)_list_(start|end)$"
73 -extra_definitions+="^z_mapped_(start|end)$"
/Zephyr-latest/samples/net/ptp/
DREADME.rst52 Compile the ``ptp4l`` daemon and start it like this:
66 When the Zephyr image is build, you can start it like this:
/Zephyr-latest/include/zephyr/linker/common-rom/
Dcommon-rom-init.ld18 * Zephyr's start-up code uses the __ZEPHYR_CTOR_LIST__ and
52 * Zephyr's start-up code uses the __zephyr_init_array_start and
/Zephyr-latest/subsys/portability/cmsis_rtos_v1/
Dcmsis_thread.c55 (void)arch_page_phys_get((void *)thread->stack_info.start, &stack_start); in thread_abort_hook()
57 stack_start = thread->stack_info.start; in thread_abort_hook()
/Zephyr-latest/drivers/sensor/ist8310/
Dist8310.h36 uint8_t start, uint8_t *buf, int size);
/Zephyr-latest/include/zephyr/drivers/
Dcoredump.h42 uintptr_t start; member
/Zephyr-latest/subsys/net/lib/shell/
Ddhcpv6.c76 SHELL_CMD_ARG(start, NULL, "Start the Dhcpv6 client operation on the interface.\n"

1...<<11121314151617181920>>...45