![]() ![]() The standard peripheral Library covers all standard peripherals from GPIO to timer, and then to can, I2C, SPI, UART and ADC. In short, the biggest advantage of using standard peripheral library for development is that developers can use every peripheral flexibly and normatively without in-depth understanding of the underlying hardware details. This book uses the current version of v3.4.ġ.1.2 advantages of using standard peripheral Library Development The version after V3.0 has changed a lot compared with the previous version. Since the MDK arm3.23 released in September 2008, the v2.0 firmware library has been used. The v2.0 firmware library was released in June 2008. ST company released v1.0 firmware library in October 2007, which is supported by versions before MDK arm3.22. The development of each device is driven by an application programming interface (API), which standardizes the structure, function and parameter name of the driver. Each peripheral driver consists of a set of functions, which cover all the functions of the peripheral. Therefore, the use of solid-state function library can greatly reduce the user’s programming time, thereby reducing the development cost. By using the firmware function library, developers can easily apply each peripheral without mastering the details of the underlying hardware. ![]() The function library also includes the driver description and application examples of each peripheral, which provides an intermediate API for developers to access the underlying hardware. The previous version of STM32 standard peripheral library, also known as firmware function library or firmware library for short, is a firmware function package, which consists of program, data structure and macro, including the performance characteristics of all peripheral devices of microcontroller. 1.1 software development based on standard peripheral library 1.1.1 overview of STM32 standard peripheral Library ![]() Please correct the specific deficiencies. Limited by my level, it is inevitable that there are great limitations. I’ll try my best to explain the cause and effect clearly. Many people write tutorials to tell you how to do it, but not why. Part of it refers to the description of the firmware library, but it is basically re expressed and rewritten in the order that I understand. Based on my understanding of the firmware library, the content of this paper is sorted out and introduced in the order that is easy to understand. Recently, I post some of the contents, and welcome to correct me. I have written a lot before, but I don’t feel that each chapter is particularly complete. Recently, there have been many examinations, and the compilation of teaching materials has been suspended for a while. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |