Searched refs:populate (Results 1 – 25 of 28) sorted by relevance
12
/Zephyr-latest/dts/common/ |
D | skeleton.dtsi | 5 * add a compatible value. The bootloader will typically populate the memory
|
/Zephyr-latest/samples/posix/env/ |
D | README.rst | 9 In this sample application, the POSIX :c:func:`setenv`, function is used to populate several enviro…
|
/Zephyr-latest/tests/drivers/i2c/i2c_target_api/ |
D | README.txt | 23 * Use API specific to the simulated EEPROM to pre-populate the simulated
|
/Zephyr-latest/tests/bluetooth/audio/mocks/src/ |
D | gatt.c | 384 goto populate; in gatt_register() 391 populate: in gatt_register()
|
/Zephyr-latest/boards/nxp/mimxrt1160_evk/ |
D | mimxrt1160_evk.dtsi | 80 * Note that if you populate them, they conflict with camera and
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | shell.rst | 321 …unprovisioned device. Providing a hex-string shorter than 16 bytes will populate the N most signif… 337 …unprovisioned device. Providing a hex-string shorter than 16 bytes will populate the N most signif… 347 …w 128-bit UUID value. Providing a hex-string shorter than 16 bytes will populate the N most signif… 378 …ue of the static OOB. Providing a hex-string shorter than 16 bytes will populate the N most signif… 440 …* ``Val`` - Static OOB value. Providing a hex-string shorter than 32 bytes will populate the N mos… 642 …it hexadecimal value. Providing a hex-string shorter than 16 bytes will populate the N most signif… 651 …it hexadecimal value. Providing a hex-string shorter than 16 bytes will populate the N most signif… 675 …it hexadecimal value. Providing a hex-string shorter than 16 bytes will populate the N most signif… 684 …it hexadecimal value. Providing a hex-string shorter than 16 bytes will populate the N most signif… 774 …ddress to publish to. Providing a hex-string shorter than 16 bytes will populate the N most signif… [all …]
|
D | access.rst | 98 populate the :c:member:`bt_mesh_model_pub.update` callback. The
|
D | dfu.rst | 279 populate the Distributor's receivers list with the address and relevant firmware image index of each
|
/Zephyr-latest/boards/adi/max78000fthr/doc/ |
D | index.rst | 172 | | | R15 or R20 resistors. Do not populate both. … 175 | | | R15 or R20 resistors. Do not populate both. …
|
/Zephyr-latest/boards/nxp/mimxrt1170_evk/ |
D | mimxrt1170_evk.dtsi | 65 * Note that if you populate them, they conflict with camera and
|
/Zephyr-latest/boards/nxp/mimxrt1050_evk/ |
D | mimxrt1050_evk.dtsi | 146 * Note that if you populate them, they conflict with LCD and
|
/Zephyr-latest/boards/nxp/mimxrt1040_evk/ |
D | mimxrt1040_evk.dts | 216 * Note that if you populate them, they conflict with JTAG_TDO and
|
/Zephyr-latest/doc/hardware/arch/ |
D | x86.rst | 85 the script, populate a CMake list named ``X86_EXTRA_GEN_MMU_ARGUMENTS``
|
/Zephyr-latest/doc/kernel/drivers/ |
D | index.rst | 96 The device initialization macros populate some data structures at build time 156 of these APIs, and populate an instance of subsystem_driver_api structure using
|
/Zephyr-latest/doc/develop/west/ |
D | zephyr-cmds.rst | 84 #. Pre-populate a build directory :file:`BUILD_DIR` like this:
|
/Zephyr-latest/doc/_extensions/zephyr/kconfig/static/ |
D | kconfig.mjs | 406 /* populate kconfig-search container */
|
/Zephyr-latest/doc/kernel/ |
D | timeutil.rst | 235 The mechanism used to populate synchronization points is not relevant: it may
|
/Zephyr-latest/subsys/net/lib/dns/ |
D | Kconfig | 98 to populate the server list. If the DNS server addresses are
|
/Zephyr-latest/doc/releases/ |
D | release-notes-1.5.rst | 139 * ``ZEP-254`` - nios2: define NANO_ESF struct and populate _default_esf
|
/Zephyr-latest/doc/hardware/peripherals/ |
D | i3c.rst | 93 * BCR and DCR need to be obtained separately to populate
|
/Zephyr-latest/subsys/net/ip/ |
D | Kconfig | 561 # that used to populate the routing table. 568 would need to populate the routing table. RPL used to do that
|
/Zephyr-latest/subsys/bluetooth/host/ |
D | gatt.c | 1262 goto populate; in gatt_register() 1269 populate: in gatt_register()
|
/Zephyr-latest/doc/contribute/documentation/ |
D | guidelines.rst | 1233 The metadata for the board is read from various config files and used to automatically populate
|
/Zephyr-latest/doc/develop/ |
D | modules.rst | 1128 #. In a separate CMake script which is pre-loaded to populate the CMake cache,
|
/Zephyr-latest/ |
D | CMakeLists.txt | 2138 # To populate with hex files to merge, do the following:
|
12