2015-08-23 02:43:07 +08:00
|
|
|
# Kconfig - general configuration options
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Copyright (c) 2014-2015 Wind River Systems, Inc.
|
2016-03-26 05:30:50 +08:00
|
|
|
# Copyright (c) 2016 Intel Corporation
|
2015-08-23 02:43:07 +08:00
|
|
|
#
|
2017-01-19 09:01:01 +08:00
|
|
|
# SPDX-License-Identifier: Apache-2.0
|
2015-08-23 02:43:07 +08:00
|
|
|
#
|
2018-01-09 21:12:07 +08:00
|
|
|
|
2019-05-29 02:22:51 +08:00
|
|
|
menu "Modules"
|
|
|
|
|
|
2019-03-01 19:57:11 +08:00
|
|
|
source "$(CMAKE_BINARY_DIR)/Kconfig.modules"
|
2019-05-24 05:19:41 +08:00
|
|
|
source "modules/Kconfig"
|
2019-03-13 22:30:55 +08:00
|
|
|
|
2019-05-29 02:22:51 +08:00
|
|
|
endmenu
|
|
|
|
|
|
Kconfig: Use the first default with a satisfied condition
Up until now, Zephyr has patched Kconfig to use the last 'default' with
a satisfied condition, instead of the first one. I'm not sure why the
patch was added (it predates Kconfiglib), but I suspect it's related to
Kconfig.defconfig files.
There are at least three problems with the patch:
1. It's inconsistent with how Kconfig works in other projects, which
might confuse newcomers.
2. Due to oversights, earlier 'range' properties are still preferred,
as well as earlier 'default' properties on choices.
In addition to being inconsistent, this makes it impossible to
override 'range' properties and choice 'default' properties if the
base definition of the symbol/choice already has 'range'/'default'
properties.
I've seen errors caused by the inconsistency, and I suspect there
are more.
3. A fork of Kconfiglib that adds the patch needs to be maintained.
Get rid of the patch and go back to standard Kconfig behavior, as
follows:
1. Include the Kconfig.defconfig files first instead of last in
Kconfig.zephyr.
2. Include boards/Kconfig and arch/<arch>/Kconfig first instead of
last in arch/Kconfig.
3. Include arch/<arch>/soc/*/Kconfig first instead of last in
arch/<arch>/Kconfig.
4. Swap a few other 'source's to preserve behavior for some scattered
symbols with multiple definitions.
Swap 'source's in some no-op cases too, where it might match the
intent.
5. Reverse the defaults on symbol definitions that have more than one
default.
Skip defaults that are mutually exclusive, e.g. where each default
has an 'if <some board>' condition. They are already safe.
6. Remove the prefer-later-defaults patch from Kconfiglib.
Testing was done with a Python script that lists all Kconfig
symbols/choices with multiple defaults, along with a whitelist of fixed
symbols. The script also verifies that there are no "unreachable"
defaults hidden by defaults without conditions
As an additional test, zephyr/.config was generated before and after the
change for several samples and checked to be identical (after sorting).
This commit includes some default-related cleanups as well:
- Simplify some symbol definitions, e.g. where a default has 'if FOO'
when the symbol already has 'depends on FOO'.
- Remove some redundant 'default ""' for string symbols. This is the
implicit default.
Piggyback fixes for swapped ranges on BT_L2CAP_RX_MTU and
BT_L2CAP_TX_MTU (caused by confusing inconsistency).
Piggyback some fixes for style nits too, e.g. unindented help texts.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-30 16:57:47 +08:00
|
|
|
# Include these first so that any properties (e.g. defaults) below can be
|
2019-06-19 02:45:40 +08:00
|
|
|
# overridden in *.defconfig files (by defining symbols in multiple locations).
|
Kconfig: Use the first default with a satisfied condition
Up until now, Zephyr has patched Kconfig to use the last 'default' with
a satisfied condition, instead of the first one. I'm not sure why the
patch was added (it predates Kconfiglib), but I suspect it's related to
Kconfig.defconfig files.
There are at least three problems with the patch:
1. It's inconsistent with how Kconfig works in other projects, which
might confuse newcomers.
2. Due to oversights, earlier 'range' properties are still preferred,
as well as earlier 'default' properties on choices.
In addition to being inconsistent, this makes it impossible to
override 'range' properties and choice 'default' properties if the
base definition of the symbol/choice already has 'range'/'default'
properties.
I've seen errors caused by the inconsistency, and I suspect there
are more.
3. A fork of Kconfiglib that adds the patch needs to be maintained.
Get rid of the patch and go back to standard Kconfig behavior, as
follows:
1. Include the Kconfig.defconfig files first instead of last in
Kconfig.zephyr.
2. Include boards/Kconfig and arch/<arch>/Kconfig first instead of
last in arch/Kconfig.
3. Include arch/<arch>/soc/*/Kconfig first instead of last in
arch/<arch>/Kconfig.
4. Swap a few other 'source's to preserve behavior for some scattered
symbols with multiple definitions.
Swap 'source's in some no-op cases too, where it might match the
intent.
5. Reverse the defaults on symbol definitions that have more than one
default.
Skip defaults that are mutually exclusive, e.g. where each default
has an 'if <some board>' condition. They are already safe.
6. Remove the prefer-later-defaults patch from Kconfiglib.
Testing was done with a Python script that lists all Kconfig
symbols/choices with multiple defaults, along with a whitelist of fixed
symbols. The script also verifies that there are no "unreachable"
defaults hidden by defaults without conditions
As an additional test, zephyr/.config was generated before and after the
change for several samples and checked to be identical (after sorting).
This commit includes some default-related cleanups as well:
- Simplify some symbol definitions, e.g. where a default has 'if FOO'
when the symbol already has 'depends on FOO'.
- Remove some redundant 'default ""' for string symbols. This is the
implicit default.
Piggyback fixes for swapped ranges on BT_L2CAP_RX_MTU and
BT_L2CAP_TX_MTU (caused by confusing inconsistency).
Piggyback some fixes for style nits too, e.g. unindented help texts.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-30 16:57:47 +08:00
|
|
|
# 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.
|
|
|
|
|
#
|
2018-09-05 18:58:05 +08:00
|
|
|
# Note: $ARCH and $BOARD_DIR might be glob patterns.
|
2018-09-05 19:10:19 +08:00
|
|
|
source "$(BOARD_DIR)/Kconfig.defconfig"
|
Kconfig: Use the first default with a satisfied condition
Up until now, Zephyr has patched Kconfig to use the last 'default' with
a satisfied condition, instead of the first one. I'm not sure why the
patch was added (it predates Kconfiglib), but I suspect it's related to
Kconfig.defconfig files.
There are at least three problems with the patch:
1. It's inconsistent with how Kconfig works in other projects, which
might confuse newcomers.
2. Due to oversights, earlier 'range' properties are still preferred,
as well as earlier 'default' properties on choices.
In addition to being inconsistent, this makes it impossible to
override 'range' properties and choice 'default' properties if the
base definition of the symbol/choice already has 'range'/'default'
properties.
I've seen errors caused by the inconsistency, and I suspect there
are more.
3. A fork of Kconfiglib that adds the patch needs to be maintained.
Get rid of the patch and go back to standard Kconfig behavior, as
follows:
1. Include the Kconfig.defconfig files first instead of last in
Kconfig.zephyr.
2. Include boards/Kconfig and arch/<arch>/Kconfig first instead of
last in arch/Kconfig.
3. Include arch/<arch>/soc/*/Kconfig first instead of last in
arch/<arch>/Kconfig.
4. Swap a few other 'source's to preserve behavior for some scattered
symbols with multiple definitions.
Swap 'source's in some no-op cases too, where it might match the
intent.
5. Reverse the defaults on symbol definitions that have more than one
default.
Skip defaults that are mutually exclusive, e.g. where each default
has an 'if <some board>' condition. They are already safe.
6. Remove the prefer-later-defaults patch from Kconfiglib.
Testing was done with a Python script that lists all Kconfig
symbols/choices with multiple defaults, along with a whitelist of fixed
symbols. The script also verifies that there are no "unreachable"
defaults hidden by defaults without conditions
As an additional test, zephyr/.config was generated before and after the
change for several samples and checked to be identical (after sorting).
This commit includes some default-related cleanups as well:
- Simplify some symbol definitions, e.g. where a default has 'if FOO'
when the symbol already has 'depends on FOO'.
- Remove some redundant 'default ""' for string symbols. This is the
implicit default.
Piggyback fixes for swapped ranges on BT_L2CAP_RX_MTU and
BT_L2CAP_TX_MTU (caused by confusing inconsistency).
Piggyback some fixes for style nits too, e.g. unindented help texts.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-30 16:57:47 +08:00
|
|
|
|
2018-09-05 03:34:06 +08:00
|
|
|
source "$(SOC_DIR)/$(ARCH)/*/Kconfig.defconfig"
|
Kconfig: Use the first default with a satisfied condition
Up until now, Zephyr has patched Kconfig to use the last 'default' with
a satisfied condition, instead of the first one. I'm not sure why the
patch was added (it predates Kconfiglib), but I suspect it's related to
Kconfig.defconfig files.
There are at least three problems with the patch:
1. It's inconsistent with how Kconfig works in other projects, which
might confuse newcomers.
2. Due to oversights, earlier 'range' properties are still preferred,
as well as earlier 'default' properties on choices.
In addition to being inconsistent, this makes it impossible to
override 'range' properties and choice 'default' properties if the
base definition of the symbol/choice already has 'range'/'default'
properties.
I've seen errors caused by the inconsistency, and I suspect there
are more.
3. A fork of Kconfiglib that adds the patch needs to be maintained.
Get rid of the patch and go back to standard Kconfig behavior, as
follows:
1. Include the Kconfig.defconfig files first instead of last in
Kconfig.zephyr.
2. Include boards/Kconfig and arch/<arch>/Kconfig first instead of
last in arch/Kconfig.
3. Include arch/<arch>/soc/*/Kconfig first instead of last in
arch/<arch>/Kconfig.
4. Swap a few other 'source's to preserve behavior for some scattered
symbols with multiple definitions.
Swap 'source's in some no-op cases too, where it might match the
intent.
5. Reverse the defaults on symbol definitions that have more than one
default.
Skip defaults that are mutually exclusive, e.g. where each default
has an 'if <some board>' condition. They are already safe.
6. Remove the prefer-later-defaults patch from Kconfiglib.
Testing was done with a Python script that lists all Kconfig
symbols/choices with multiple defaults, along with a whitelist of fixed
symbols. The script also verifies that there are no "unreachable"
defaults hidden by defaults without conditions
As an additional test, zephyr/.config was generated before and after the
change for several samples and checked to be identical (after sorting).
This commit includes some default-related cleanups as well:
- Simplify some symbol definitions, e.g. where a default has 'if FOO'
when the symbol already has 'depends on FOO'.
- Remove some redundant 'default ""' for string symbols. This is the
implicit default.
Piggyback fixes for swapped ranges on BT_L2CAP_RX_MTU and
BT_L2CAP_TX_MTU (caused by confusing inconsistency).
Piggyback some fixes for style nits too, e.g. unindented help texts.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-30 16:57:47 +08:00
|
|
|
|
2018-09-04 21:32:07 +08:00
|
|
|
source "boards/Kconfig"
|
|
|
|
|
|
2018-09-05 03:34:06 +08:00
|
|
|
source "$(SOC_DIR)/Kconfig"
|
2018-09-04 21:32:07 +08:00
|
|
|
|
2015-10-09 18:20:52 +08:00
|
|
|
source "arch/Kconfig"
|
2015-08-23 02:43:07 +08:00
|
|
|
|
2015-10-09 18:20:52 +08:00
|
|
|
source "kernel/Kconfig"
|
2015-08-23 02:43:07 +08:00
|
|
|
|
2017-08-03 19:47:44 +08:00
|
|
|
source "dts/Kconfig"
|
|
|
|
|
|
2015-10-09 18:20:52 +08:00
|
|
|
source "drivers/Kconfig"
|
2015-08-23 02:43:07 +08:00
|
|
|
|
2016-05-15 11:10:51 +08:00
|
|
|
source "lib/Kconfig"
|
|
|
|
|
|
2016-10-29 19:10:36 +08:00
|
|
|
source "subsys/Kconfig"
|
2016-07-26 07:20:54 +08:00
|
|
|
|
2016-05-25 03:23:26 +08:00
|
|
|
source "ext/Kconfig"
|
|
|
|
|
|
2019-05-24 05:19:41 +08:00
|
|
|
|
2018-11-02 19:12:07 +08:00
|
|
|
menu "Build and Link Features"
|
|
|
|
|
|
|
|
|
|
menu "Linker Options"
|
|
|
|
|
|
2018-10-20 01:15:19 +08:00
|
|
|
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
|
2019-06-19 02:45:40 +08:00
|
|
|
Linker places the orphan sections in output and issues
|
2018-10-20 01:15:19 +08:00
|
|
|
warning about those sections.
|
|
|
|
|
|
|
|
|
|
config LINKER_ORPHAN_SECTION_ERROR
|
|
|
|
|
bool "Error"
|
|
|
|
|
help
|
|
|
|
|
Linker exits with error when an orphan section is found.
|
|
|
|
|
|
|
|
|
|
endchoice
|
2018-11-02 19:12:07 +08:00
|
|
|
|
2018-11-13 19:27:45 +08:00
|
|
|
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
|
2019-08-15 17:03:26 +08:00
|
|
|
a cmake API zephyr_code_relocate().
|
2018-11-13 19:27:45 +08:00
|
|
|
|
2018-11-02 19:12:07 +08:00
|
|
|
config HAS_FLASH_LOAD_OFFSET
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
This option is selected by targets having a FLASH_LOAD_OFFSET
|
|
|
|
|
and FLASH_LOAD_SIZE.
|
|
|
|
|
|
2019-03-18 21:02:11 +08:00
|
|
|
config USE_CODE_PARTITION
|
|
|
|
|
bool "link into code-partition"
|
|
|
|
|
depends on HAS_FLASH_LOAD_OFFSET
|
|
|
|
|
help
|
|
|
|
|
When selected application will be linked into chosen code-partition.
|
|
|
|
|
|
2019-08-28 22:29:26 +08:00
|
|
|
# Workaround for not being able to have commas in macro arguments
|
|
|
|
|
DT_CHOSEN_Z_CODE_PARTITION := zephyr,code-partition
|
|
|
|
|
|
2018-11-02 19:12:07 +08:00
|
|
|
config FLASH_LOAD_OFFSET
|
|
|
|
|
hex "Kernel load offset"
|
2019-10-24 04:15:59 +08:00
|
|
|
default $(dt_chosen_reg_addr_hex,$(DT_CHOSEN_Z_CODE_PARTITION)) if USE_CODE_PARTITION
|
2018-11-02 19:12:07 +08:00
|
|
|
default 0
|
|
|
|
|
depends on HAS_FLASH_LOAD_OFFSET
|
|
|
|
|
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
|
2019-10-18 23:12:07 +08:00
|
|
|
hex "Kernel load size"
|
2019-10-24 04:15:59 +08:00
|
|
|
default $(dt_chosen_reg_size_hex,$(DT_CHOSEN_Z_CODE_PARTITION)) if USE_CODE_PARTITION
|
2018-11-02 19:12:07 +08:00
|
|
|
default 0
|
|
|
|
|
depends on HAS_FLASH_LOAD_OFFSET
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
config TEXT_SECTION_OFFSET
|
2019-01-23 21:13:03 +08:00
|
|
|
hex
|
|
|
|
|
prompt "TEXT section offset" if !BOOTLOADER_MCUBOOT
|
2018-11-02 19:12:07 +08:00
|
|
|
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
|
2019-03-20 19:53:49 +08:00
|
|
|
bool "(DEPRECATED) Include custom-rodata.ld"
|
2018-11-02 19:12:07 +08:00
|
|
|
help
|
2019-03-20 19:53:49 +08:00
|
|
|
Note: This is deprecated, use Cmake function zephyr_linker_sources() instead.
|
2018-11-02 19:12:07 +08:00
|
|
|
Include a customized linker script fragment for inserting additional
|
|
|
|
|
data and linker directives into the rodata section.
|
|
|
|
|
|
|
|
|
|
config CUSTOM_RWDATA_LD
|
2019-03-20 19:53:49 +08:00
|
|
|
bool "(DEPRECATED) Include custom-rwdata.ld"
|
2018-11-02 19:12:07 +08:00
|
|
|
help
|
2019-03-20 19:53:49 +08:00
|
|
|
Note: This is deprecated, use Cmake function zephyr_linker_sources() instead.
|
2018-11-02 19:12:07 +08:00
|
|
|
Include a customized linker script fragment for inserting additional
|
|
|
|
|
data and linker directives into the data section.
|
|
|
|
|
|
|
|
|
|
config CUSTOM_SECTIONS_LD
|
2019-03-20 19:53:49 +08:00
|
|
|
bool "(DEPRECATED) Include custom-sections.ld"
|
2018-11-02 19:12:07 +08:00
|
|
|
help
|
2019-03-20 19:53:49 +08:00
|
|
|
Note: This is deprecated, use Cmake function zephyr_linker_sources() instead.
|
2018-11-02 19:12:07 +08:00
|
|
|
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.
|
|
|
|
|
|
2019-03-15 21:05:09 +08:00
|
|
|
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.
|
|
|
|
|
|
2018-11-02 19:12:07 +08:00
|
|
|
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 <elf>
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
2018-11-26 17:47:16 +08:00
|
|
|
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
|
|
|
|
|
|
2018-11-02 19:12:07 +08:00
|
|
|
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
|
2018-12-14 19:25:43 +08:00
|
|
|
depends on ARM || XTENSA
|
2018-11-02 19:12:07 +08:00
|
|
|
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"
|
2019-03-18 21:02:11 +08:00
|
|
|
select USE_CODE_PARTITION
|
2018-11-02 19:12:07 +08:00
|
|
|
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
|
2019-02-12 18:07:20 +08:00
|
|
|
depends on SYS_POWER_DEEP_SLEEP_STATES && BOOTLOADER_CONTEXT_RESTORE_SUPPORTED
|
2018-11-02 19:12:07 +08:00
|
|
|
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).
|
2019-02-28 03:53:18 +08:00
|
|
|
|
|
|
|
|
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).
|
|
|
|
|
|
2018-11-02 19:12:07 +08:00
|
|
|
endmenu
|
2019-06-26 22:22:26 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
menu "Compatibility"
|
|
|
|
|
|
|
|
|
|
config COMPAT_INCLUDES
|
|
|
|
|
bool "Suppress warnings when using header shims"
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Suppress any warnings from the pre-processor when including
|
|
|
|
|
deprecated header files.
|
|
|
|
|
|
|
|
|
|
endmenu
|