Why Windows Embedded CE Shared Source?

By Kevin Ebi
For businesses that develop, manufacture, and distribute embedded devices, protecting their design and Intellectual Property (IP), as well as getting to market quickly is critical to long-term success. Yet, for the developers of embedded devices, access to source code may dramatically speed development, reduce debugging time, and assist them in supporting devices remotely. Is it possible to develop a device that meets the business needs for IP protection and gain the development benefits of "shared source code"? Yes, with the Microsoft® and Windows® CE Shared Source programs.

Shared Source is a Microsoft licensing framework that is designed to enable increased customer and developer community access to Microsoft source code, while preserving the intellectual property protections that are essential for a healthy software business ecosystem. Shared Source is a Microsoft-wide philosophy that covers a variety of Microsoft technologies and licensing programs that can be individually tailored to the diverse needs of customers and developers who require access to source code.

The Windows CE Shared Source Licensing Program provides many of the core elements of Windows CE, including the Kernel Library, File System, Device Manager and Storage Manager. Source code is also available for a number of additional Windows CE features, including HTTP Web server, Explorer Shell, Windows Sockets Interface, SOAP and uPNP implementations, Microsoft Message Queuing, Bluetooth and Point-to-Point Protocol.

"Using the shared source in Windows CE can greatly reduce development time, as well as improve customer satisfaction," said Nic Sagez, Microsoft Windows Embedded product manager. "Most developers use shared source code to troubleshoot projects and debug code quickly. Whether it is during development, or providing remote support to a customer, having the ability to look 'under the hood' to pinpoint problems can save hundreds of hours of effort." Developers can see exactly how Windows CE works, how an API works, and how certain operations are conducted. This allows them to build better devices and applications because they can learn how to best optimize them.

Some developers use the code to customize Windows CE, tailoring its real-time operating system capabilities to the needs of a particular device. An example where shared source code played a significant part in embedded device development was in allowing the Greer Company to customize Windows CE for a heavy construction environment; where one wrong or late calculation might result in serious damage or injury.

Greer makes electronic devices that help construction firms safely use cranes to their fullest potential. Managing a 90-ton crane is critical work and requires the device to constantly keep track of the crane's position and a host of other variables, including load weight, boom angle and even wind speed. With the source code in hand, Applied Data Systems (ADS), a Microsoft Gold Level Systems Integrator, adjusted the Windows CE thread prioritization to handle critical real-time input/output device drivers.

"The ability to modify core elements of the Windows CE operating system was essential to our goal of ensuring the highest level of safety for our clients," said Simon Worboys, Engineering Manager at Greer. "Our customers are able to do more than they ever thought possible, giving us a strong competitive advantage and sharp increase in sales."

"With embedded devices, there is a lot of variety hardware and capabilities," said Sagez. “We allow developers to adapt the code to make it run better on their devices."

Zoe Medical, which develops health monitoring equipment, and its systems integration partner, ADS, used Windows CE source code to extend the operating system to meet its unique needs. For years, Zoe used MS-DOS to collect data from sensors and instruments. ADS then used shared source to extend the Windows CE API to include those hardware extensions, allowing Zoe to covert its MS-DOS applications into Windows CE applications in just a few weeks.

"With just two developers, Zoe got both a hospital and a home device to market in about 12 months, including regulatory clearances," says Jim Chickering, Clinical Applications Manager, Zoe Medical Development. "Windows CE and Microsoft tools were a big part of that achievement."

With the Windows CE Shared Source Program, Microsoft provides more advanced Windows CE code—including the Graphic Windowing and Events Subsystem, TCP/IP and IPv6Networking and additional file system and device drivers—to Windows Embedded Premier Joint Development Partners, Windows Embedded Silicon Vendor Partners, Windows Embedded Partner Gold-Level Systems Integrators, and Microsoft's Most Valuable Professionals. OEMs can use the code to customize critical aspects of the operating system.

Shared Source appears similar to open source, but there are some key differences. Unlike open source, changes you make to the Windows CE source code are yours; you do not have to share them with the open source community or Microsoft. This attribute allows you to protect your valuable work and maintain marketplace advantage by eliminating the risk a competitor will be able to replicate your work.

Whether you just need some extra insight into the inner workings of Windows CE to help debug your project, or need to quickly customize the operating system to meet the needs of your device or a demanding environment, shared source for Windows CE gives you the resources you need to innovate and be successful.