2019-11-01 13:45:29 +01:00
|
|
|
# General configuration options
|
2015-08-22 20:43:07 +02:00
|
|
|
|
|
|
|
|
# Copyright (c) 2014-2015 Wind River Systems, Inc.
|
2016-03-25 22:30:50 +01:00
|
|
|
# Copyright (c) 2016 Intel Corporation
|
2017-01-19 02:01:01 +01:00
|
|
|
# SPDX-License-Identifier: Apache-2.0
|
2018-01-09 14:12:07 +01:00
|
|
|
|
2019-05-28 20:22:51 +02:00
|
|
|
menu "Modules"
|
|
|
|
|
|
2020-07-06 21:39:31 +02:00
|
|
|
source "$(KCONFIG_BINARY_DIR)/Kconfig.modules"
|
2019-05-23 23:19:41 +02:00
|
|
|
source "modules/Kconfig"
|
2019-03-13 15:30:55 +01:00
|
|
|
|
2019-05-28 20:22:51 +02:00
|
|
|
endmenu
|
|
|
|
|
|
2020-01-26 23:47:41 +01:00
|
|
|
# Include Kconfig.defconfig files first so that they can override defaults and
|
|
|
|
|
# other symbol/choice properties by adding extra symbol/choice definitions.
|
|
|
|
|
# After merging all definitions for a symbol/choice, Kconfig picks the first
|
|
|
|
|
# property (e.g. the first default) with a satisfied condition.
|
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 10:57:47 +02:00
|
|
|
#
|
2020-01-26 23:47:41 +01:00
|
|
|
# Shield defaults should have precedence over board defaults, which should have
|
|
|
|
|
# precedence over SoC defaults, so include them in that order.
|
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 10:57:47 +02:00
|
|
|
#
|
2020-01-26 23:47:41 +01:00
|
|
|
# $ARCH and $BOARD_DIR will be glob patterns when building documentation.
|
2019-11-22 10:37:01 +01:00
|
|
|
source "boards/shields/*/Kconfig.defconfig"
|
2018-09-05 13:10:19 +02:00
|
|
|
source "$(BOARD_DIR)/Kconfig.defconfig"
|
2020-07-06 12:53:39 +02:00
|
|
|
source "$(KCONFIG_BINARY_DIR)/Kconfig.soc.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 10:57:47 +02:00
|
|
|
|
2018-09-04 15:32:07 +02:00
|
|
|
source "boards/Kconfig"
|
2020-07-06 12:53:39 +02:00
|
|
|
source "soc/Kconfig"
|
2015-10-09 12:20:52 +02:00
|
|
|
source "arch/Kconfig"
|
|
|
|
|
source "kernel/Kconfig"
|
2017-08-03 13:47:44 +02:00
|
|
|
source "dts/Kconfig"
|
2015-10-09 12:20:52 +02:00
|
|
|
source "drivers/Kconfig"
|
2016-05-15 05:10:51 +02:00
|
|
|
source "lib/Kconfig"
|
2016-10-29 13:10:36 +02:00
|
|
|
source "subsys/Kconfig"
|
2016-05-24 21:23:26 +02:00
|
|
|
|
2020-01-24 16:39:40 +01:00
|
|
|
osource "$(TOOLCHAIN_KCONFIG_DIR)/Kconfig"
|
2019-05-23 23:19:41 +02:00
|
|
|
|
2018-11-02 12:12:07 +01:00
|
|
|
menu "Build and Link Features"
|
|
|
|
|
|
|
|
|
|
menu "Linker Options"
|
|
|
|
|
|
2018-10-19 19:15:19 +02: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-18 20:45:40 +02:00
|
|
|
Linker places the orphan sections in output and issues
|
2018-10-19 19:15:19 +02: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 12:12:07 +01:00
|
|
|
|
2018-11-13 12:27:45 +01:00
|
|
|
config CODE_DATA_RELOCATION
|
2019-11-01 10:24:07 +01:00
|
|
|
bool "Relocate code/data sections"
|
|
|
|
|
depends on ARM
|
|
|
|
|
help
|
2018-11-13 12:27:45 +01:00
|
|
|
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 11:03:26 +02:00
|
|
|
a cmake API zephyr_code_relocate().
|
2018-11-13 12:27:45 +01:00
|
|
|
|
2018-11-02 12:12:07 +01:00
|
|
|
config HAS_FLASH_LOAD_OFFSET
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
This option is selected by targets having a FLASH_LOAD_OFFSET
|
|
|
|
|
and FLASH_LOAD_SIZE.
|
|
|
|
|
|
2019-11-16 01:33:09 +01:00
|
|
|
if HAS_FLASH_LOAD_OFFSET
|
|
|
|
|
|
2019-11-16 01:22:16 +01:00
|
|
|
config USE_DT_CODE_PARTITION
|
2019-11-16 01:16:57 +01:00
|
|
|
bool "Link application into /chosen/zephyr,code-partition from devicetree"
|
2019-03-18 14:02:11 +01:00
|
|
|
help
|
2019-11-16 01:16:57 +01:00
|
|
|
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.
|
2019-03-18 14:02:11 +01:00
|
|
|
|
2019-08-28 16:29:26 +02:00
|
|
|
# Workaround for not being able to have commas in macro arguments
|
|
|
|
|
DT_CHOSEN_Z_CODE_PARTITION := zephyr,code-partition
|
|
|
|
|
|
2018-11-02 12:12:07 +01:00
|
|
|
config FLASH_LOAD_OFFSET
|
2019-11-16 01:22:16 +01:00
|
|
|
# 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
|
2018-11-02 12:12:07 +01:00
|
|
|
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
|
2019-11-16 01:22:16 +01:00
|
|
|
# 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
|
2018-11-02 12:12:07 +01:00
|
|
|
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.
|
|
|
|
|
|
2019-11-16 01:33:09 +01:00
|
|
|
endif # HAS_FLASH_LOAD_OFFSET
|
|
|
|
|
|
2020-02-10 08:37:24 +01:00
|
|
|
config ROM_START_OFFSET
|
2019-01-23 14:13:03 +01:00
|
|
|
hex
|
2020-02-10 08:37:24 +01:00
|
|
|
prompt "ROM start offset" if !BOOTLOADER_MCUBOOT
|
2018-11-02 12:12:07 +01: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
|
2020-02-10 08:37:24 +01:00
|
|
|
space between the beginning of the image and the start of the first
|
2018-11-02 12:12:07 +01:00
|
|
|
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 KERNEL_ENTRY
|
|
|
|
|
string "Kernel entry symbol"
|
|
|
|
|
default "__start"
|
|
|
|
|
help
|
|
|
|
|
Code entry symbol, to be set at linking phase.
|
|
|
|
|
|
2019-03-15 14:05:09 +01: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 12:12:07 +01:00
|
|
|
endmenu
|
|
|
|
|
|
|
|
|
|
menu "Compiler Options"
|
|
|
|
|
|
2020-08-26 18:48:33 +02:00
|
|
|
config CODING_GUIDELINE_CHECK
|
|
|
|
|
bool "Enforce coding guideline rules"
|
|
|
|
|
help
|
|
|
|
|
Use available compiler flags to check coding guideline rules during
|
|
|
|
|
the build.
|
|
|
|
|
|
2018-11-02 12:12:07 +01:00
|
|
|
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
|
|
|
|
|
|
2019-11-24 17:28:38 +01:00
|
|
|
choice
|
|
|
|
|
prompt "Error checking behavior for CHECK macro"
|
|
|
|
|
default RUNTIME_ERROR_CHECKS
|
|
|
|
|
|
|
|
|
|
config ASSERT_ON_ERRORS
|
|
|
|
|
bool "Assert on all errors"
|
|
|
|
|
help
|
|
|
|
|
Assert on errors covered with the CHECK macro.
|
|
|
|
|
|
|
|
|
|
config NO_RUNTIME_CHECKS
|
|
|
|
|
bool "No runtime error checks"
|
|
|
|
|
help
|
|
|
|
|
Do not do any runtime checks or asserts when using the CHECK macro.
|
|
|
|
|
|
|
|
|
|
config RUNTIME_ERROR_CHECKS
|
|
|
|
|
bool "Enable runtime error checks"
|
|
|
|
|
help
|
|
|
|
|
Always perform runtime checks covered with the CHECK macro. This
|
|
|
|
|
option is the default and the only option used during testing.
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2018-11-02 12:12:07 +01:00
|
|
|
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.
|
|
|
|
|
|
2020-05-07 06:38:37 +02:00
|
|
|
config OUTPUT_DISASSEMBLE_ALL
|
|
|
|
|
bool "Disassemble all sections with source. Fill zeros."
|
|
|
|
|
default n
|
|
|
|
|
depends on OUTPUT_DISASSEMBLY
|
|
|
|
|
help
|
|
|
|
|
The .lst file will contain complete disassembly of the firmware
|
|
|
|
|
not just those expected to contain instructions including zeros
|
|
|
|
|
|
2018-11-02 12:12:07 +01:00
|
|
|
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
|
|
|
|
|
|
2020-08-06 23:57:17 +02:00
|
|
|
config BUILD_NO_GAP_FILL
|
|
|
|
|
bool "Don't fill gaps in generated hex/bin/s19 files."
|
|
|
|
|
|
2018-11-02 12:12:07 +01:00
|
|
|
config BUILD_OUTPUT_HEX
|
|
|
|
|
bool "Build a binary in HEX format"
|
|
|
|
|
help
|
2020-08-06 23:57:17 +02:00
|
|
|
Build an Intel HEX binary zephyr/zephyr.hex in the build directory.
|
|
|
|
|
The name of this file can be customized with CONFIG_KERNEL_BIN_NAME.
|
2018-11-02 12:12:07 +01:00
|
|
|
|
|
|
|
|
config BUILD_OUTPUT_BIN
|
|
|
|
|
bool "Build a binary in BIN format"
|
|
|
|
|
default y
|
|
|
|
|
help
|
2020-08-06 23:57:17 +02:00
|
|
|
Build a "raw" binary zephyr/zephyr.bin in the build directory.
|
|
|
|
|
The name of this file can be customized with CONFIG_KERNEL_BIN_NAME.
|
2018-11-02 12:12:07 +01:00
|
|
|
|
|
|
|
|
config BUILD_OUTPUT_EXE
|
|
|
|
|
bool "Build a binary in ELF format with .exe extension"
|
|
|
|
|
help
|
2020-08-06 23:57:17 +02:00
|
|
|
Build an ELF binary that can run in the host system at
|
|
|
|
|
zephyr/zephyr.exe in the build directory.
|
|
|
|
|
The name of this file can be customized with CONFIG_KERNEL_BIN_NAME.
|
2018-11-02 12:12:07 +01:00
|
|
|
|
|
|
|
|
config BUILD_OUTPUT_S19
|
|
|
|
|
bool "Build a binary in S19 format"
|
|
|
|
|
help
|
2020-08-06 23:57:17 +02:00
|
|
|
Build an S19 binary zephyr/zephyr.s19 in the build directory.
|
|
|
|
|
The name of this file can be customized with CONFIG_KERNEL_BIN_NAME.
|
2018-11-26 10:47:16 +01:00
|
|
|
|
2018-11-02 12:12:07 +01:00
|
|
|
config BUILD_OUTPUT_STRIPPED
|
|
|
|
|
bool "Build a stripped binary"
|
|
|
|
|
help
|
2020-08-06 23:57:17 +02:00
|
|
|
Build a stripped binary zephyr/zephyr.strip in the build directory.
|
|
|
|
|
The name of this file can be customized with CONFIG_KERNEL_BIN_NAME.
|
2018-11-02 12:12:07 +01:00
|
|
|
|
|
|
|
|
config APPLICATION_DEFINED_SYSCALL
|
|
|
|
|
bool "Scan application folder for any syscall definition"
|
|
|
|
|
help
|
|
|
|
|
Scan additional folders inside application source folder
|
|
|
|
|
for application defined syscalls.
|
|
|
|
|
|
2019-10-17 14:25:34 +02:00
|
|
|
config MAKEFILE_EXPORTS
|
|
|
|
|
bool "Generate build metadata files named Makefile.exports"
|
|
|
|
|
help
|
|
|
|
|
Generates a file with build information that can be read by
|
|
|
|
|
third party Makefile-based build systems.
|
|
|
|
|
|
2020-06-08 15:29:19 +02:00
|
|
|
config DEPRECATED_ZEPHYR_INT_TYPES
|
|
|
|
|
bool "Allow the use of the deprecated zephyr integer types"
|
2020-05-27 20:16:44 +02:00
|
|
|
help
|
2020-06-08 15:29:19 +02:00
|
|
|
Allows the use of the deprecated Zephyr integer typedefs defined in
|
|
|
|
|
Zephyr 2.3 and previous versions. These types are:
|
|
|
|
|
u8_t, u16_t, u32_t, u64_t, s8_t, s16_t, s32_t, and s64_t.
|
2020-05-27 20:16:44 +02:00
|
|
|
|
2018-11-02 12:12:07 +01:00
|
|
|
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 12:25:43 +01:00
|
|
|
depends on ARM || XTENSA
|
2018-11-02 12:12:07 +01: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-11-16 01:22:16 +01:00
|
|
|
select USE_DT_CODE_PARTITION
|
2018-11-02 12:12:07 +01: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:
|
|
|
|
|
|
2020-02-10 08:37:24 +01:00
|
|
|
* Setting ROM_START_OFFSET to a default value that allows space
|
2018-11-02 12:12:07 +01:00
|
|
|
for the MCUboot image header
|
2020-07-03 16:01:33 +02:00
|
|
|
* Activating SW_VECTOR_RELAY_CLIENT on Cortex-M0
|
|
|
|
|
(or Armv8-M baseline) targets with no built-in vector relocation
|
|
|
|
|
mechanisms
|
2018-11-02 12:12:07 +01:00
|
|
|
|
2020-08-18 20:28:04 +02:00
|
|
|
if BOOTLOADER_MCUBOOT
|
|
|
|
|
|
|
|
|
|
config MCUBOOT_SIGNATURE_KEY_FILE
|
|
|
|
|
string "Path to the mcuboot signing key file"
|
|
|
|
|
default ""
|
|
|
|
|
help
|
|
|
|
|
The file contains a key pair whose public half is verified
|
|
|
|
|
by your target's MCUboot image. The file is in PEM format.
|
|
|
|
|
|
|
|
|
|
If set to a non-empty value, the build system tries to
|
|
|
|
|
sign the final binaries using a 'west sign -t imgtool' command.
|
|
|
|
|
The signed binaries are placed in the build directory
|
|
|
|
|
at zephyr/zephyr.signed.bin and zephyr/zephyr.signed.hex.
|
|
|
|
|
|
|
|
|
|
The file names can be customized with CONFIG_KERNEL_BIN_NAME.
|
|
|
|
|
The existence of bin and hex files depends on CONFIG_BUILD_OUTPUT_BIN
|
|
|
|
|
and CONFIG_BUILD_OUTPUT_HEX.
|
|
|
|
|
|
|
|
|
|
This option should contain an absolute path to the same file
|
|
|
|
|
as the BOOT_SIGNATURE_KEY_FILE option in your MCUboot
|
|
|
|
|
.config. (The MCUboot config option is used for the MCUboot
|
|
|
|
|
bootloader image; this option is for your application which
|
|
|
|
|
is to be loaded by MCUboot. The MCUboot config option can be
|
|
|
|
|
a relative path from the MCUboot repository root; this option's
|
|
|
|
|
behavior is undefined for relative paths.)
|
|
|
|
|
|
|
|
|
|
If left empty, you must sign the Zephyr binaries manually.
|
|
|
|
|
|
|
|
|
|
config MCUBOOT_EXTRA_IMGTOOL_ARGS
|
|
|
|
|
string "Extra arguments to pass to imgtool"
|
|
|
|
|
default ""
|
|
|
|
|
help
|
|
|
|
|
If CONFIG_MCUBOOT_SIGNATURE_KEY_FILE is a non-empty string,
|
|
|
|
|
you can use this option to pass extra options to imgtool.
|
|
|
|
|
For example, you could set this to "--version 1.2".
|
|
|
|
|
|
|
|
|
|
config MCUBOOT_GENERATE_CONFIRMED_IMAGE
|
2020-09-03 20:37:31 +02:00
|
|
|
bool "Also generate a padded, confirmed image"
|
2020-08-18 20:28:04 +02:00
|
|
|
help
|
2020-09-03 20:37:31 +02:00
|
|
|
The signed, padded, and confirmed binaries are placed in the build
|
|
|
|
|
directory at zephyr/zephyr.signed.confirmed.bin and
|
2020-08-18 20:28:04 +02:00
|
|
|
zephyr/zephyr.signed.confirmed.hex.
|
|
|
|
|
|
|
|
|
|
The file names can be customized with CONFIG_KERNEL_BIN_NAME.
|
|
|
|
|
The existence of bin and hex files depends on CONFIG_BUILD_OUTPUT_BIN
|
|
|
|
|
and CONFIG_BUILD_OUTPUT_HEX.
|
|
|
|
|
|
|
|
|
|
endif # BOOTLOADER_MCUBOOT
|
|
|
|
|
|
2018-11-02 12:12:07 +01:00
|
|
|
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
|
|
|
|
|
|
2020-06-13 21:32:11 +02:00
|
|
|
config BOOTLOADER_BOSSA
|
|
|
|
|
bool "BOSSA bootloader support"
|
|
|
|
|
select USE_DT_CODE_PARTITION
|
|
|
|
|
depends on SOC_FAMILY_SAM0
|
|
|
|
|
|
|
|
|
|
help
|
|
|
|
|
Signifies that the target uses a BOSSA compatible bootloader. If CDC
|
|
|
|
|
ACM USB support is also enabled then the board will reboot into the
|
|
|
|
|
bootloader automatically when bossac is run.
|
|
|
|
|
|
|
|
|
|
config BOOTLOADER_BOSSA_DEVICE_NAME
|
|
|
|
|
string "BOSSA CDC ACM device name"
|
|
|
|
|
depends on BOOTLOADER_BOSSA && CDC_ACM_DTE_RATE_CALLBACK_SUPPORT
|
|
|
|
|
default "CDC_ACM_0"
|
|
|
|
|
help
|
|
|
|
|
Sets the CDC ACM port to watch for reboot commands.
|
|
|
|
|
|
|
|
|
|
choice
|
|
|
|
|
prompt "BOSSA bootloader variant"
|
|
|
|
|
depends on BOOTLOADER_BOSSA
|
|
|
|
|
|
|
|
|
|
config BOOTLOADER_BOSSA_ARDUINO
|
|
|
|
|
bool "Arduino"
|
|
|
|
|
help
|
|
|
|
|
Select the Arduino variant of the BOSSA bootloader. Uses 0x07738135
|
|
|
|
|
as the magic value to enter the bootloader.
|
|
|
|
|
|
|
|
|
|
config BOOTLOADER_BOSSA_ADAFRUIT_UF2
|
|
|
|
|
bool "Adafruit UF2"
|
|
|
|
|
help
|
|
|
|
|
Select the Adafruit UF2 variant of the BOSSA bootloader. Uses
|
|
|
|
|
0xf01669ef as the magic value to enter the bootloader.
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2018-11-02 12:12:07 +01:00
|
|
|
config BOOTLOADER_CONTEXT_RESTORE
|
|
|
|
|
bool "Boot loader has context restore support"
|
|
|
|
|
default y
|
2019-02-12 11:07:20 +01:00
|
|
|
depends on SYS_POWER_DEEP_SLEEP_STATES && BOOTLOADER_CONTEXT_RESTORE_SUPPORTED
|
2018-11-02 12:12:07 +01: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-27 20:53:18 +01: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 12:12:07 +01:00
|
|
|
endmenu
|
2019-12-17 18:13:47 +01: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
|