michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/arch/arm/soc/st_stm32/stm32f1/soc.h

62 lines
1.2 KiB
C
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 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
*/
/**
* @file SoC configuration macros for the STM32F103 family processors.
*
* Based on reference manual:
* STM32F101xx, STM32F102xx, STM32F103xx, STM32F105xx and STM32F107xx
doc: replace UTF-8 chars Some our Zephyr tools don't like seeing UTF-8 characters, as reported in issue #4131) so a quick scan and replace for UTF-8 characters in .rst, .h, and Kconfig files using "file --mime-encoding" (excluding the /ext folders) finds these files to tweak. Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2017-10-01 10:00:48 -07:00
* advanced ARM(r)-based 32-bit MCUs
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
*
* Chapter 3.3: Memory Map
*/
#ifndef _STM32F1_SOC_H_
#define _STM32F1_SOC_H_
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
#define GPIO_REG_SIZE 0x400
/* base address for where GPIO registers start */
#define GPIO_PORTS_BASE (GPIOA_BASE)
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
#ifndef _ASMLANGUAGE
#include <device.h>
#include <misc/util.h>
subsys: Add random subsystem Some "random" drivers are not drivers at all: they just implement the function `sys_rand32_get()`. Move those to a random subsystem in preparation for a reorganization. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-10-13 15:45:02 -07:00
#include <random/rand32.h>
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
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
#include <stm32f1xx.h>
soc/stm32f1/gpio: implement GPIO support Add functions required for integration with common STM32 GPIO driver. Change-Id: Ic6637e991f5c0cf659f3b927ed47ef482b13b64f Origin: Original Signed-off-by: Maciej Borzecki <maciek.borzecki@gmail.com>
2016-03-06 13:50:48 +01:00
soc/stm32f1: add IRQ numbers listing Add a list of symbolic constants for IRQ lines available on STM32F1 line of MCUs. Change-Id: Iebf1847719c0db31cf852529fe5876e3cabbfe52 Origin: Original Signed-off-by: Maciej Borzecki <maciek.borzecki@gmail.com>
2016-03-13 19:21:42 +01:00
#include "soc_irq.h"
driver: serial: Move STM32 UART driver to LL API STM32 UART driver was using a mix of LL/HAL APIs. This commit removes calls to HAL API and replaces them with LL APIs. No functional change have been seen during non regression testing. But we could note a direct gain of 1Kb of ROM Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2017-09-21 15:20:53 +02:00
#ifdef CONFIG_SERIAL_HAS_DRIVER
#include <stm32f1xx_ll_usart.h>
#endif
drivers: clock_control: provide LL based driver to stm32f1xx series Align stm32f1xx series clock driver to other parts of stm32 family. Driver support both Connectivity and Density lines of stm32f1 series, that are based on different Reset and Clock Control architectures. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2017-05-29 14:52:19 +02:00
#ifdef CONFIG_CLOCK_CONTROL_STM32_CUBE
#include <stm32f1xx_ll_utils.h>
#include <stm32f1xx_ll_bus.h>
#include <stm32f1xx_ll_rcc.h>
#include <stm32f1xx_ll_system.h>
#endif /* CONFIG_CLOCK_CONTROL_STM32_CUBE */
soc: stm32: F1/F3/F4/L4: enable I2C LL Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com> Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
2017-06-23 11:27:17 +02:00
#ifdef CONFIG_I2C
#include <stm32f1xx_ll_i2c.h>
#endif
drivers: spi_ll_stm32: Enable SPI driver for F1 family Enables SPI driver for STM32F1 SoCs Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2017-12-13 13:46:27 +02:00
#ifdef CONFIG_SPI_STM32
#include <stm32f1xx_ll_spi.h>
#endif
iwdg: make independent watchdog driver compliant with STM32Cube LL API Appropriate inclusion done for F1/F3/F4/L4 families in SoC tree. JIRA: ZEP-2347 Signed-off-by: Adam Podogrocki <adam.podogrocki@rndity.com>
2017-06-21 10:36:18 +02:00
#ifdef CONFIG_IWDG_STM32
#include <stm32f1xx_ll_iwdg.h>
#endif
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
#endif /* !_ASMLANGUAGE */
#endif /* _STM32F1_SOC_H_ */
Copy permalink