Searched refs:read (Results 751 – 775 of 1064) sorted by relevance
1...<<31323334353637383940>>...43
/Zephyr-latest/boards/nxp/mimxrt1064_evk/ |
D | mimxrt1064_evk.dts | 160 ahb-read-addr-opt;
|
/Zephyr-latest/boards/dragino/lsn50/doc/ |
D | index.rst | 53 - Up to 192 KB Flash, 2 banks read-while-write, proprietary code readout protection
|
/Zephyr-latest/boards/dragino/nbsn95/doc/ |
D | index.rst | 52 - Up to 192 KB Flash, 2 banks read-while-write, proprietary code readout protection
|
/Zephyr-latest/tests/bluetooth/gatt/src/ |
D | main.c | 433 ret = attr->read(NULL, attr, (void *)buf, sizeof(buf), 0); in ZTEST()
|
/Zephyr-latest/boards/atmel/sam/sam_v71_xult/ |
D | sam_v71_xult-common.dtsi | 296 read-only;
|
/Zephyr-latest/subsys/net/lib/sockets/ |
D | sockets_packet.c | 472 .read = packet_sock_read_vmeth,
|
/Zephyr-latest/subsys/shell/ |
D | shell_cmds.c | 97 (void)sh->iface->api->read(sh->iface, &c, in cursor_position_get()
|
/Zephyr-latest/boards/nordic/nrf7002dk/doc/ |
D | index.rst | 265 The nRF5340 has a flash read-back protection feature. When flash read-back
|
/Zephyr-latest/doc/hardware/porting/ |
D | arch.rst | 392 can be used to send all output to a circular buffer that can be read 594 CPU features for this purpose, or special read-only guard regions immediately 710 read-only region when the thread is created. 907 * Hardware register read/write functions: 978 * :c:macro:`GDB_MEM_REGION_RO`: region is read-only. 980 * :c:macro:`GDB_MEM_REGION_RW`: region is read-write. 982 * :c:member:`gdb_mem_region.alignment` specifies read/write alignment 984 and read/write can be done byte-by-byte.
|
/Zephyr-latest/arch/ |
D | Kconfig | 412 Add a "nocache" read-write memory section that is configured to 933 1) All program text will be have read-only, execute memory permission 934 2) All read-only data will have read-only permission, and execution 936 3) All other RAM addresses will have read-write permission, and 947 access permissions set, typically read/write/execute. It may be desirable
|
/Zephyr-latest/doc/services/storage/zms/ |
D | zms.rst | 144 ZMS ID/data read (with history) 149 its data and returns the number of bytes that were read. 221 .. note:: The CRC of the data is checked only when the whole the element is read. 222 The CRC of the data is not checked for a partial read, as it is computed for the whole element.
|
/Zephyr-latest/doc/kernel/drivers/ |
D | index.rst | 98 split into read-only and runtime-mutable parts. At a high level we have: 109 The ``config`` member is for read-only configuration data set at build time. For 119 implementations in the driver. It is typically read-only and populated at
|
/Zephyr-latest/subsys/fs/ |
D | fat_fs.c | 539 .read = fatfs_read,
|
/Zephyr-latest/drivers/sensor/memsic/mmc56x3/ |
D | mmc56x3.c | 38 return config->bus_io->read(&config->bus, reg, buf, size); in mmc56x3_reg_read()
|
/Zephyr-latest/drivers/ethernet/phy/ |
D | phy_microchip_ksz8081.c | 512 .read = phy_mc_ksz8081_read,
|
/Zephyr-latest/drivers/flash/ |
D | flash_sam.c | 468 .read = sam_flash_read,
|
/Zephyr-latest/scripts/ci/es_upload/ |
D | README.md | 18 or read its source code with inline comments there.
|
/Zephyr-latest/boards/seeed/xiao_esp32c3/doc/ |
D | index.rst | 144 For more information about the system build please read the :ref:`sysbuild` documentation.
|
/Zephyr-latest/drivers/display/ |
D | display_ili9xxx.c | 484 .read = ili9xxx_read,
|
/Zephyr-latest/doc/services/ |
D | secure_storage.rst | 69 read/write by software or debugging. (Against ``2.`` and ``10.`` in
|
/Zephyr-latest/drivers/adc/ |
D | adc_gd32.c | 361 .read = adc_gd32_read,
|
D | adc_sam0.c | 508 .read = adc_sam0_read,
|
/Zephyr-latest/boards/m5stack/stamp_c3/doc/ |
D | index.rst | 126 For more information about the system build please read the :ref:`sysbuild` documentation.
|
/Zephyr-latest/doc/develop/test/twister/ |
D | twister_blackbox.rst | 50 Typical files read in blackbox tests are ``testplan.json`` , ``twister.xml`` and ``twister.log`` .
|
/Zephyr-latest/boards/lilygo/ttgo_t7v1_5/doc/ |
D | index.rst | 139 For more information about the system build please read the :ref:`sysbuild` documentation.
|
1...<<31323334353637383940>>...43