# General configuration options # Copyright (c) 2014-2015 Wind River Systems, Inc. # Copyright (c) 2016 Intel Corporation # SPDX-License-Identifier: Apache-2.0 menu "Modules" source "$(CMAKE_BINARY_DIR)/Kconfig.modules" source "modules/Kconfig" endmenu # Include these first so that any properties (e.g. defaults) below can be # overridden in *.defconfig files (by defining symbols in multiple locations). # After merging all the symbol definitions, Kconfig picks the first property # (e.g. the first default) with a satisfied condition. # # Board defaults should be parsed before SoC defaults, because boards usually # overrides SoC values. # # Note: $ARCH and $BOARD_DIR might be glob patterns. source "$(BOARD_DIR)/Kconfig.defconfig" source "$(SOC_DIR)/$(ARCH)/*/Kconfig.defconfig" source "boards/Kconfig" source "$(SOC_DIR)/Kconfig" source "arch/Kconfig" source "kernel/Kconfig" source "dts/Kconfig" source "drivers/Kconfig" source "lib/Kconfig" source "subsys/Kconfig" source "ext/Kconfig" menu "Build and Link Features" menu "Linker Options" choice prompt "Linker Orphan Section Handling" default LINKER_ORPHAN_SECTION_WARN config LINKER_ORPHAN_SECTION_PLACE bool "Place" help Linker puts orphan sections in place without warnings or errors. config LINKER_ORPHAN_SECTION_WARN bool "Warn" help Linker places the orphan sections in output and issues warning about those sections. config LINKER_ORPHAN_SECTION_ERROR bool "Error" help Linker exits with error when an orphan section is found. endchoice config CODE_DATA_RELOCATION bool "Relocate code/data sections" depends on ARM help When selected this will relocate .text, data and .bss sections from the specified files and places it in the required memory region. The files should be specified in the CMakeList.txt file with a cmake API zephyr_code_relocate(). config HAS_FLASH_LOAD_OFFSET bool help This option is selected by targets having a FLASH_LOAD_OFFSET and FLASH_LOAD_SIZE. if HAS_FLASH_LOAD_OFFSET config USE_DT_CODE_PARTITION bool "Link application into /chosen/zephyr,code-partition from devicetree" help When enabled, the application will be linked into the flash partition selected by the zephyr,code-partition property in /chosen in devicetree. When this is disabled, the flash load offset and size can be set manually below. # Workaround for not being able to have commas in macro arguments DT_CHOSEN_Z_CODE_PARTITION := zephyr,code-partition config FLASH_LOAD_OFFSET # Only user-configurable when USE_DT_CODE_PARTITION is disabled hex "Kernel load offset" if !USE_DT_CODE_PARTITION default $(dt_chosen_reg_addr_hex,$(DT_CHOSEN_Z_CODE_PARTITION)) if USE_DT_CODE_PARTITION default 0 help This option specifies the byte offset from the beginning of flash that the kernel should be loaded into. Changing this value from zero will affect the Zephyr image's link, and will decrease the total amount of flash available for use by application code. If unsure, leave at the default value 0. config FLASH_LOAD_SIZE # Only user-configurable when USE_DT_CODE_PARTITION is disabled hex "Kernel load size" if !USE_DT_CODE_PARTITION default $(dt_chosen_reg_size_hex,$(DT_CHOSEN_Z_CODE_PARTITION)) if USE_DT_CODE_PARTITION default 0 help If non-zero, this option specifies the size, in bytes, of the flash area that the Zephyr image will be allowed to occupy. If zero, the image will be able to occupy from the FLASH_LOAD_OFFSET to the end of the device. If unsure, leave at the default value 0. endif # HAS_FLASH_LOAD_OFFSET config TEXT_SECTION_OFFSET hex prompt "TEXT section offset" if !BOOTLOADER_MCUBOOT default 0x200 if BOOTLOADER_MCUBOOT default 0 help If the application is built for chain-loading by a bootloader this variable is required to be set to value that leaves sufficient space between the beginning of the image and the start of the .text section to store an image header or any other metadata. In the particular case of the MCUboot bootloader this reserves enough space to store the image header, which should also meet vector table alignment requirements on most ARM targets, although some targets may require smaller or larger values. config HAVE_CUSTOM_LINKER_SCRIPT bool "Custom linker scripts provided" help Set this option if you have a custom linker script which needed to be define in CUSTOM_LINKER_SCRIPT. config CUSTOM_LINKER_SCRIPT string "Path to custom linker script" depends on HAVE_CUSTOM_LINKER_SCRIPT help Path to the linker script to be used instead of the one define by the board. The linker script must be based on a version provided by Zephyr since the kernel can expect a certain layout/certain regions. This is useful when an application needs to add sections into the linker script and avoid having to change the script provided by Zephyr. config CUSTOM_RODATA_LD bool "(DEPRECATED) Include custom-rodata.ld" help Note: This is deprecated, use Cmake function zephyr_linker_sources() instead. Include a customized linker script fragment for inserting additional data and linker directives into the rodata section. config CUSTOM_RWDATA_LD bool "(DEPRECATED) Include custom-rwdata.ld" help Note: This is deprecated, use Cmake function zephyr_linker_sources() instead. Include a customized linker script fragment for inserting additional data and linker directives into the data section. config CUSTOM_SECTIONS_LD bool "(DEPRECATED) Include custom-sections.ld" help Note: This is deprecated, use Cmake function zephyr_linker_sources() instead. Include a customized linker script fragment for inserting additional arbitrary sections. config KERNEL_ENTRY string "Kernel entry symbol" default "__start" help Code entry symbol, to be set at linking phase. config LINKER_SORT_BY_ALIGNMENT bool "Sort input sections by alignment" default y help This turns on the linker flag to sort sections by alignment in decreasing size of symbols. This helps to minimize padding between symbols. endmenu menu "Compiler Options" config NATIVE_APPLICATION bool "Build as a native host application" help Build as a native application that can run on the host and using resources and libraries provided by the host. choice prompt "Optimization level" default NO_OPTIMIZATIONS if COVERAGE default DEBUG_OPTIMIZATIONS if DEBUG default SIZE_OPTIMIZATIONS help Note that these flags shall only control the compiler optimization level, and that no extra debug code shall be conditionally compiled based on them. config SIZE_OPTIMIZATIONS bool "Optimize for size" help Compiler optimizations will be set to -Os independently of other options. config SPEED_OPTIMIZATIONS bool "Optimize for speed" help Compiler optimizations will be set to -O2 independently of other options. config DEBUG_OPTIMIZATIONS bool "Optimize debugging experience" help Compiler optimizations will be set to -Og independently of other options. config NO_OPTIMIZATIONS bool "Optimize nothing" help Compiler optimizations will be set to -O0 independently of other options. endchoice config COMPILER_OPT string "Custom compiler options" help This option is a free-form string that is passed to the compiler when building all parts of a project (i.e. kernel). The compiler options specified by this string supplement the predefined set of compiler supplied by the build system, and can be used to change compiler optimization, warning and error messages, and so on. endmenu menu "Build Options" config KERNEL_BIN_NAME string "The kernel binary name" default "zephyr" help This option sets the name of the generated kernel binary. config OUTPUT_STAT bool "Create a statistics file" default y help Create a stat file using readelf -e config OUTPUT_DISASSEMBLY bool "Create a disassembly file" default y help Create an .lst file with the assembly listing of the firmware. config OUTPUT_PRINT_MEMORY_USAGE bool "Print memory usage to stdout" default y help If the toolchain supports it, this option will pass --print-memory-region to the linker when it is doing it's first linker pass. Note that the memory regions are symbolic concepts defined by the linker scripts and do not necessarily map directly to the real physical address space. Take also note that some platforms do two passes of the linker so the results do not match exactly to the final elf file. See also rom_report, ram_report and https://sourceware.org/binutils/docs/ld/MEMORY.html config BUILD_OUTPUT_HEX bool "Build a binary in HEX format" help Build a binary in HEX format. This will build a zephyr.hex file need by some platforms. config BUILD_OUTPUT_BIN bool "Build a binary in BIN format" default y help Build a binary in BIN format. This will build a zephyr.bin file need by some platforms. config BUILD_OUTPUT_EXE bool "Build a binary in ELF format with .exe extension" help Build a binary in ELF format that can run in the host system. This will build a zephyr.exe file. config BUILD_OUTPUT_S19 bool "Build a binary in S19 format" help Build a binary in S19 format. This will build a zephyr.s19 file need by some platforms. config BUILD_NO_GAP_FILL bool "Don't fill gaps in generated hex/bin/s19 files." depends on BUILD_OUTPUT_HEX || BUILD_OUTPUT_BIN || BUILD_OUTPUT_S19 config BUILD_OUTPUT_STRIPPED bool "Build a stripped binary" help Build a stripped binary. This will build a zephyr.stripped file need by some platforms. config APPLICATION_DEFINED_SYSCALL bool "Scan application folder for any syscall definition" help Scan additional folders inside application source folder for application defined syscalls. endmenu endmenu menu "Boot Options" config IS_BOOTLOADER bool "Act as a bootloader" depends on XIP depends on ARM help This option indicates that Zephyr will act as a bootloader to execute a separate Zephyr image payload. config BOOTLOADER_SRAM_SIZE int "SRAM reserved for bootloader" default 16 depends on !XIP || IS_BOOTLOADER depends on ARM || XTENSA help This option specifies the amount of SRAM (measure in kB) reserved for a bootloader image, when either: - the Zephyr image itself is to act as the bootloader, or - Zephyr is a !XIP image, which implicitly assumes existence of a bootloader that loads the Zephyr !XIP image onto SRAM. config BOOTLOADER_MCUBOOT bool "MCUboot bootloader support" select USE_DT_CODE_PARTITION help This option signifies that the target uses MCUboot as a bootloader, or in other words that the image is to be chain-loaded by MCUboot. This sets several required build system and Device Tree options in order for the image generated to be bootable using the MCUboot open source bootloader. Currently this includes: * Setting TEXT_SECTION_OFFSET to a default value that allows space for the MCUboot image header * Activating SW_VECTOR_RELAY on Cortex-M0 (or Armv8-M baseline) targets with no built-in vector relocation mechanisms * Including dts/common/mcuboot.overlay when building the Device Tree in order to place and link the image at the slot0 offset config BOOTLOADER_ESP_IDF bool "ESP-IDF bootloader support" depends on SOC_ESP32 help This option will trigger the compilation of the ESP-IDF bootloader inside the build folder. At flash time, the bootloader will be flashed with the zephyr image config BOOTLOADER_KEXEC bool "Boot using Linux kexec() system call" depends on X86 help This option signifies that Linux boots the kernel using kexec system call and utility. This method is used to boot the kernel over the network. config BOOTLOADER_CONTEXT_RESTORE bool "Boot loader has context restore support" default y depends on SYS_POWER_DEEP_SLEEP_STATES && BOOTLOADER_CONTEXT_RESTORE_SUPPORTED help This option signifies that the target has a bootloader that restores CPU context upon resuming from deep sleep power state. config REBOOT bool "Reboot functionality" select SYSTEM_CLOCK_DISABLE help Enable the sys_reboot() API. Enabling this can drag in other subsystems needed to perform a "safe" reboot (e.g. SYSTEM_CLOCK_DISABLE, to stop the system clock before issuing a reset). config MISRA_SANE bool "MISRA standards compliance features" help Causes the source code to build in "MISRA" mode, which disallows some otherwise-permitted features of the C standard for safety reasons. Specifically variable length arrays are not permitted (and gcc will enforce this). endmenu