Posted By David CampbellProgram Manager
Doug Boling recently hosted one of his regular webcasts on Optimizing performance and power on Windows Embedded Compact 7 and has graciously provided me with a companion article. Thanks Doug! There’s more information later in the article about how you can sign up for these webcasts so please do join us for the monthly sessions.
Embedded hardware is slow. It’s designed that way. Unlike Personal Computers which are sold to customers who are dazzled by high gigahertz numbers and massive hard disks, embedded customers buy a widget that does something. If the widget does something well that’s all that matters, so the manufacturer of that widget is going to use the slowest (and often least expensive) hardware possible to implement that widget. This is one requirement that makes embedded software so challenging to write. Embedded software must have great performance so that the hardware can be as inexpensive as possible.
In this blog post, I will review some of the techniques for system design that can improve performance, and as a consequence, the power consumption of a system. I’ll also cover some lower level application driver characteristics that can lower power consumption directly.
Comments Windows Embedded Compact
Windows Embedded Standard 2011 provides a tool called Image Configuration Editor (ICE) to help developers configure the components to be installed on the run time image. The configuration is stored in XML file format and is called an answer file.
Before creating an answer file, you should gather the hardware configuration of the target device by running TAP.EXE. This will generate a PMQ file. For instructions on how to generate a PMQ file, please refer to the “How to Generate a .PMQ File Using Target Analyzer” section in ICE Help.
Let us go through how to create a simple answer file that represents the configuration to be installed on the run time image.
**Updated 3/26/09 with preface
[The following article is authored by one of the Windows Embedded MVPs (Most Valuable Professionals). Our MVPs have a heavy background in Embedded systems and are a great repository of information on Windows Embedded products. We’re providing this space on our team blog as a service to our readers by allowing MVPs to share some of their knowledge with the rest of the community.]
Embedded devices quite often have special footprint requirements that have direct effects on the way these devices can be managed. Small footprint, for example, may mean fewer management capabilities available on the device. This leads to different management scenarios.
* Updated Boot from USB section 10/5/09
With the next version of Windows Embedded Standard, we’ve focused heavily on making it as easy as possible to create the embedded operating system for your device.
As mentioned in a previous blog article, the Windows Embedded Standard 2011 “Quebec” toolset is broken up into two main components: Image Configuration Editor (ICE) and Image Builder Wizard (IBW). ICE is the equivalent of your Target Designer experience in Windows Embedded Standard 2009. IBW is a new development experience that is designed to be extremely simple. With IBW, you can quickly and easily create an embedded OS for your device. With ICE, the development experience is slightly more time consuming, but you have the full flexibility to customize the OS to your heart’s content.
Posted By J.T. Kimbell Program Manager
In June, we announced at Computex in Taiwan the release of the second Community Technology Preview (CTP) for Windows Embedded Standard 8. Building on that momentum, we’re excited to say the third CTP is available today, and David Wurster, a product manager on the Windows Embedded team, is here to tell us more about how you can get a download and try it out.
Today the Microsoft Windows Embedded team is excited to announce the availability of the third Windows Embedded Standard 8 community technology preview (CTP).
This release follows the Windows Embedded Standard 8 CTP 2 made available in June and delivers many quality improvements and several new capabilities – including:
The Windows Embedded Standard 8 CTP 3 marks another milestone on Windows Embedded Standard 8 roadmap, but your feedback is still needed to ensure that we’re delivering the best product that we possibly can. At Microsoft we are very excited about the possibilities Windows 8 technologies provide for intelligent systems and encourage our partners to download the CTP 3 today.
Comments Windows Embedded Standard