這是STM32固件庫原版，中文版有一些函數(shù)沒有

Introduction This document describes the ARM?-based 32-bit MCU STM32F101xx and STM32F103xx firmware library.

This library is a firmware package which contains a collection of routines， data structures and macros covering the features of all peripherals. It includes a description of the device drivers plus a set of examples for each peripheral. The firmware library allows any device to be used in the user application without the need for in-depth study of each peripheral specifications. As a result， using the firmware library saves significant time that would otherwise be spent in coding， while reducing the application development and integration cost.

Each device driver consists of a set of functions covering all peripheral functionalities. The development of each driver is driven by a common API （application programming interface） which standardizes the driver structure， the functions and the names of parameters. The driver source code is developed in ‘Strict ANSI-C’ （relaxed ANSI-C for projects and examples files）。 It is fully documented and is MISRA-C 2004 compliant （the compliancy matrix is available upon request）。 Writing the whole library in ‘Strict ANSI-C’ makes it independent from the software toolchain. Only the start-up files depend on the toolchain. The firmware library implements run-time failure detection by checking the input values for all library functions.

This dynamic checking contributes to enhance the robustness of the software. Run-time detection is suitable for user application development and debugging. It adds an overhead and can be removed from the final application code to minimize code size and execution speed. For more details refer to Section 2.5： Run-time checking on page 48. Since the firmware library is generic and covers all peripherals functionalities， the size and/or execution speed of the application code may not be optimized.

For many applications， the library may be used as is. However， for applications having tough constraints in terms of code size and/or execution speed， the library drivers should be used as a reference on how to configure the peripheral and tailor them to specific application requirements.

The firmware library user manual is structured as follows： ■ Definitions， document conventions and firmware library rules

■ Overview of the firmware library （package content， library structure）， installation guidelines， and example on how to use the library.

■ Detailed description the firmware library： configuration structure and software functions for each peripheral.