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
Posted By J.T. KimbellProgram Manager
When thinking about the newest features or the things that may excite you about the next Windows Embedded release, servicing may not be the first thing that comes to mind. However, as many of you know, servicing and managing your devices comprises a huge part of their lifecycle and cost. We realize this as well in the Windows Embedded team and strive to make the servicing and update experience as simple as possible for Windows Embedded Standard 8. In many ways, this means making the experience as close as possible to the Windows 8 servicing experience.
In Windows Embedded Standard 7, all updates to Windows were applicable to Windows Embedded, but only security updates appeared through Windows Update. Additionally, those security updates were packaged separately from the Windows security updates. As such, they would appear in the IT administrator’s consoles separately as “Security Update for Windows 7” and “Security Update for Windows Embedded Standard 7” even though they contained the same payload.
For Windows Embedded 8, all update types will be available through Windows Update (with the exception of service packs) and these will be packaged together with the updates release for Windows 8, meaning less clutter in the IT admin’s console. To learn more about the nine different update types, please see the appendix below.
Also, several changes have been made to Windows 8 that will also improve the Windows Update experience for Embedded customers. As described in this blog post on the Building Windows 8 blog, there will be less disruptive reboots due to Windows Updates, which is being achieved in a handful of ways:
Comments Products in Development
Posted By Phillip CaveSoftware Development Engineer
[UPDATE from J.T. (7/30/12) - Phil has now become a blogger on the site and I've moved this post to his page]
Last month Phil Cave provided us with an overview of Agile software development in Windows Embedded and set the table for some great follow-up posts. In this post Phil dives deeper into defining small customer based experiences. In my opinion, he did so masterfully and I hope you find it as insightful as I did.
The introduction to this series on “Embedded Agility” summarized the transition and ongoing transformation of Windows Embedded to a delivery model based in Lean thinking. That first post outlined 3 basic tenets:
This blog post begins a deeper dive into the topic of defining small experiences. This first principle has a profound implication on flipping our approach from technology layers to business value slices of functionality. Instead of creating a very large batch of user stories and treating them as if they are exactly the same, defining these customer experiences requires communicating in terms of the business and customer to define value as they would experience it; and then delivering those slices of business functionality incrementally.
Our business partners and customers focus on the experience of the device they are using. Yes, they expect a certain acceptable performance of the device as part of that experience and that performance is in relation to the experience of using features. The road to business agility begins with understanding what is of value and what is not. This includes the software features we deliver as well as the system in which we deliver those software features. Our customers understand this and communicate this way.
We deliver experiences. We deliver capabilities to fulfill experiences. Windows Embedded creates and delivers software that does both. The Auto team directly creates user experiences when delivering the Sync product to Ford. The Cassini and Compact teams create platforms upon which others may develop experiences. The creation of those platforms provides experiences (or ability to create experiences) to our partners who use the platforms.
Examine the picture below to see a visual representation of the experiences and capabilities of which I write. The Agile world of execution labels these experiences as “user stories”. The systems model on the left represents building out our software in one large batch of experiences. The systems model on the right represents building out our software by incrementally delivering smaller batches of experiences.
Comments Intelligent Systems
Just four years ago I got the chance to spend a summer as a Microsoft intern, which was an absolutely fantastic experience. This summer we have quite a few interns getting a similar experience on Windows Embedded. Jordan Goldberg’s post is the first in a series of blogs from those interns to let you learn more about their experiences, their projects for Windows Embedded, and Microsoft’s culture. We hope you enjoy reading about their experiences!
Hello World! My name is Jordan, and I am an intern here on the Windows Embedded team. Today I would like to share the experience I have had here at Microsoft and how I’ve been given the opportunity to make an impact with my work. To start, let me introduce myself. I grew up in the “Great White North” -- Canada, or more specifically, the town of Caledon which is slightly Northwest of Toronto. I am currently completing my undergraduate degree in Computer Science at the University of Guelph and my interests range from playing guitar to practicing parkour to developing mobile and web solutions. This summer I have had the extreme pleasure of moving to the West Coast to complete an internship with Microsoft! For the past 8 weeks I have been working on developing a Windows Debugger Extension for the new Unified Write Filters feature in Embedded Standard 8; but I will delve more into this experience later.
Life here at Microsoft has been nothing short of remarkable. In the short time that I have been here Microsoft has announced the innovative Xbox Smart Glass platform, unveiled the highly anticipated Windows Phone 8 and revealed the ultra-secret Microsoft Surface; I can proudly say that I am working for one of the most exciting tech companies in the world! On top of this, the Redmond campus is absolutely breathtaking. Being surrounded by snowcapped mountains, green vegetation and sprawling forests makes the commute to work each day a treat. And with a population of over 40,000 Microsofties, the campus feels more like a city than a corporate headquarters!
Comments Windows Embedded Standard
Posted By Garrett ClarkeSenior Business Development and Strategy Manager
As many of my colleagues have mentioned in their blogs over the past few months, we are seeing an increasing trend from autonomous devices toward ones that are truly connected and part of a much broader ecosystem. This shift in the embedded industry toward Intelligent Systems is further accelerated by the desire of enterprises to obtain a competitive advantage through increased knowledge about their customers and their business. It is truly an exciting time as the number of devices that are part of an Intelligent System is expected to nearly double by 2015 according to IDC. Clearly the application for Intelligent Systems spans many industries including Retail, Manufacturing, Auto, and Health. However, since I have spent the last 10 years (or so) working in healthcare, I wanted to share some of the thoughts I have on some usage scenarios of Intelligent Systems in health.
Enabling the Connection to the Patient at Home:The impact that Intelligent Systems have on the healthcare has many similarities to that of other industries (i.e. reuse of data, cost reduction, timely access to information….) but it also has some distinct advantages. Most importantly, improved outcomes for patients. Many device manufacturers are now making devices that patients can use at home that will automatically connect the patient back to the provider or caregiver through the cloud. This streamlined integration increases the frequency that a provider or caregiver receives critical health metrics (blood pressure, blood glucose levels, weight, etc.). These “Connected Health” scenarios allows for greater collaboration across the provider, patient, and caregiver potentially allowing action to be taken prior to an acute event occurring.