Tucao 51 and STM32

   After I came into contact with STM32, I felt that I had met it too late. In its era, 51 had made great achievements in the field of embedded systems. But today, the battlefield here does not belong to 51. If it were not for the great Chinese educational institutions that can always "keep up with the times", 51 should really appear in the museum.

   If you have used 51, I guarantee that as long as you pass by STM32, you will fall in love with this guy deeply and can't stop, really.

   hardware.

   Speed. The difference between 51 and STM32 is the difference between a bull pulling a cart and a Ferrari. This is obvious enough, you know. 51 is a luxury with 12M. If the code is a little bigger, it can't afford it, so you have to optimize here and there. To be honest, 51 always likes to make things difficult for engineers. STM32, you know how happy it is, it is 72M, 100M at any time, the code runs so happily and so happily. The masters who have come into contact with STM32 know that STM32 is far better than 51 in hardware.

   Configuration above. I can only say, what else does 51 have besides itself. Is there I2C? No! Is there SPI? No! Is there USB? No! Is there Ethernet? Even less! No! No! No! No! No, no! I won't say more, sorry 51.

   Okay, software.

   In this link, STM32 is better than 51, not just a little bit. Why? Everyone on earth knows that STM32 has a low-level driver library, and the code of this library is completely open source. When the masters use this library for development, they are happier than using 51. Using this library to develop software is like traveling, really, if you have experienced 51 code development, it is true. Moreover, using this library, the developed code has few bugs, and using the library has a sense of floating on the shoulders of giants. For example, this library from the Internet master - ST is built by the official team of ST and has been carefully tested. For example, if you want the processor to support the USB U disk function, for 51, you may steal a piece of code on the Internet now, and then stay up all night to start transplanting. The transplantation work itself is very tiring, not to mention the trouble, and there are many bugs. But for STM32, these have long been in the library functions, and they are very mature, so it is very happy, smooth, comfortable, and enjoyable to develop.

   Price, this seems to be the only capital of 51. Wrong, the cheapest STM32 is 8 yuan.

   After going through 51, I found that this is a misunderstanding: before learning ARM, it is best to use 51 to lay the foundation. In fact, there is no need for this. The bottom layer of 51 operation is through the operation of registers, while STM32 achieves the purpose of controlling the bottom layer by calling library functions. These two bottom-level code writing modes are completely different. On the contrary, you will not be able to adapt to the transition from 51 to STM32. Therefore, there is no need to work on 51 first and then STM32. In my experience, you can go directly to STM32. Calling library functions for programming will make you very happy, believe me.

   The above is just a complaint, don’t take it seriously.

   51 has made a lot of contributions to embedded systems and paved the way for experts who have entered the embedded system. After all, 51 is the simplest, easy to use, and not difficult to understand. It is the first and lowest threshold to enter the embedded system. I also passed by 51 and came here. Thank you 51.

    If you are a student, I recommend you to try 51 first, then ARM, after all, this will let you know what is going on at the bottom. You can't be unclear about how to implement the code when doing embedded systems. Of course, as an engineer, there is no need for this. The project time is so tight, how can you have time to be conceited?