Home
last modified time | relevance | path

Searched refs:overlap (Results 1 – 24 of 24) sorted by relevance

/Zephyr-Core-3.5.0/scripts/build/
Dmergehex.py16 def merge_hex_files(output, input_hex_files, overlap): argument
28 ih.merge(to_merge, overlap=overlap)
52 merge_hex_files(args.output, args.input_files, args.overlap)
/Zephyr-Core-3.5.0/cmake/compiler/host-gcc/
Dcompiler_flags.cmake2 # Significant overlap with freestanding gcc compiler so reuse it
/Zephyr-Core-3.5.0/samples/drivers/memc/
DREADME.rst14 overlap with memory used for XIP or SRAM by the application, as the sample
/Zephyr-Core-3.5.0/include/zephyr/linker/
Dintlist.ld25 * shouldn't overlap any other regions. On most arches the following should be
/Zephyr-Core-3.5.0/tests/bsim/bluetooth/ll/cis/
DKconfig55 scanning to overlap with advertising events hence do not use
/Zephyr-Core-3.5.0/include/zephyr/arch/x86/
Dmemory.ld55 * Board-level DTS must specify a flash region that doesn't overlap with
104 * target. However, it shouldn't overlap any other regions.
/Zephyr-Core-3.5.0/drivers/display/
DKconfig.mcux_dcnano_lcdif47 does not overlap with other data. Each allocated LCDIF buffer will
/Zephyr-Core-3.5.0/arch/x86/zefi/
DREADME.txt81 doesn't overlap with the target Zephyr memory. In practice on the
87 the overlap and warn about it.
/Zephyr-Core-3.5.0/include/zephyr/arch/arm64/scripts/
Dlinker.ld146 * section overlap.
227 * than __rodata_region_end, and this two regions can overlap.
/Zephyr-Core-3.5.0/soc/arm64/nxp_imx/mimx9/
Dlinker.ld146 * section overlap.
227 * than __rodata_region_end, and this two regions can overlap.
/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/
Doverview.rst48 * Intelligent scheduling of roles to minimize overlap
/Zephyr-Core-3.5.0/include/zephyr/arch/arm/cortex_a_r/scripts/
Dlinker.ld172 * section overlap.
/Zephyr-Core-3.5.0/arch/xtensa/core/
DREADME-WINDOWS.rst107 caller-save. When using CALLn, you always need to overlap 4 registers
/Zephyr-Core-3.5.0/kernel/
DKconfig.vm91 there isn't overlap with the existed mappings, it will reserve the
/Zephyr-Core-3.5.0/include/zephyr/arch/arm/cortex_m/scripts/
Dlinker.ld167 * section overlap.
/Zephyr-Core-3.5.0/doc/kernel/usermode/
Dmemory_domain.rst180 - Partitions within the same memory domain may not overlap each other. There is
184 overlap a boot-time memory region is architecture specific.
/Zephyr-Core-3.5.0/boards/x86/acrn/doc/
Dindex.rst180 configuring multiple guests, you probably don't want to overlap these
/Zephyr-Core-3.5.0/boards/x86/qemu_x86/
Dqemu_x86_tiny.ld72 * target. However, it shouldn't overlap any other regions.
/Zephyr-Core-3.5.0/boards/arm/mps2_an521/doc/
Dindex.rst98 some overlap in the memory maps.
/Zephyr-Core-3.5.0/subsys/bluetooth/controller/
DKconfig.ll_sw_split458 bool "Skip Periodic Sync event on overlap with Extended Scan Event"
659 and/or PHY Update procedure to avoid overlap of radio events
/Zephyr-Core-3.5.0/doc/hardware/arch/
Darm_cortex_m.rst513 overlap. :kconfig:option:`CONFIG_MPU_GAP_FILLING` controls whether the fixed MPU region
/Zephyr-Core-3.5.0/doc/releases/
Drelease-notes-3.3.rst2653 - :github:`51024` - aarch32 excn vector not pinned in mmu causing newlib heap overlap
2802 - :github:`54577` - IPv6 defragmenting fails when segments do not overlap
2926 * :github:`54393` - Bluetooth: Controller: Starting a second BIG causes them to overlap and have tw…
2938 * :github:`54344` - Bluetooth: Controller: Central ACL connections overlap Broadcast ISO BIG event
3101 * :github:`53221` - Systemview trace id overlap
Drelease-notes-2.4.rst1383 * :github:`26413` - disco_l475_iot1: flash storage corruption caused by partition overlap
1607 * :github:`24859` - os: Add memory partition overlap assert check is not made for x86 boards
Drelease-notes-3.2.rst2049 * :github:`49036` - soc: telink_b91: ROM region section overlap