How about it? After reading so many engineers' discussions in the previous article, do you have some idea about how to learn DSP technology? Take your time. I believe that through the knowledge learning on this website, you will be able to establish a systematic learning method. Next, let's talk about how to start learning DSP based on the author's experience. Perhaps, there is nothing new. Many views have been mentioned before. Here is a summary and supplement. I hope it can bring you some help. In fact, the topic everyone is talking about is not only applicable to DSP, but also a discussion of a learning method that should be suitable for most MCUs. Of course, what is expressed here is only the author's personal opinion, which may not be applicable to everyone. Everyone can summarize and experience the learning method that suits them in the process of learning. This is the best learning method. First, let's talk about the steps of DSP learning. The first thing you need to do is to select a DSP. You have to choose a chip that you think will be useful to you, or a project, or an interest. It is recommended to choose a more popular chip, because there are more materials about popular things, and it is convenient to communicate. For entry-level learning, it is recommended to choose 2812. Next, you have to choose related books. There are still many Chinese textbooks about 2812 in China, which brings great convenience to everyone's learning. This book is also written to help everyone learn 2812. However, it is recommended that you read the Chinese textbooks while combining them with the English documents of T1 Company. The original English expression can not only deepen the understanding of key knowledge points, but also improve English reading ability unconsciously, which is very helpful for future learning and R&D work. ①Reading is the first step in learning. It is impossible to learn a technology without reading. How should I read a book? Many people feel confused when reading a book. They forget the previous part after reading the latter part. This is a normal phenomenon. After all, few people are geniuses who can remember everything they see. What's more, they are faced with extremely difficult and stiff professional terms. Combining my own learning and practical experience, I suggest that you read the book at the beginning. You can take a general look. There is no need to be too careful and understand every problem. Just have a clear idea in your mind, for example, what parts are the internal structure of 2812 and what are the contents of each part. It is worth mentioning that you must not memorize the contents of the registers, because it is useless. You just have to flip through the book. ②After reading the contents of the book, you must be depressed, because if you are learning for the first time, it is very likely that you don't understand most of the things. But it doesn't matter. First build the software and hardware platform required for DSP development and slowly regain your confidence. We can run a routine with phenomena on the development board. It is recommended to choose a marquee. Under your own hands, it should be a big surprise to make the marquee of the DSP board run. For the routine, you need to learn its program framework, such as which files are composed of the project, whether these files are necessary, what is the content of each file, what function it plays, etc. If these are not mentioned in the books you have read before, don't worry, this book will introduce them to you in detail later. In addition, you have to learn the content of the routine. You need to think about the meaning of each statement, why the register is configured in this way, and what function it has. Generally, a routine is related to a certain part of a DSP. At this time, you need to carefully study the content of this part in the book. When looking at the register configuration, you have to look at it one by one in the book, because each bit has a specific meaning. When you understand this routine almost, you can try to rewrite the routine, modify it according to your own understanding, and then verify through experiments whether the modification is correct and consistent with what you understand. In this way, you can truly absorb nutrients from the routine and gain something. ③ After you have mastered two or three routines, you can try to write your own programs. It is recommended that you do not look at the routines first, but write them according to the functions of the routines, and then compare them with the routines to see where the differences are and what you have not considered. The gains after comparative learning will definitely be greater. After learning the routines, you should be able to write the programs you want. Any program with complex functions is composed of several functional modules, so when you master simple functions one by one, writing complex programs should not be a big problem. ④ The previous discussion is about software learning; for hardware, it is recommended to start with imitating the development board, design according to the principle of the development board, and think about why you should do so and whether there is any basis. Don't be afraid of failure. Generally, the probability of one-time success is very small, and there will always be omissions. You can modify it and then make the board. Generally, it is normal to go back and forth two or three times. Hardware requires experience accumulation, and you will naturally have a plan if you do it more. In short, the method of learning DSP well can be summarized as "four mores", that is, more reading, more thinking, more hands-on, and more communication. We have already talked about reading more, thinking more, and doing more. Now let's talk about communicating more. When learning any subject, there must be people who have made a lot of efforts before, so we need to learn based on the experience of predecessors. This requires that in the process of learning, we should communicate more, and not blindly study alone. Sometimes, a problem that you have been thinking about for two or three days may have been summarized and shared with everyone by predecessors. What's more, "there must be a teacher for me when there are kings." Through communication, everyone can complement each other's knowledge. I may not know this problem, but others do. On other problems, I may know it, but others don't. Once everyone communicates, the problem may be solved. In the process of learning, you will definitely encounter many problems and need to seek help or ask questions on the Internet forum, but you also need to pay attention to how to ask questions. First of all, you can't ask questions as soon as you have a problem. At least you should find a way to solve it yourself. Learn to analyze the possible causes of the problem. Look for it in the forum (such as HELLODSP) and search to see if someone has encountered the same problem before and whether there are related discussions. There is really nothing I can do. When posting, you must clearly explain your problem. Don't use simple words like "help". If you don't even have time to summarize the problem or write a complete title, how can you expect others to have time to answer you? Also, don't upload the program in its entirety, just say that the program has errors and ask others to fix it. Because everyone writes programs that vary greatly and have different styles, reading programs is also a very painful thing, so you must analyze them yourself first and figure out the possible problems before asking for help. Finally, not all problems will be of interest to others and will be answered. Asking for help is just a way to find solutions to problems. The most important thing is to figure it out on your own. Seeking help without thinking will only develop a bad habit of relying on others.
|