How can one learn microcontrollers effectively? This article shares six key experiences from senior engineer Liu Ping, hoping to resonate with everyone.
1. Correct Understanding of Microcontrollers
Understanding microcontroller technology correctly is essential; it’s not unattainable, nor can it be mastered in just ten days. If this technology were so difficult and profound, how could it be widely applied in real life? Readers must eliminate feelings of “fear” and “awe.” Microcontrollers are a combination of “hardware” and “software”; understanding hardware requires knowledge of software (in fact, once the hardware is set, all variations stem from software). Therefore, many label microcontrollers as “difficult to learn”; of course, they cannot be mastered in just a few days. If microcontrollers could be learned in a few days, would the technology still hold value? Would companies worry about not finding high-tech talent? Moreover, would companies hire engineers who have only studied microcontrollers for ten days? I hope readers can, like me, persist in experimenting after mastering the correct methods.
2. Master Software Development Tools
It is crucial to be proficient with development tools. Speaking of development tools, since these tools operate on PCs, let’s first discuss PCs—not the principles and components of computers. A computer is essential for learning, programming, and researching information. For the wealthy, buying a computer is a trivial matter. However, for someone like me, born in one of the world’s poorest counties, purchasing a computer is no small expense (it took my family a year to prepare for it). Therefore, cherishing a computer goes without saying. After buying a computer, I played a few rounds of CS and Need for Speed, and watched fewer than ten movies. Keeping the computer organized brings a refreshing and pleasant feeling; do not install all software on the C drive or randomly place files on any drive, making it hard to find them, leading to downloading duplicates and turning your computer into a “garbage bin.” You can observe how to organize your computer by watching my recorded videos. Also, do not let your computer become a gaming or movie machine. Of course, it’s fine to play occasionally when tired, but do not be like some classmates whose 320GB hard drives are not enough for games or whose 500GB drives are insufficient for soap operas, requiring them to buy a 1TB external hard drive for storage. Back to the point, if you want to develop microcontrollers, you should at least know how to use Keil; if you’re doing hardware design, you should know how to draw PCBs; otherwise, there is no point in discussing anything else. In specific development, you must master these tools; otherwise, development is impossible. In microcontroller software development, you might use Keil, IAR, STC-ISP, etc.; for circuit simulation, you might use Proteus, Multisim, pSpice, etc.; for PCB design, you might use Altium Designer (or the earlier Protel), PADS, Cadence, and for impedance analysis, Polar; when developing CPLD/FPGA, you might use ISE (Xilinx), Quartus II (Altera), ModelSim, NIOS II, etc.; for ARM and DSP development, you might use ADS and CCS respectively; for upper computer development, you might use VS2010, LabVIEW, Lab/WindowsCVI, etc. Besides these, there are many auxiliary software needed in development, too numerous to list. Among these, I am proficient in all except ADS, CCS, and Cadence. Mastering these tools may not reflect a designer’s ability, but if you cannot even use the tools, how can your ability be demonstrated? Thus, mastering development tools is essential, and reaching a level of proficiency is even better.
3. Balance Theory and Practice
For beginners learning microcontrollers, if you learn in a textbook manner, starting with a pile of instructions and terminology, you may find it tedious and give up after a few days. Therefore, combining learning with practice is an excellent method—learning and practicing in tandem, progressing step by step. This way, you can understand and internalize the instructions used without much time, making them deeply rooted in your mind. After learning a few instructions (not focusing on quantity, but understanding), you should conduct experiments to feel the control effects of the instructions you just learned—visible (lights) and audible (sounds)—which enhances your understanding of how instructions convert into signals for control. Seeing the results of your learning through experiments not only provides a sense of achievement but also increases your interest in microcontrollers. To be honest, microcontrollers are more about learning through experimentation rather than just studying; you should learn with a playful mindset, not just to complete a task. Moreover, conducting experiments is, in itself, a learning process.
4. Invest in Necessary Experimentation Equipment and Books
It is essential to invest appropriately in purchasing experimental equipment and books. Microcontroller technology is highly valuable; once mastered, learning other technologies becomes much easier (e.g., ARM, FPGA, DSP), and the benefits are undoubtedly high. Whether seeking employment or starting your own business, the prospects are bright. Therefore, during learning, be willing to invest in necessary learning and experimental equipment. Additionally, frequently visit science bookstores to purchase books that suit your learning needs. A good book is vital; it allows you to refer back to it anytime, supplementing knowledge you do not understand or have forgotten.
5. Master Soldering Skills
If you choose this field, solid soldering skills are indispensable. Some may argue that soldering is done by machines in factories or by workers, questioning why engineers should solder. In small companies without dedicated soldering workers, the task of soldering the first prototype may fall to hardware engineers. For survival, this may be a choice without options; however, in a slightly more formal company, they would not assign prototype soldering tasks to hardware engineers. Even so, we still need solid soldering skills. In the company where I initially worked, there were two dedicated workers responsible for soldering prototypes, but sometimes, when tasks piled up, the soldering of mainboards would still fall to newcomers. Moreover, debugging later and replacing components or fixing circuits are tasks that hardware engineers must handle. During university, I enjoyed electronics and DIY, often soldering small items, becoming quite skilled with through-hole components. Unfortunately, I did not have the opportunity to solder surface-mounted devices, making me quite unfamiliar with them. I remember discussing with classmates that devices like PQFP-240 (with 240 pins) were impossible to solder by hand, but I found this belief incorrect once at the company. Except for BGA packages, which require hot air guns or BGA rework stations, any component from FQFP-10000 (which does not exist in reality) to 0402 (I have not soldered 0201 yet) can all be soldered with just a soldering iron.
6. Summarize and Document Experiences
Taking notes and writing documents is crucial. Many university students or young people just entering the workforce might think writing documents is merely about Googling or Baidu-ing and piecing together information. I remember during military training in my freshman summer, the camp leader asked us to write a reflection on military training. Two days later, we all submitted our reflections, but the camp leader suddenly called a meeting and was furious, not knowing the reason. He scolded us, saying: “Look at your reflections on military training; how can such a sacred matter be treated lightly?” One student even wrote, “To know the feelings of military training, just search on Baidu!” I digress; back to the point, writing documents is not about randomly searching online. In a company, various documents can sometimes be overwhelming—formal, informal, for others, for oneself, truly a mixed bag. I want to share my insights: formal documents should be written as requested by leaders, while for personal notes, it’s essential to know how to take notes and where to keep them. I must clarify that I do not have the qualifications to critique others; I merely wish to share my growth process with novices, hoping readers can avoid detours. I strongly recommend everyone to write blogs, recording your learning notes on well-known electronic websites like EDNChina, ChinaAET, Elecfans, Eefocus, etc. You can write about book notes, learning notes, project notes, or circuit debugging summaries, or share your life and work experiences. Such articles not only benefit yourself but also others. If you have an apple and exchange it with N people, you still have one apple. However, if you have a piece of information and exchange it with N people, you will have N+1 pieces of information. In these online communities, there are many talented individuals. Readers can check out articles from bloggers like Tequan, sunyzz, coyoo, Observer on the Road, and Wang Jinjin, who write thousands of words in a casual style, allowing you to showcase your talents. I borrowed the writing style of Tequan, combining text and images, which allows everyone to learn while enjoying a visual feast, leaving behind a beautiful memory in my engineering career. Why not?
Friends, let’s work hard! Now we have our parents supporting us, and we do not have to struggle for a living, but time passes quickly. In the blink of an eye, we will enter society and experience the bitterness, helplessness, and trials of life. Or perhaps you are already in the workforce, smoothed out by society, lacking edges and corners. However, since you have chosen this industry and decided to work in technology, you must strive and fight hard. Milk and bread will come. One day, you will be grateful for your past efforts.
Scientists have discovered that only two types of animals can reach the top of the pyramid: one is the eagle, which can easily fly up with its talent and wings. The other is the snail, which has no wings to soar but must climb up, possibly taking a month, two months, or even a year or three years. The process of the snail climbing will certainly not be smooth; it will fall and climb again, fall and climb again. As long as it reaches the top of the pyramid, the world it sees and the achievements it gains will be the same as those of the eagle. As long as you are willing to put in the effort, there will come a day when the little sapling will flourish and grow into a towering tree.