Searched refs:linked (Results 101 – 122 of 122) sorted by relevance
12345
194 archives are then linked with *ld* as specified in the
62 Zephyr binaries are compiled and linked by a *toolchain* comprised of
398 - Flash partition that the Zephyr image's text section should be linked
222 make sure it gets linked to from gen_devicetree_rest.py too.
146 a double-linked list, with an attendant delta count in ticks from the
18 and linked to any relevant :ref:`bug or feature tracking issues<bug_reporting>`
34 * Added DLIST to operate in all elements of a doubly-linked list.
180 * The kernel is linked at its physical memory location in RAM.928 * :github:`28443` - drivers: sensor: hts221 compilation issue linked to DT property drdy_gpios
1182 * :github:`23324` - TinyCBOR is not linked to application files unless CONFIG_MCUMGR is selected
677 on the linked flash device partition.685 * Intel GPDMA linked list transfer descriptors appropriately aligned to 64 byte addresses
845 this works better when flashing Zephyr images linked for locations other
1187 * :github:`15083` - MCUBoot is linked to slot0 because overlay is dropped in boilerplate.cmake
288 ``scripts/build/gen_app_partitions.py``. If a static library is linked into Zephyr,
444 Many system calls pass in structures or even linked data structures. All should
947 * one is linked here.
525 software ISR table that are then compiled and linked into the final
573 will be linked into its code partition, specified in DeviceTree.
535 created from the backend on one side and linked to the other.
94 When enabled, the application will be linked into the flash partition
526 This option configures the advertising sets linked with the same
1210 can be linked to using the :rst:role:`zephyr:board` role.
4648 # FORMAT <format>: The output format of the linked executable.5802 # - PRE_BUILD: Before the llext code is linked, if the architecture uses5838 # > before the object files are linked:
