Searched refs:header (Results 401 – 425 of 890) sorted by relevance
1...<<11121314151617181920>>...36
| /Zephyr-latest/soc/nxp/rw/ |
| D | Kconfig | 26 bool "Create boot header"
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | ptp.rst | 36 :header: Feature, Supported
64 :header: Management_ID, Management_ID name, Allowed actions
|
| /Zephyr-latest/boards/renesas/da14695_dk_usb/doc/ |
| D | index.rst | 89 written to flash has to have proper header prepended. The process is simplified
90 by using dedicated `eZFlashCLI`_ tool that takes care of writing header and can
|
| /Zephyr-latest/boards/gd/gd32e507v_start/doc/ |
| D | index.rst | 36 :header-rows: 1
88 the JP1 header.
|
| /Zephyr-latest/boards/gd/gd32f350r_eval/doc/ |
| D | index.rst | 41 :header-rows: 1
80 allows flash programming and debugging over USB. There is also a SWD header
|
| /Zephyr-latest/boards/gd/gd32f450v_start/doc/ |
| D | index.rst | 36 :header-rows: 1
82 allows flash programming and debugging over USB. There is also a SWD header
|
| /Zephyr-latest/boards/gd/gd32l233r_eval/doc/ |
| D | index.rst | 40 :header-rows: 1
81 allows flash programming and debugging over USB. There is also a SWD header
|
| /Zephyr-latest/boards/gd/gd32vf103v_eval/doc/ |
| D | index.rst | 43 :header-rows: 1
86 allows flash programming and debugging over USB. There is also a JTAG header
|
| /Zephyr-latest/boards/particle/argon/dts/ |
| D | mesh_feather.dtsi | 70 compatible = "particle-gen3-header";
99 compatible = "adafruit-feather-header";
|
| /Zephyr-latest/boards/particle/boron/dts/ |
| D | mesh_feather.dtsi | 70 compatible = "particle-gen3-header";
99 compatible = "adafruit-feather-header";
|
| /Zephyr-latest/boards/particle/xenon/dts/ |
| D | mesh_feather.dtsi | 70 compatible = "particle-gen3-header";
99 compatible = "adafruit-feather-header";
|
| /Zephyr-latest/tests/subsys/sip_svc/src/ |
| D | main.c | 72 req.header = SIP_SVC_PROTO_HEADER(SIP_SVC_PROTO_CMD_SYNC, 0); in sip_svc_send_sync_request()
152 req.header = SIP_SVC_PROTO_HEADER(SIP_SVC_PROTO_CMD_ASYNC, 0); in sip_svc_send_async_request()
|
| /Zephyr-latest/boards/olimex/stm32_h405/doc/ |
| D | index.rst | 105 EXT1 header
121 EXT2 header
|
| /Zephyr-latest/drivers/can/ |
| D | can_mcp251xfd.c | 67 memcpy(&spi_data->header[1], &spi_cmd, sizeof(spi_cmd)); in mcp251xfd_read_reg()
69 struct spi_buf tx_buf = {.buf = &spi_data->header[1], .len = MCP251XFD_SPI_CMD_LEN + len}; in mcp251xfd_read_reg()
70 struct spi_buf rx_buf = {.buf = &spi_data->header[1], .len = MCP251XFD_SPI_CMD_LEN + len}; in mcp251xfd_read_reg()
94 struct spi_buf tx_buf = {.buf = &spi_data->header[0], in mcp251xfd_read_crc()
99 struct spi_buf rx_buf = {.buf = &spi_data->header[0], in mcp251xfd_read_crc()
108 memcpy(&spi_data->header[0], &spi_cmd, sizeof(spi_cmd)); in mcp251xfd_read_crc()
109 spi_data->header[2] = len; in mcp251xfd_read_crc()
116 (uint8_t *)(&spi_data->header[0]), in mcp251xfd_read_crc()
150 struct spi_buf tx_buf = {.buf = &spi_data->header[1], .len = MCP251XFD_SPI_CMD_LEN + len}; in mcp251xfd_write()
154 memcpy(&spi_data->header[1], &spi_cmd, sizeof(spi_cmd)); in mcp251xfd_write()
|
| /Zephyr-latest/soc/intel/intel_adsp/common/include/ |
| D | manifest.h | 148 struct sof_man_fw_header header; member
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | index.rst | 16 The output from Kconfig is a header file :file:`autoconf.h` with macros that
|
| /Zephyr-latest/boards/nordic/nrf5340dk/ |
| D | nrf5340dk_common.dtsi | 53 compatible = "arduino-header-r3";
|
| /Zephyr-latest/drivers/sensor/st/lsm6dsv16x/ |
| D | lsm6dsv16x_rtio_stream.c | 265 rx_data->header.is_fifo = 1; in lsm6dsv16x_read_fifo_cb()
266 rx_data->header.timestamp = lsm6dsv16x->fifo_timestamp; in lsm6dsv16x_read_fifo_cb()
318 .header = { in lsm6dsv16x_read_fifo_cb()
|
| /Zephyr-latest/scripts/build/ |
| D | gen_app_partitions.py | 130 partitions[partition_name] = {SZ: section.header.sh_size}
136 partitions[partition_name][SZ] += section.header.sh_size
|
| /Zephyr-latest/boards/gd/gd32f450z_eval/doc/ |
| D | index.rst | 47 :header-rows: 1
99 allows flash programming and debugging over USB. There is also a JTAG header
|
| /Zephyr-latest/boards/gd/gd32f470i_eval/doc/ |
| D | index.rst | 48 :header-rows: 1
103 allows flash programming and debugging over USB. There is also a JTAG header
|
| /Zephyr-latest/boards/st/steval_fcu001v1/doc/ |
| D | index.rst | 106 The programmer is attached to the P8 programming header with ARM-JTAG-20-10-Plug-in Adapter.
112 the P7 header of the steval_fcu001v1 board. Then run a serial host
|
| /Zephyr-latest/boards/atmel/sam0/samr21_xpro/ |
| D | samr21_xpro.dts | 59 compatible = "atmel-xplained-pro-header";
82 compatible = "atmel-xplained-pro-header";
|
| /Zephyr-latest/subsys/secure_storage/ |
| D | Kconfig | 44 The header is made available when this Kconfig option is enabled.
92 The header is made available when this Kconfig option is enabled.
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | syscalls.rst | 30 will be declared in some header under ``include/`` or in another
83 Any header file that declares system calls must include a special generated
84 header at the very bottom of the header file. This header follows the
85 naming convention ``syscalls/<name of header file>``. For example, at the
104 ``zephyr_syscall_header_ifdef`` are used to specify which header
106 present in the final binaries. Note that header files inside
142 C and header files by the :ref:`gen_syscalls.py` script, all of which can be found in
153 prototypes are declared in header files when
171 The body of the API is created in the generated system header. Using the
177 Inside this header is the body of :c:func:`k_sem_init()`::
[all …]
|
1...<<11121314151617181920>>...36
