Software Engineers [hardware] the clock

Software engineers to write programs do not think about the clock, except when it comes to performance requirements, will take a look. Hardware engineers are not, they are very demanding of time, the MCU clock frequency, is an important indicator of their concerns, 4M, 8M, 12M, 48M , 72M, 200M, 400M and so on, the higher the clock frequency, which means SCM system the faster data processing speed, however, the price will be higher in the hardware unit of time, therefore, need to be based on actual demand, for example, just do a timer, there is no need to get hold of 400M frequency SCM, and too wasteful.
To get software engineers to understand the clock, really it is not a simple matter. The reason is that software developers do not need to know the clock, they are commonly used is the timing that is sleep, but also a good package of high-level language, it seems that software engineers and hardware engineers than it is like a dandy, like a dervish, this is just an analogy and there is no implication. I hope you do not suspicious. So, software engineers in the entry hardware when needed before to get rid of "wasteful" habits, especially in-depth understanding of the clock, because it is everywhere.

Guess you like

Origin blog.csdn.net/wwwmagic/article/details/91372400