Windows Embedded Compact 2013 differentiates itself from other operating systems by providing a real-time, small-footprint operating system that can be customized to meet the targeted requirements of a specialized device on multiple chipset options, including both x86 and ARM. With an emphasis on “non-PC” solutions, Windows Embedded Compact is not trying to create multi-purpose desktop, but instead focuses on devices such as industrial controllers, medical imaging units, printers, digital signs, and retail scanners, to name a few. The specific characteristics of a device, like a small touchscreen or no screen at all (headless), plus its single-purpose functionality, make it a “specialized device.” As you can imagine, there are thousands of possibilities and you probably interact with these specialized devices every day without realizing it. When you want to design a device to serve a specific purpose and build it to meet a cost objective, Windows Embedded Compact is a great place to start.
Minimally, as a 32-bit operating system, Windows Embedded Compact requires a 32-bit CPU with a memory management unit. Along with supporting multiple architectures, the latest versions support symmetric multiprocessors, allowing developers to control which processor does the work or let the operating system balance the workload across multiple cores.
OS advantages
Embedded device manufacturers can and do take advantage of the logical separation of operating system design and the hardware. Developers in charge of the software features of their design can start their operating system and application prototyping on a Virtual PC-based platform while hardware-level board-support package (BSP) development is done in tandem (see Fig. 1 ). The modular design of the OS is uniquely geared so that designers can select only the components needed for their targeted scenario and it easily allows for the integration of third-party or custom features as well. Along with access to shared sources, Windows Embedded Compact gives all of the benefits of a Win32 API, coupled with the freedom to make the OS have only the features that are absolutely required.
Fig. 1: Developers in charge of the software features of their design can start their operating system and application prototyping on a Virtual PC-based platform while hardware-level board-support package development is done in tandem.
Windows Embedded Compact development is done using tools hosted in Visual Studio. This allows embedded developers to use the latest in Microsoft developer tools when creating their platform. The Windows Embedded Compact OS design tool, Platform Builder, provides access to a catalog of features and the ability select only those software components that are absolutely necessary for the targeted solution. Application Builder (formerly Visual Studio for Devices) allows application developers to create rich, targeted device applications without requiring the full platform development toolset. Not only is Win-32 available in Windows Embedded Compact, but ATL, MFC, DirectDraw, OpenGL, and XAML are also available if the designer includes the required components.
A “compact” version of the .NET Framework is selectable in the Windows Embedded Compact catalog to support Visual Basic and C# development for devices. The Microsoft .NET Compact Framework enables the device to host managed applications and use Web services. It includes an optimized common language runtime (CLR) and a subset of the .NET Framework class library that supports features such as Windows Communication Foundation (WCF) and Windows Forms. It also contains classes that are designed exclusively for the .NET Compact Framework.
When and why would I use Windows Embedded Compact?
Embedded operating systems, unlike their desktop counterparts, usually bundle the operating system and the required application together into a single executable image for purpose-driven devices. Using less space and only including required software allows Windows Embedded Compact to run on small-footprint devices needing flexible hardware and hard, real-time support. In short, you would use Windows Embedded Compact to create lower cost, purpose-driven devices where you need the reliability of a trusted Microsoft platform with support for up to 15 years.
A fully featured image for Windows Embedded Compact is about 45 Mbytes, but the size will vary based on what you include. It is recommended that a designer download the Compact 2013 kit (it is free at www.Windowsembedded.com/Compact) and try it out using the Virtual PC.
Microsoft recently posted a blog that discusses real-time in some detail and has links to the real-time studies done on Compact 7 (http://blogs.msdn.com/b/windows-embedded/archive/2013/07/17/the-hard-and-soft-facts-behind-real-time.aspx). The blog, in general, has a number of interesting postings.
Windows Embedded Compact offers encryption and networking security options and Windows CE supports creating a trusted app execution environment using certs etc. See http://msdn.microsoft.com/en-us/library/ee498894.aspx. Downloads of all Windows Embedded offerings are available at www.microsoft.com/windowsembedded/en-us/downloads.aspx.
Advertisement
Learn more about Microsoft
