aboutsummaryrefslogtreecommitdiff
path: root/tmp/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Template/HiTOP/STM3210E-EVAL/readme.txt
diff options
context:
space:
mode:
authorTrygve Laugstøl <trygvis@inamo.no>2017-01-25 22:24:18 +0100
committerTrygve Laugstøl <trygvis@inamo.no>2017-01-25 22:29:25 +0100
commit40e04e3772726829d66c12e69f24b03920d79c67 (patch)
tree636811bad956798c9d5d22de9e7ba8c799b8d791 /tmp/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Template/HiTOP/STM3210E-EVAL/readme.txt
parent2fff65aed2477a503c72629d27e2a330d30c02d1 (diff)
downloadstm32f103-playground-40e04e3772726829d66c12e69f24b03920d79c67.tar.gz
stm32f103-playground-40e04e3772726829d66c12e69f24b03920d79c67.tar.bz2
stm32f103-playground-40e04e3772726829d66c12e69f24b03920d79c67.tar.xz
stm32f103-playground-40e04e3772726829d66c12e69f24b03920d79c67.zip
o Moving tinyprintf and stm libraries under thirdparty.
Diffstat (limited to 'tmp/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Template/HiTOP/STM3210E-EVAL/readme.txt')
-rw-r--r--tmp/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Template/HiTOP/STM3210E-EVAL/readme.txt112
1 files changed, 0 insertions, 112 deletions
diff --git a/tmp/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Template/HiTOP/STM3210E-EVAL/readme.txt b/tmp/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Template/HiTOP/STM3210E-EVAL/readme.txt
deleted file mode 100644
index 7e4c10b..0000000
--- a/tmp/STM32F10x_StdPeriph_Lib_V3.5.0/Project/STM32F10x_StdPeriph_Template/HiTOP/STM3210E-EVAL/readme.txt
+++ /dev/null
@@ -1,112 +0,0 @@
-/**
- @page HiTOP5_STM3210E HiTOP Project Template for STM32F10x High-density devices
-
- @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 Peripherals
- * Library and working with HiTOP software toolchain (version 5.40 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.htp: A pre-configured project file with the provided library
- structure that produces an executable image with HiTOP
-
- - cstart_thumb2.asm: This file initializes the stack pointer and copy initialized
- sections from ROM to RAM.
-
- - Objects: This mandatory directory contains the executable images.
-
- - Settings: This directory contains the linker and script files.
- - arm_arch.lsl: This file is used to place program code (readonly)
- in internal FLASH and data (readwrite, Stack and Heap)
- in internal SRAM.
-
- - flash_nor.scr: This file is a HiTOP script allowing the FSMC configuration.
- It should be executed before programming the NOR flash of the
- STM32 High-density devices.
-
- - link.lnk: This file is the HiTOP linker it invokes the STM32F10x_hd.lsl.
-
- - linkextsram.lnk: This file is the HiTOP linker it invokes the STM32F10x_extsram.lsl.
-
- - linknor.lnk: This file is the HiTOP linker it invokes the STM32F10xnor.lsl.
-
- - reset_appl.scr: This file is a HiTOP script it performs a target reset.
-
- - reset_go_main.scr: This file is a HiTOP script and it sets the Program
- Counter at the "main" instruction.
-
- - StartupScript.scr: This file is a HiTOP script and it performs a target
- reset before loading The executable image.
-
- - STM32F10x_extsram.lsl: This file used to place program code (readonly) in
- internal FLASH and data (readwrite, Stack and Heap)
- in external SRAM.
- It contains also the vector table of the STM32 high-density
- devices.
- You can customize this file to your need.
- This file is used only with STM32 High-density devices.
-
- - STM32F10x_hd.lsl: This file is used to place program code (readonly)
- in internal FLASH and data (readwrite, Stack and Heap)
- in internal SRAM.
- It contains also the vector table of the STM32
- High-Density devices.
- You can customize this file to your need.
-
- - STM32F10xnor.lsl: This file used to place program code (readonly) in
- external NOR FLASH and data (readwrite, Stack and Heap)
- in internal SRAM.
- It contains also the vector table of the STM32 high-density
- devices.
- You can customize this file to your need.
- This file is used only with STM32 High-density devices.
-
-@par How to use it ?
-
-- Open the HiTOP toolchain.
-- Browse to open the project.htp
-- A "Download application" window is displayed, click "cancel".
-- Rebuild all files: Project->Rebuild all
-- Load project image : Click "ok" in the "Download application" window.
-- Run the "RESET_GO_MAIN" script to set the PC at the "main"
-- Run program: Debug->Go(F5).
-
-- When using High-density devices, it is mandatory to reset the target before
- loading the project into target
-- It is recommended to run the reset script ( click on TR button in the toolbar menu)
- after loading the project into target.
-
-@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.
-
- * <h3><center>&copy; COPYRIGHT 2011 STMicroelectronics</center></h3>
- */