michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/soc/arm/st_stm32/stm32f1/Kconfig.series

15 lines
338 B
Text
Raw Normal View History

kconfig: Clean up header comments and make them consistent Use this short header style in all Kconfig files: # <description> # <copyright> # <license> ... Also change all <description>s from # Kconfig[.extension] - Foo-related options to just # Foo-related options It's clear enough that it's about Kconfig. The <description> cleanup was done with this command, along with some manual cleanup (big letter at the start, etc.) git ls-files '*Kconfig*' | \ xargs sed -i -E '1 s/#\s*Kconfig[\w.-]*\s*-\s*/# /' Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-11-01 13:45:29 +01:00
# ST Microelectronics STM32F1 MCU series
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 15:32:21 +01:00
# 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-18 17: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 15:32:21 +01: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-02 23:36:02 -04:00
config SOC_SERIES_STM32F1X
bool "STM32F1x Series MCU"
select CPU_CORTEX_M3
soc: arm: st_stm32: Select CPU DWT feature symbol The Data Watchpoint and Trace (DWT) is an optional debug unit for the Cortex-M family cores (except ARMv6-M; i.e. M0 and M0+) that provides watchpoints, data tracing and system profiling capabilities. Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
2020-01-10 10:51:17 +09:00
select CPU_CORTEX_M_HAS_DWT
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-02 23:36:02 -04:00
select SOC_FAMILY_STM32
stm32f1: Enable STM32Cube SDK support on stm32f1 family Create HAS_CUBE config flag to control activation of STM32Cube support. Generate fitting compilation options for STM32Cube in /ext/hal/stm32cube/Makefile soc.h is updated to include minimum include files from ext/hal/stm23cube Change-Id: If58ce0a4fdb7fbf5f171dfe5f1f8eb75126a8313 Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2016-11-02 09:58:02 +01:00
select HAS_STM32CUBE
soc: stm32: add SWO logger backend support This patch adds HAS_SWO selections to all STM32 SoCs supporting Serial Wire Output via the Trace Port Interface Unit (TPIU). Signed-off-by: Markus Fuchs <markus.fuchs@de.sauter-bc.com>
2019-07-13 22:02:34 +02:00
select HAS_SWO
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-02 23:36:02 -04:00
help
kconfig: Global whitespace/consistency cleanup Clean up space errors and use a consistent style throughout the Kconfig files. This makes reading the Kconfig files more distraction-free, helps with grepping, and encourages the same style getting copied around everywhere (meaning another pass hopefully won't be needed). Go for the most common style: - Indent properties with a single tab, including for choices. Properties on choices work exactly the same syntactically as properties on symbols, so not sure how the no-indentation thing happened. - Indent help texts with a tab followed by two spaces - Put a space between 'config' and the symbol name, not a tab. This also helps when grepping for definitions. - Do '# A comment' instead of '#A comment' I tweaked Kconfiglib a bit to find most of the stuff. Some help texts were reflowed to 79 columns with 'gq' in Vim as well, though not all, because I was afraid I'd accidentally mess up formatting. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-11-01 10:24:07 +01:00
Enable support for STM32F1 MCU series
Copy permalink