From afbb4cc73c44b6321cae39dbe46b97155805097d Mon Sep 17 00:00:00 2001 From: Trygve Laugstøl Date: Sun, 13 Dec 2015 21:03:11 +0100 Subject: wip --- .../MDK-ARM/readme.txt | 85 ++++++++++++++++++++++ 1 file changed, 85 insertions(+) create mode 100644 tmp/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Template/MDK-ARM/readme.txt (limited to 'tmp/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Template/MDK-ARM/readme.txt') diff --git a/tmp/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Template/MDK-ARM/readme.txt b/tmp/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Template/MDK-ARM/readme.txt new file mode 100644 index 0000000..c647c15 --- /dev/null +++ b/tmp/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Template/MDK-ARM/readme.txt @@ -0,0 +1,85 @@ +/** + @page mdkarm MDK-ARM Project Template + + @verbatim + ******************** (C) COPYRIGHT 2011 STMicroelectronics ******************* + * @file readme.txt + * @author MCD Application Team + * @version V3.5.0 + * @date 08-April-2011 + * @brief This sub directory contains all the user modifiable files needed + * to create a new project linked with the STM32F10x Standard Peripheral + * Library and working with RealView MDK-ARM toolchain (Version 4.12 and later). + ****************************************************************************** + * THE PRESENT FIRMWARE WHICH IS FOR GUIDANCE ONLY AIMS AT PROVIDING CUSTOMERS + * WITH CODING INFORMATION REGARDING THEIR PRODUCTS IN ORDER FOR THEM TO SAVE TIME. + * AS A RESULT, STMICROELECTRONICS SHALL NOT BE HELD LIABLE FOR ANY DIRECT, + * INDIRECT OR CONSEQUENTIAL DAMAGES WITH RESPECT TO ANY CLAIMS ARISING FROM THE + * CONTENT OF SUCH FIRMWARE AND/OR THE USE MADE BY CUSTOMERS OF THE CODING + * INFORMATION CONTAINED HEREIN IN CONNECTION WITH THEIR PRODUCTS. + ****************************************************************************** + @endverbatim + + @par Directory contents + + - Project.Uv2/.Opt: A pre-configured project file with the provided library structure + that produces an executable image with MDK-ARM + +Enabling "Options for Target 'Output' Browser Information" is useful for quick +source files navigation but may slow the compilation time. + +@note the @subpage note file contains the needed steps to follow when using the +default startup file provided by MDK-ARM when creating new projects. + + @par How to use it ? + + - Open the Project.uvproj project + - In the build toolbar select the project config: + - STM32100B-EVAL: to configure the project for STM32 Medium-density Value + line devices + @note The needed define symbols for this config are already declared in the + preprocessor section: USE_STDPERIPH_DRIVER, STM32F10X_MD_VL, USE_STM32100B_EVAL + + - STM3210C-EVAL: to configure the project for STM32 Connectivity line devices + @note The needed define symbols for this config are already declared in the + preprocessor section: USE_STDPERIPH_DRIVER, STM32F10X_CL, USE_STM3210C_EVAL + + - STM3210B-EVAL: to configure the project for STM32 Medium-density devices + @note The needed define symbols for this config are already declared in the + preprocessor section: USE_STDPERIPH_DRIVER, STM32F10X_MD, USE_STM3210B_EVAL + + - STM3210E-EVAL: to configure the project for STM32 High-density devices + @note The needed define symbols for this config are already declared in the + preprocessor section: USE_STDPERIPH_DRIVER, STM32F10X_HD, USE_STM3210E_EVAL + + - STM3210E-EVAL_XL: to configure the project for STM32 XL-density devices + @note The needed define symbols for this config are already declared in the + preprocessor section: USE_STDPERIPH_DRIVER, STM32F10X_XL, USE_STM3210E_EVAL + + - STM32100E-EVAL: to configure the project for STM32 High-density Value line devices + @note The needed define symbols for this config are already declared in the + preprocessor section: USE_STDPERIPH_DRIVER, STM32F10X_HD_VL, USE_STM32100E_EVAL + + - Rebuild all files: Project->Rebuild all target files + - Load project image: Debug->Start/Stop Debug Session + - Run program: Debug->Run (F5) + +@note + - Low-density Value line devices are STM32F100xx microcontrollers where the + Flash memory density ranges between 16 and 32 Kbytes. + - Low-density devices are STM32F101xx, STM32F102xx and STM32F103xx + microcontrollers where the Flash memory density ranges between 16 and 32 Kbytes. + - Medium-density Value line devices are STM32F100xx microcontrollers where + the Flash memory density ranges between 64 and 128 Kbytes. + - Medium-density devices are STM32F101xx, STM32F102xx and STM32F103xx + microcontrollers where the Flash memory density ranges between 64 and 128 Kbytes. + - High-density Value line devices are STM32F100xx microcontrollers where + the Flash memory density ranges between 256 and 512 Kbytes. + - High-density devices are STM32F101xx and STM32F103xx microcontrollers where + the Flash memory density ranges between 256 and 512 Kbytes. + - XL-density devices are STM32F101xx and STM32F103xx microcontrollers where + the Flash memory density ranges between 512 and 1024 Kbytes. + - Connectivity line devices are STM32F105xx and STM32F107xx microcontrollers. + + *

© COPYRIGHT 2011 STMicroelectronics

+ */ -- cgit v1.2.3