We have learned about the basic knowledge of UCOS before. Some of the places are not explained in the book translated by Shao Beibei. You can read it in conjunction with that book. If you have any questions or don't understand, please discuss them here. Welcome to remove the questions. This time we mainly understand the file structure of UCOS-II. After understanding the file structure of UCOS, we will explain the key points and difficulties of each chapter one by one, so that you can learn to use UCOS in a short time. We use this picture to dissect the inside of UCOS. We can clearly see the structure and hierarchy of the UCOS kernel. At the bottom of this picture is the hardware we use, that is, our transplant platform, such as the minimum system version of the STM32F103XX series and the minimum system version of 51. Haha, I personally think that there is little meaning in transplanting UCOS to 51. It's OK to learn, but I don't recommend using it! From the picture, we can see that if you want to port UCOS, your hardware platform must have a timer, which is the TIMER in the picture above. This TIMER is used to provide clock beats for UCOS, which is equivalent to our heartbeat. Without this TIMER, nothing can run. Then the software is above. The first layer of software is the focus of our porting. These three files mainly include some processor-related codes. We will discuss these three files in detail when we explain the porting process later. On the upper left are the various files of the system kernel source code. Forum friends who are interested can refer to the book translated by Professor Shao Beibei for in-depth study. Since my main task here is to tell you how to use UCOS, I will not explain the source code too much, but just tell you how to use it. Of course, if you encounter problems during the research process, you can discuss it with everyone. The right side is the system configuration file, which is relatively simple and mainly involves the cutting of some functions. The top layer is our application software, which is equivalent to the Office software we use on computers. Of course, here is your own task code.
|