First state a concept, naked programming, a term I coined, which refers to writing programs on bare metal, naked metal, inMicrocontrollerThe field refers to the microcontroller control system with hardware, don't think about it.
Programming on bare metal is like reclaiming a wasteland, and any hoe will hit a hard stone. The pioneers pursue an oasis in the coming year. And what are the so-called engineers who reclaim bare metal pursuing? Of course, we are looking for a task.
We generally claim to be high-level intellectuals, so what should we think about in the process of pioneering? Of course, it is not about how to complete the task, but first of all thinking about what we are thinking. Did you go around it? It's right to go around it, and this circle goes around the thought. Thought is the commander of a simple person doing everything in a complex environment, which affects every detail of a pioneer's life, including naked programming itself, of course.
When a person holds a hoe, hoe after hoe, sweat drips under their feet, can we know what they are thinking? Of course, this is hard to say, if you go to the hoe yourself, you will know. But it's probably the same, just a few: Why is this sun so fucking poisonous? Why are there so many fucking stones? What is the best place to plant here? How many days will this be done? It's too slow to do this, how nice it would be if there was a machine. Of course, this is only part of it, and anyone can come up with many ideas.
So what should we think about when we pioneer on bare metal? Maybe our general idea is: do a simple function first, do an important function first, finally debug this function today, and tomorrow you can do the next function, why is this not the result I imagined? It's really inexplicable! Wait a minute.
If you take a task, set up a test platform and start making a program, thinking about one function after another, and then intoxicate yourself with the joy of success, then doing this program is basically called having no thoughts. Thoughtful programming cannot pile up source code at once, because that will only make a bunch of blunt numbers timidly crowded together, regardless of whether they are redundant or not, whether there are contradictions or not. So before writing the source code, you have to think about how to write it. Many people may have thought about similar problems before writing, such as modularizing tasks and then organizing programs. However, such an idea is only a matter of tasks, not the idea of naked programming, which should affect the guiding ideology of source code organization in the process of organizing task modules and when writing bare programs, which directly determines the quality of source code.
A data structure, a module formation, a microcontroller instruction, a hard instruction operation mechanism, a mouth line driving mode, an interrupt sequence, a jump delay, a code position, a logical organization, a module (runtime state) and death (non-runtime state) relationship between modules, etc., are all components of the naked program idea.
This may seem trivial, but the bare program is inherently so, it is different from the host program and has a strong and complete operating system support. It is impossible to implant an operating system in a microcontroller, so it will change the taste, but don't let anyone jump out and say, so-and-so microcontroller has an operating system. The quality of the naked program may often not be felt in the application, maybe you can do it and he can achieve the function, but a good naked program has good scalability, maintainability, and the system has high stability and high performance.
In the pursuit of this high-grade technical realm, we must have good ideas to guide. Do you look a little confused? In general, it is to implant an excellent soul into your source code and make your source code have an excellent idea.
|
Posted on 11/25/2014 10:03:01 PM
|
|
|
Posted on 6/12/2018 4:20:49 PM