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

85 lines
1.6 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
*/
/**
arch/arm/soc/st_stm32: Fix typos in soc.h Fix typos in soc.h for stm32f1 and stm32l4 families. Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2018-04-28 16:39:07 +03:00
* @file SoC configuration macros for the STM32F1 family processors.
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
*
* 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_
#ifndef _ASMLANGUAGE
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>
arch: stm32f0/f1/f3/l0: remove core zephyr header inclusions Apply the changes done in commit aee97be to F0, F1, F3, L0 series. Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2018-07-06 13:00:35 +03:00
/* ARM CMSIS definitions must be included before kernel_includes.h.
* Therefore, it is essential to include kernel_includes.h after including
* core SOC-specific headers.
*/
#include <kernel_includes.h>
drivers/interrupt_controller: stm32: Use LL API exti driver implementation does not fit all SoCs because some EXTI ip does not match stm32_exti register map provided. Instead of providing exti register map for all SoCs, use LL API which abstracts IP variations and enable uniform use of the drivers on all STM32SoCs. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2019-01-29 21:09:04 +01:00
#ifdef CONFIG_EXTI_STM32
#include <stm32f1xx_ll_exti.h>
#endif
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: replace use of Kconfig I2C by I2C_STM32 For LL header inclusion, use _STM32 Kconfig symbol (related to the driver), rather than generic symbol, that could theoretically use an alternate solution. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2019-10-10 11:11:57 +02:00
#ifdef CONFIG_I2C_STM32
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
#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
drivers: watchdog: stm32: Add implementation for WWDG Added drivers for System Window Watchdog of STM32 platform. Signed-off-by: Ioannis Konstantelias <ikonstadel@gmail.com>
2019-07-15 16:07:00 +03:00
#ifdef CONFIG_WWDG_STM32
#include <stm32f1xx_ll_wwdg.h>
#endif
soc: arm: st_stm32: Using LL library to implement gpio functions The original implementation of gpio functions access registers directly. Using LL library can add a set of unifying access functions for all series of stm32 for avoiding accessing low level code, and improve readability. Signed-off-by: Song Qiang <songqiang1304521@gmail.com>
2019-01-08 18:12:04 +08:00
#ifdef CONFIG_GPIO_STM32
#include <stm32f1xx_ll_gpio.h>
#endif
drivers: adc: add driver support for ADC1 of stm32 This commit adds driver support for ADC1 on all 8 supported series of stm32 with resolution and conversion time selection and calibration. Currently DMA is not supported for all series, and without it, zephyr won't be able to catch up ADC's end of conversion interrupt, so this version of the driver supports one channel conversion only. Users want multi-channel conversion should use multiple sequences in their app code. This driver uses LL lib rather than HAL because the current HAL lib for ADC will call HAL_DMA_* functions rather than using zephyr's common DMA interface, so that way the driver will break the consistency of the code. This driver has been tested on multiple nucleo boards including NUCLEO_F091RC/F103RB/F207ZG/F302R8/F401RE/F746ZG/L073RZ/L476RG and all passed the test cases in tests/drivers/adc/adc_api. If the external ADC line is floating, it may fail the tests since ADC may get 0V and the test cases think 0 is failing. Connect it to any voltage source between 0-3.3V will help passing the test cases. Signed-off-by: Song Qiang <songqiang1304521@gmail.com>
2019-05-07 16:37:35 +08:00
#ifdef CONFIG_ADC_STM32
#include <stm32f1xx_ll_adc.h>
#endif
drivers: dma: add generic driver support for some series of stm32 This commit adds driver support for DMA on f0/f1/f2/f3/f4/l0/l4 series stm32. Notice due to some bugs, this is currently not working with f7. There are two kinds of IP blocks are used across these stm32, one is the one that has been used on F2/F4/F7 series, and the other one is the one that has been used on F0/F1/F3/L0/L4 series. Memory to memory transfer is only supported on the second DMA on F2/F4 with 'st,mem2mem' to be declared in dts. This driver depends on k_malloc to allocate memory for stream instances, so CONFIG_HEAP_MEM_POOL_SIZE must be big enough to hold them. Common parts of the driver are in dma_stm32.c and SoC related parts are implemented in dma_stm32_v*.c. This driver has been tested on multiple nucleo boards, including NUCLEO_F091RC/F103RB/F207ZG/F302R8/F401RE/L073RZ/L476RG with the loop_transfer and chan_blen_transfer test cases. Signed-off-by: Song Qiang <songqiang1304521@gmail.com>
2019-10-24 19:06:19 +08:00
#ifdef CONFIG_DMA_STM32
#include <stm32f1xx_ll_dma.h>
#endif
SoC: stm32: Include LL utilities if HWINFO is selected Include stm32XXxx_ll_utils.h in soc.h for every stm32 SoC, if CONFIG_HWINFO_STM32 is selected. Signed-off-by: Alexander Wachter <alexander@wachter.cloud>
2020-02-20 12:37:03 +01:00
#ifdef CONFIG_HWINFO_STM32
#include <stm32f1xx_ll_utils.h>
#endif
drivers: pwm: stm32: refactor driver using LL API The PWM drivers has been refactored using the HAL LL API. Not only that, but the set pin_set function is now faster, as channel output compare is just initialized if needed. NOTE: Has been tested using H743zi board for now. Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
2020-04-21 21:50:03 +02:00
#ifdef CONFIG_PWM_STM32
#include <stm32f1xx_ll_tim.h>
#endif /* CONFIG_PWM_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 15:32:21 +01:00
#endif /* !_ASMLANGUAGE */
#endif /* _STM32F1_SOC_H_ */
Copy permalink