嵌入式應用的能源調試工具

　　隨著開發(fā)進程的推進，代碼變得更大，而能源效率優(yōu)化變得困難和耗時的任務。如果沒有適當?shù)墓ぞ?，識別錯誤，如可避免的等待周期可能被中斷服務程序，或周邊的誤區(qū)，變得越來越困難。如果這些“能量漏洞”沒有發(fā)現(xiàn)和開發(fā)階段解決，它來檢測他們的領域或老化試驗幾乎是不可能的。

　　有嵌入式系統(tǒng)應用中的節(jié)能和效率在開發(fā)商優(yōu)先考慮的越來越多。這些限制可以根據(jù)政府規(guī)定（如計量應用），要求增加電池的使用壽命，或僅僅是需要降低電費。在電池供電的系統(tǒng)，能源效率通常扮演最重要的角色。如果開發(fā)商是滿意的系統(tǒng)電池壽命，提高能源效率意味著他們可以切換到更小更便宜的電池，降低整體成本。也有情況下的使用壽命必須擴展到最大值；例如，在電池無法更換或更換涉及很高的成本。

　　To accommodate this trend， a growing number of “ultra-low-power” microcontrollers （MCUs） have become available. However， tools that provide developers with a detailed monitor of their systems‘ energy consumption have not accompanied the MCUs until recently. Having a low-power MCU by itself does not mean lower energy consumption. The trick is to optimize your software， not just in terms of functionality， but also with respect to energy efficiency. Having full control of the hardware surrounding the MCU and optimizing the overall software and peripheral usage are crucial factors for reducing system energy consumption. Software is not usually seen as an energy drain but every clock cycle consumes energy. Minimizing this is a key challenge in reducing overall system energy consumption.

　　Developers are now able to visualize the energy consumption of their systems and relate it to the software running on the microcontroller. Real-time information on current consumption is correlated with program counter sampling to provide advanced energy monitoring capabilities.

　　Energy friendly embedded systems development can be seen as a three stage cycle： hardware debugging， software functionality debugging， and software energy debugging.