OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/arch/arm/soc/st_stm32/Kconfig

30 lines
555 B
Plaintext
Raw Normal View History

st_stm32/stm32f1: introduce STM32F1x SoC family The patch introduces a new family of SoCs based on STMicroelectronics' STM32 MCU line. The patch introduces a basic arch/arm/soc layout along with configuration of 2 MCUs from STM32F1 series: STM32F103VE and STM32F103RB. The patch assumes that other MCUs from STM32 family will be included under arch/arm/soc/st_stm32 tree, to achieve the following layout: arch/ arm/ soc/ st_stm32/ stm32f0/ stm32f1/ stm32f2/ ... stm32l0/ Most of the configuration within a single MCU family (ex. STM32F1) is shared, however individual MCUs differ with respect to SRAM size, flash size or the number of available peripherals. The patch assumes that per MCU line Kconfig.soc.family file should introduce basic setup for given series. This can be further tuned by per MCU files, with Kconfig.soc.stm32f103rb and Kconfig.soc.stm32f103ve as examples. Each family defines a configuration option, ex. CONFIG_STM32F10X, while individual MCUs define a corresponding per MCU config options, ex. CONFIG_STM32F103VE. From the menuconfig perspective, the user is presented with a family selection under General Platform Configuration/SoC Selection. A specific MCU model can be selected by accessing General Platform Configuration/STM32F1x MCU Selection, with the default entry being selected by the board configuration. Change-Id: I22e4defd4a08ed1b2e2cad0e214b34f565e08831 Origin: Original Signed-off-by: Maciej Borzecki <maciek.borzecki@gmail.com>
2016-03-03 22:32:21 +08:00
# Kconfig - ST Microelectronics STM32 MCU line
#
# Copyright (c) 2016 Open-RnD Sp. z o.o.
#
license: Replace Apache boilerplate with SPDX tag Replace the existing Apache 2.0 boilerplate header with an SPDX tag throughout the zephyr code tree. This patch was generated via a script run over the master branch. Also updated doc/porting/application.rst that had a dependency on line numbers in a literal include. Manually updated subsys/logging/sys_log.c that had a malformed header in the original file. Also cleanup several cases that already had a SPDX tag and we either got a duplicate or missed updating. Jira: ZEP-1457 Change-Id: I6131a1d4ee0e58f5b938300c2d2fc77d2e69572c Signed-off-by: David B. Kinder <david.b.kinder@intel.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-01-19 09:01:01 +08:00
# SPDX-License-Identifier: Apache-2.0
st_stm32/stm32f1: introduce STM32F1x SoC family The patch introduces a new family of SoCs based on STMicroelectronics' STM32 MCU line. The patch introduces a basic arch/arm/soc layout along with configuration of 2 MCUs from STM32F1 series: STM32F103VE and STM32F103RB. The patch assumes that other MCUs from STM32 family will be included under arch/arm/soc/st_stm32 tree, to achieve the following layout: arch/ arm/ soc/ st_stm32/ stm32f0/ stm32f1/ stm32f2/ ... stm32l0/ Most of the configuration within a single MCU family (ex. STM32F1) is shared, however individual MCUs differ with respect to SRAM size, flash size or the number of available peripherals. The patch assumes that per MCU line Kconfig.soc.family file should introduce basic setup for given series. This can be further tuned by per MCU files, with Kconfig.soc.stm32f103rb and Kconfig.soc.stm32f103ve as examples. Each family defines a configuration option, ex. CONFIG_STM32F10X, while individual MCUs define a corresponding per MCU config options, ex. CONFIG_STM32F103VE. From the menuconfig perspective, the user is presented with a family selection under General Platform Configuration/SoC Selection. A specific MCU model can be selected by accessing General Platform Configuration/STM32F1x MCU Selection, with the default entry being selected by the board configuration. Change-Id: I22e4defd4a08ed1b2e2cad0e214b34f565e08831 Origin: Original Signed-off-by: Maciej Borzecki <maciek.borzecki@gmail.com>
2016-03-03 22:32:21 +08:00
#
stm32: rename CONFIG_SOC_STM32 -> CONFIG_SOC_FAMILY_STM32 Use CONFIG_SOC_FAMILY for the top level SoC family. A family will have different SoCs or different SoC series with multiple SoCs. Adding the Family string to the config variable to avoid confusion between actual SoCs and families and to prevent name collisions. Change-Id: Ic99a2c1df7850dee3a45641027af82464dd6fadb Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-04-03 10:29:40 +08:00
config SOC_FAMILY_STM32
st_stm32/stm32f1: introduce STM32F1x SoC family The patch introduces a new family of SoCs based on STMicroelectronics' STM32 MCU line. The patch introduces a basic arch/arm/soc layout along with configuration of 2 MCUs from STM32F1 series: STM32F103VE and STM32F103RB. The patch assumes that other MCUs from STM32 family will be included under arch/arm/soc/st_stm32 tree, to achieve the following layout: arch/ arm/ soc/ st_stm32/ stm32f0/ stm32f1/ stm32f2/ ... stm32l0/ Most of the configuration within a single MCU family (ex. STM32F1) is shared, however individual MCUs differ with respect to SRAM size, flash size or the number of available peripherals. The patch assumes that per MCU line Kconfig.soc.family file should introduce basic setup for given series. This can be further tuned by per MCU files, with Kconfig.soc.stm32f103rb and Kconfig.soc.stm32f103ve as examples. Each family defines a configuration option, ex. CONFIG_STM32F10X, while individual MCUs define a corresponding per MCU config options, ex. CONFIG_STM32F103VE. From the menuconfig perspective, the user is presented with a family selection under General Platform Configuration/SoC Selection. A specific MCU model can be selected by accessing General Platform Configuration/STM32F1x MCU Selection, with the default entry being selected by the board configuration. Change-Id: I22e4defd4a08ed1b2e2cad0e214b34f565e08831 Origin: Original Signed-off-by: Maciej Borzecki <maciek.borzecki@gmail.com>
2016-03-03 22:32:21 +08:00
bool
# omit prompt to signify a "hidden" option
arch/arm: stm32: All SoCs have dts for I2C and SPI All boards based on STM32 should use dts for I2C and SPI. Move CONFIG flags selection from boards to arch and select them for all STM32 SoCs. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2018-04-10 20:19:07 +08:00
select HAS_DTS_I2C_DEVICE if I2C
select HAS_DTS_SPI_DEVICE if SPI
st_stm32/stm32f1: introduce STM32F1x SoC family The patch introduces a new family of SoCs based on STMicroelectronics' STM32 MCU line. The patch introduces a basic arch/arm/soc layout along with configuration of 2 MCUs from STM32F1 series: STM32F103VE and STM32F103RB. The patch assumes that other MCUs from STM32 family will be included under arch/arm/soc/st_stm32 tree, to achieve the following layout: arch/ arm/ soc/ st_stm32/ stm32f0/ stm32f1/ stm32f2/ ... stm32l0/ Most of the configuration within a single MCU family (ex. STM32F1) is shared, however individual MCUs differ with respect to SRAM size, flash size or the number of available peripherals. The patch assumes that per MCU line Kconfig.soc.family file should introduce basic setup for given series. This can be further tuned by per MCU files, with Kconfig.soc.stm32f103rb and Kconfig.soc.stm32f103ve as examples. Each family defines a configuration option, ex. CONFIG_STM32F10X, while individual MCUs define a corresponding per MCU config options, ex. CONFIG_STM32F103VE. From the menuconfig perspective, the user is presented with a family selection under General Platform Configuration/SoC Selection. A specific MCU model can be selected by accessing General Platform Configuration/STM32F1x MCU Selection, with the default entry being selected by the board configuration. Change-Id: I22e4defd4a08ed1b2e2cad0e214b34f565e08831 Origin: Original Signed-off-by: Maciej Borzecki <maciek.borzecki@gmail.com>
2016-03-03 22:32:21 +08:00
stm32: reorganise soc directory and use family/series Use SoC family/series and reoganise the structure to follow new hierarchy. Change-Id: I8637f1487a8287a6614ce6636cd018cf342fec95 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-04-03 11:36:02 +08:00
if SOC_FAMILY_STM32
build: use kconfig to select generated artifacts Not all boards require the various binary formats zephyr generates. So be selective based on the arch, SoC or board and only geenrate the binaries actually needed. Fixes #5009 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-11-23 02:03:53 +08:00
stm32: reorganise soc directory and use family/series Use SoC family/series and reoganise the structure to follow new hierarchy. Change-Id: I8637f1487a8287a6614ce6636cd018cf342fec95 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-04-03 11:36:02 +08:00
config SOC_FAMILY
string
soc: soc_family: Consistently quote string defaults In preparation for introducing a warning. Unquoted string defaults work through a quirk of Kconfig (undefined symbols get their name as their string value), but look confusing. It's done inconsistently now too. Suggested by Kumar Gala. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-05-26 03:12:24 +08:00
default "st_stm32"
stm32: reorganise soc directory and use family/series Use SoC family/series and reoganise the structure to follow new hierarchy. Change-Id: I8637f1487a8287a6614ce6636cd018cf342fec95 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-04-03 11:36:02 +08:00
arm: soc: stm32: make mpu f4 config useable for other family As other stm32 series support MPU, move common file in a file tree useable by socs from other series JIRA: ZEP-2220 Signed-off-by: Michel Jaouen <michel.jaouen@st.com>
2017-06-09 23:18:09 +08:00
config STM32_ARM_MPU_ENABLE
arm: soc: Elaborate Kconfig strings for MPU selection Some of the SoCs specify "Enable MPU" in Kconfig for enabling MPU support. This will create ambiguity while selecting options via menuconfig. Hence, append SoC family name to the selection strings to looks more elaborative. Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
2018-04-28 11:28:14 +08:00
bool "Enable MPU on STM32"
arm: soc: stm32: make mpu f4 config useable for other family As other stm32 series support MPU, move common file in a file tree useable by socs from other series JIRA: ZEP-2220 Signed-off-by: Michel Jaouen <michel.jaouen@st.com>
2017-06-09 23:18:09 +08:00
depends on CPU_HAS_MPU
select ARM_MPU
help
arm: soc: Elaborate Kconfig strings for MPU selection Some of the SoCs specify "Enable MPU" in Kconfig for enabling MPU support. This will create ambiguity while selecting options via menuconfig. Hence, append SoC family name to the selection strings to looks more elaborative. Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
2018-04-28 11:28:14 +08:00
Enable MPU support on STM32 SoCs
arm: soc: stm32: make mpu f4 config useable for other family As other stm32 series support MPU, move common file in a file tree useable by socs from other series JIRA: ZEP-2220 Signed-off-by: Michel Jaouen <michel.jaouen@st.com>
2017-06-09 23:18:09 +08:00
kconfig: Make 'source' non-globbing and use 'gsource' Until now, Zephyr has used a patched Kconfiglib that turns 'source' into a globbing source (by replacing 'source' with 'gsource' at the token level). There's two problems with this: - The patch needs to be maintained separately - Misspelled filenames are silently ignored, as they look like glob patterns that don't match anything Fix it as follows: 1. Replace all 'source' statements that use wildcards with 'gsource' 2. Remove the custom Kconfiglib patch so that 'source' no longer globs The sed pattern '/source.*[*?]/s/source/gsource/' was run over all Kconfig* files to do the replacement. source's that use environment variables that might contain glob patterns were manually changed to gsource. Building the docs in doc/ is a good test, as doc/Makefile deliberately sets the environment variables to glob up as many Kconfig files as possible. Signed-off-by: Ulf Magnusson <ulfalizer@gmail.com>
2018-05-08 15:31:48 +08:00
gsource "arch/arm/soc/st_stm32/*/Kconfig.soc"
arch: arm: soc: Cleanup Kconfig inclusion per SoC When we included SoC specific Kconfig files we do something like: gsource "arch/arm/soc/arm/*/Kconfig.soc" However, we should do that inside an if block for that SoC family so as to limit SoC family specific options to only being visible when that SoC family is selected. So we simply move the gsource and related items inside the if SOC_FAMILY_<SOC> block. Fixes: #7452 Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2018-05-10 23:17:19 +08:00
endif # SOC_FAMILY_STM32