Summary of experiences in software and hardware development

1. Read the analysis of one thread and one thread in a program. Because the program is generally large, we can take a small part of it for analysis. Every thread may include many functions. They may be in different files. We can extract them and summarize them.

2. For vulnerabilities in a certain knowledge point in a program, search for relevant information on Google, and find the definition, principle, example, and program content.

3. When building the software environment, we should be good at summing up and look at the loaded files and what types of files. The simplest thing is to translate English into Chinese, this habit should be formed after completing step by step.

4. We will certainly encounter many problems during the project process. We can summarize the problems and clarify our ideas.

5. There are also ideas for testing commands or boards that you don't understand. It is very important to determine what the test ideas look like:

1. Confirm what parameters are fixed and what is variable.

2. It is important to know what values can be set for these variable parameters!

3. Check the dependency between variable parameters.

4. determine the number of combinations of test commands.

5. Determine the parameter settings required for testing our board.

6. What is the test result?

6. Some information may not be found on the Internet. At this time, we can test the software and hardware debugging method to determine the meaning of some variables.

7. Software development not only supports understanding programs, but also requires building a development environment, such as viewing script files, makefile, and shell, the consciousness here is to focus on understanding the files, file types, and variables in folders. This is quite complicated.

8. problems may occur in some details, including program, software version, hardware address or cache, makefile, and shell script files.

9. After completing the project, make a summary.