Wind River Blog Network

Introducing Performance Studio

By Emeka Nwafor

What is Performance Studio? Is it:

1. Some kind of hair product

2. A new "clinic" for MLB players

3. Full name: : Wind River Linux Performance Studio for Intel® Architecture; a new add-on product for Wind River Linux that helps you get the most performance out of your embedded Linux device software running on Intel hardware 

If you correctly answered "3", give yourself a round of applause.

Our portfolio of development solutions have long addressed a broad set of embedded device development concerns in the areas of system definition, bring-up, software construction, integration & test, and maintaining and retro-fitting embedded device software and hardware. Now, with the introduction of Performance Studio, we not only have the broad development solutions portfolio but also further extend it with capabilities that enable us to go deeper into the platform and obtain the best performance out of embedded Linux software running on Intel® Core™, Xeon™, and Atom™ processors. 

Continue reading >>

 

Feeling the need for speed and making it happen

By Mark Guinther

“I feel the need…The need for speed!!”  Quoting old movies is where my similarities to Tom Cruise end, but it is a relevant line for today’s networking equipment.  Faster applications is one of the last steps in getting faster results to subscribers, resulting in happy subscribers which means happy service providers, happy service providers mean happy equipment providers, and… well, you get the point: Everybody is happier when their network runs faster. However, it’s getting tougher given the ever-increasing flood of data on today’s networks.    

Bigger, faster pipes are a start, but you can have the best infrastructure plumbing in the world and still have poor performance if your system and applications are a bottleneck. 

Continue reading >>

 

Exciting Times - Virtually!

By Chris Ault

It's an exciting time for embedded virtualization at Wind River!  We were recently named the embedded virtualization market leader by VDC Research Group.  In VDC’s 2011 ‘Virtualization for Mobile and Embedded Systems’ report, Wind River achieved the highest share of the market in 2010 with greater than 30 percent of total market revenue.

In addition to this significant recognition, today we announced updates to our embedded virtualization offering. We released updates to our guest operating systems – VxWorks and Wind River Linux, as well as updates to Wind River Hypervisor and Wind River Workbench tools.

Continue reading >>

Wind River Turns 30: Looking Back and Moving Forward

By Tomas Evensen 

2011 marks Wind River’s 30th anniversary. The big 3-0…it’s a major landmark moment in anyone’s book. This year, we’ll be taking time to honor this milestone with a retrospective of Wind River’s history and also a series of employee stories.  In my many years with the company, Wind River always impressed on me the concept of  being bigger than just a single product or technology. There is an underlying spirit within our teams that constantly reaches for more, for some greater innovation. While many customers know Wind River for the VxWorks real-time operating system, it was always part of the vision to provide more value. In the early days, this entailed providing a TCP/IP stack and GDB for debugging. Later, additional value came from strong IDE support through Tornado and Workbench. Lately, it has been by providing a choice of operating systems, real-time or open source/Linux. 

A standout example that exemplified the vision of providing a more complete solution was when we embarked on creating a truly embedded hypervisor. In 2004, it had already become clear to us that virtualization would play an important role in embedded designs at some point in the future. In early 2005, Paul Borman who worked for me in the CTO Office created a very impressive prototype, called eCPU, that ran VxWorks and Linux on a single CPU and we learned a lot from that effort. When Johan Fornaeus came on board in 2006 through an acquisition (he was co-founder of Interpeak and before that, one of the co-designers of the Enea/OSE operating system), I had him leading a small nimble task force team to develop a hypervisor really suited for the embedded space. I felt we made a real breakthrough. This was not a repackaged operating system pretending to be something it was not designed for, but instead a truly unique approach to virtualization and separation. Over the next couple years, this small team created a scalable product with an extremely tight footprint, incredible performance, while at the same time being full featured for the common architectures such as Intel, Power, ARM and MIPS.

Back in those days, it was not clear to us when and how important multi-OS systems would be in the future, but today it is hard to imagine how to deal with these new complex systems without a hypervisor for embedded virtualization. Looking at my team’s achievement now, I still marvel at how the Wind River Hypervisor brings together multi-core and our various operating systems. Why choose between operating systems with different characteristics when you can mix them in one system? Throw in a networking stack optimized for multi-core and tools that can debug and find performance bottlenecks and you get a very capable foundation on which our customers can innovate.

By constantly looking to the future, Wind River continues to evolve and further build on its expertise. The ongoing push to innovate may have created interesting and complex challenges along the way. However, it has also resulted in celebrations and breakthroughs, and it’s undoubtedly a big reason why so many of us continue to stay on the ride. 

 

Scalability: the key to product line success

By Bill Graham

An important requirement for an RTOS such as VxWorks is scalability. What this really means is being usable in many different types of devices, from small memory constrained, low power devices (possibly battery powered, hand held, mobile) to large scale systems, multiple nodes networked together, possibly using multicore in a multi-OS environment. Scaling down is equally important as scaling up. As my colleague Felix Baum had recently posted, flexibility is also critically important part of the equation, an RTOS must be configurable as needed by the developer and run on the hardware platforms they choose, and make the most of the hardware capabilities.

Why not just buy a specific RTOS for each project? This isn't really a viable option anymore. Our customers are looking for a tools and run-time platform they can rely on for a product line rather than an individual product. In the end this turns out the be the best solution both in terms of costs but also in reducing risk  and meeting difficult time-to-market targets. A common platform means reuse of code, expertise, tools and most importantly, "one neck to wring", one vendor and one point of contact to solve your problems.

Continue Reading >>

Autonomy and Robotic Advancement

By Mike Deliman

A few months ago at the Robotics Virtual Trade Show, in my presentation I spoke about the evolution of robotic systems.  One thing I predicted was as time goes on, robots will become more independent and autonomous, performing more of the work humans and mainframe-style systems have traditionally performed.  

Among the robots I talked about were robots similar to NASA's 
Stardust Spacecraft  Stardust is currently on course for a Valentine's Day rendezvous with Comet Temple-1.  Stardust includes a package that performs autonomous navigation, d to help keep the craft on it's flight path with reduced intrusion from ground-based systems.  Since Stardust is so far out from earth, there is significant delay in round-trip communications.  Stardust is able to detect problems in trajectory and perform course correction maneuvers on its own.

Last week, Northrop Grumman had  first-flight for an evolution in Un-maned Aerial Vehicles.  The 
X47B UCAS   is an autonomous unmanned flight system.  It is not a wireless-joystick system.  It flies itself, taking off, figuring a course to it's way points, landing.  Without human intervention.

Continue Reading >>

 

Safety-Critical Systems Symposium 2011

By Paul Parkinson

I'm looking forward to the 19th annual Safety-Critical Systems Symposium which is being held in held in the UK next week.

The conference programme covers a range of subjects including safety cases, testing of safety-critical systems, updates to safety standards, and technologies. On the Thursday afternoon, I will be presenting a paper Safety, Security and Multicore.

Wind River will be participating in the exhibition which is being held on the Wednesday, and we will have a live demo of VxWorks MILS 2.0 running on the stand. So why not pop by to discuss your safety & security requirements?

 

Embedded Virtualization Opens New Possibilities

By Mark Hermeling

One of the things that stands out in many customer visits that I do is that embedded virtualization often enables possibilities that the customer never thought possible. This of course is a good thing, it may enable them to put a new product to market that the customer had never thought of. In a few cases I have seen customers use virtualization to shift their business models from shipping custom hardware to shipping software only using COTS boards. Virtualization in this case is used to provide the customization that they formerly needed hardware for.

I went on a customer call earlier this year to a customer that was looking to go to multi-core. The customer was building a networking product and was using VxWorks on a single core Intel processor and wanted the additional processing power that a dual or quad-core could provide. They wanted to go to multi-core and came to Wind River to see what their options were. 

Continue Reading >>

Virtualization on Handsets or not?

By Mark Hermeling

Here is an interesting article, continuing a discussion thats has been going on for a long time on mobile virtualization. It argues the case that a single mobile phone can run multiple operating systems using virtualization. A bit of googling will show that this is indeed already the case. However, there is a big caveat typically that you do not see exposed. 

Mobile phones have two big constraints: processing power and battery power. Typically one operating systems is the 'phone operating system' and the other OS is more general purpose. With 'phone OS' I mean that the OS has to handle a lot of the time critical tasks, sometimes even to the level of passing data off to/from the signal processing side for communication with the antenna and the wireless network.

The signal processing side is very time sensitive and hence it is important that the time constraints are met and data is delivered/picked up on the right time. This makes it that typically the virtualization layer will have to be aware of this and it makes the solution not a general virtualization solution, but a highly device customized solution.

Continue Reading >>

Migrating to Multi-core using Embedded Virtualization

By Mark Hermeling

So, let's assume that you are currently on a single-core board and you would like to explore the possibilities of delivering a next generation device using multi-core technologies. There are a lot of different ways to approach this. The most elaborate involve doing an architecture study into ways in which you could evolve your current device architecture. This study would need to be approached from both a technical, as well as a business level.

The funny thing with software is that 'virtually' anything is possible, but the trick is to find approaches that are not only technically possible, but that provide business benefits, usually in a short time-frame. Part of the equation is the amount of work required to build this next generation of device.

Continue Reading >>

Wind River Network Acceleration Platform Wins Best Software Award

By Jessica Schieve

Last night I had the pleasure of attending the 2010 ATCA Summit Best of Show Awards ceremony where Wind River was presented the Best Software award for its Wind River Network Acceleration Platform.  
This is a major accomplishment for a industry solution that was launched less than a year ago. The panel of judges included industry editors as well as networking and telecom ecosystem peers.

So why would Wind River Network Acceleration Platform win top honors?  Let's consider the following. As I sat in a presentation about the future of 40G applications, one speaker from a prominent COTS board company discussed six different approaches to achieving the capacity and throughput needed to make 40G a reality.

Continue reading >>

Embedded Virtualization in Gaming

By Mark Hermeling

A few weeks ago I found myself in the Hard Rock Hotel in Las Vegas. My reason for being there was a seminar that Wind River was organizing together with Intel and AVNET specifically focussed on companies that build gaming. The main topics were graphics, manageability and of course, virtualization.

I am always eager to fold real-life examples into my presentations, hence I decided to try my luck at some of the slot machines in the Hard Rock Hotel under the disguise of 'domain study'. And I have to say, the state of slot machines has progressed significantly since the last time that I was in Vegas many years ago. The top of the line machines had multiple 30" inch displays with either static or moving imagery, they had player tracking, surround sound, some of them even had imagery over the rolls themselves.

Continue Reading >>

IMA on Simics: An Interview with Tennessee Carmel-Veilleux

By Jakob Engblom

After Summer, I have been in contact with Tennessee Carmel-Veilleux at the École de technologie supérieure in Quebec, who has been doing some really cool work with Simics.  Tennessee has learnt Simics very quickly, and has been very clever in how to apply Simics to the research problems he has encountered. In this interview, he tells us some more about his research and use of Simics. I prefix my comments with "JE", and his with "TCV".

Continue Reading >>

Embedded Virtualization and Multi-Core

By Mark Hermeling

VDC has released a recent report showing that multi-core is making fast inroads in embedded systems and we are seeing that at Wind River as well. There are exciting new possibilities with these chips, we have never had this much processing power in such small packages.

Take for example Freescale's new P4080 chip, 8 cores, 2 memory busses and a wealth of peripherals that are designed for multicore usage (such as the data path acceleration architecture (DPAA)). There are many things to consider with this new chip, I have blogged before about the many primary multi-core configurations available from SMP to uAMP, to sAMP to core virtualized. You have to consider partitioning, or virtualizing cores, memory and devices.

Continue Reading >>

Intuitive & Efficient Debug of Multi-core Systems

By Brian Finkel

I reflect on a recent visit with my 84-year old Aunt Honey. As you might expect, she is not an avid cell phone user. She wanted help entering contacts into her phone. She has a basic phone so we had to enter text using the “9-up” keypad. Her objective is to make phone calls by selecting someone’s name instead of typing the telephone number.   

The event had me thinking about the way we used to make telephone calls – using an address book or a phone list and then typing in the number. In my youth, things weren’t so bad – everyone lived in the same town – with the same area code and only a few prefixes. For each friend you only had to remember the 4 digits and perhaps which prefix to use. Fast forward a few years and with the advent of cell phones, IP telephony, new area codes, and geographically-dispersed friends and family – you now need to remember 10 digits. 10 digits is beyond most people’s working memory (which is typically 7 digits). Address books and phone lists were required. 

Continue Reading >>

Devices! Devices! Devices!

By Mark Hermeling

That is what embedded systems is all about: handling devices. An embedded software system has input devices and output devices and some amount of software running on operating systems, running on hardware that turn input into output. The trick is to handle the input in a fast an deterministic way and generate output in a fast and deterministic way. Determinism is important all the way through the system, from the device, to the hardware, to the operating system to the software running on the operating system.

Continue Reading >>

Variable and Deterministic

By Jakob Engblom

A virtual platform like Wind River Simics is generally designed to be deterministic. Determinism brings a host of benefits to users (repeatability of bugs, reverse execution, bug transportation, etc.), but is also easily misunderstood. Quite often, users fear that they will lose an important "feature" of a physical machine - its built-in variation across runs of the same software. If the virtual platform is deterministic, surely it will not expose all the different ways a program can run that you get on a random physical machine? Yes it can.

There is a huge difference between the repeatable determinism of a virtual machine and completely invariant, predictable, predetermined behavior.

Continue Reading >>

Test Automation Meets Simulation

By Paul Henderson

I'm seeing increasing interest from many companies in using simulation environments with test automation systems to accelerate the testing process. Specifically, putting Wind River Test Management together with Wind River Simics is getting creative juices flowing in industry thought leaders.

Why? Well, development teams have started to realize the benefits of simulation systems for speeding and validating system and software design, and for accelerating software development and debug in advance of hardware availabilty. And even when hardware is available, systems like Simics provide tremendous access and control to speed analysis and diagnsotics.

Continue Reading >>

Transporting Bugs with Checkpoints

By Jakob Engblom

I have a paper about "Transporting Bugs with Checkpoints" to be presented at the S4D (System, Software, SoC and Silicon Debug) conference in Southampton, UK, on September 15 and 16, 2010. The core concept presented is to leverage Wind River Simics checkpointing to capture and move a bug from the bug reporter to the responsible developer. It is a fairly simple idea, but getting it to work efficiently does require that some things are done right.

Continue Reading >>

Interview with Girish Venkatasubramanian

By Jakob Engblom

After my blog post on Academic Simics earlier this Summer, I got a very nice reply from Girish Venkatasubramanian of UFL. Turned out that he and his group was doing some really interesting and exciting stuff with Simics, researching into Hypervisor architectures and hardware support. Having been a PhD student myself, I can certainly appreciate the excitement and fun of working in that field. We ended up doing a virtual interview, which I am happy to present here.

Continue Reading >>

Wind River and IBM Attack Software Quality

By Paul Henderson

As I've mentioned before, we've been working with IBM Rational for some time around quality management automation. Both companies see the skyrocketing software content and architectural complexity in the embedded device market as creating a tipping point where companies will not be able to continue with business as usual.

Product development teams will need to take a more managed and automated approach to quality that spans across the lifecycle and access into the devices under test. This is particularly true in markets that require strict adherance to standards and compliance regulations.

We put together a joint whitepaper on this subject downloadable from here. And we are also having a joint web seminar next week on Tuesday Aug 31 at 2pm EDT. You can register for this event here.

Continue Reading >>

Type 1 versus Type 2 Hypervisors

By Mark Hermeling

I have always found the difference between Type 1 vs Type 2 hypervisors rather uninteresting. In short, a type-1 hypervisor is a hypervisor that has direct access to the hardware, where a type-2 hypervisor executes inside an operating system. Most hypervisors are type-1 hypervisors, including IT hypervisors such as VMWare, Xen, KVM and such. Type-2 hypervisors are applications like VMWare Workstation (or Fusion), Parallels, .... The distinction between type-1 versus type-2 is really not as useful as most people think. There is a good blog article by Anthony Liguori that describes this as well, complete with references, the article is a bit old, but still correct.

Continue Reading >>

VxWorks in Education: University of São Paulo, Brazil - Part 3

By Bill Graham

In the third and final part of my interview with Professor Glauco Caurin we discuss multicore and virtualization and why they are working with us on their research projects.

Q: Are your students learning about multi-core processors  and programming? What about multi-OS systems including virtualization, i.e.  systems that have more than one OS on a single processor?

Continue Reading >>

Freescale on Multi-core and Virtualization

By Mark Hermeling

Two good blog posts from some of my colleagues at Freescale. One on Heading Into Hyperspace: Hypervisor and Multi-core design by Jim Trudeau and one by Rob Oshana on the Top 3 Keys to Multi-core software development. Jim talks about the multi-core aspects mostly from Freescale's P4080 perspective, an elegant, powerful and very popular processor in the networking space. The P4080 has not only many processors, it is truly designed for multicore with multiple peripherals (multiple PCI hosts) and multiple memory controllers for example to reduce contention.

Continue Reading >>

Primary Virtualization Use Case

By Mark Hermeling

This topic invariably comes up when talking to customers, unfortunately, there is not just one, but several primary use cases. There are multiple ways to look into the various use cases. The one I like best is to look at generic drivers. An alternative is to look at actual usages in the various industries.

Continue Reading >>

It’s Time for Testers to Step Up

By Paul Henderson

RTC Magazine recently published an article that I wrote called "Time to Rethink Software Testing for Embedded Devices". In it I describe some of the new techniques that are possible, and I believe necessary, to delivery high quality device software for embedded devices.

• When staying 'positive' doesn't pay
• Getting negative with white box testing
• Focusing on the 'deltas' with change-based test automation

Continue Reading >>

Test Driven Development Meets Continuous Integration

By Paul Henderson

In my last posting I mentioned I'd be running a webinar with James Grenning on Agile testing. James is a recognized expert and frequent speaker on the topic of software development and one of the original authors of the Manifesto for Agile Software Development.

We talked about the case for agility where today's embedded software projects are inevitably faced with changing requirements and market conditions that cause unplanned, mid-course corrections. The result is what went in is often not what was expected to come out. Testing folks are the tail trying to wag the dog as they try to test in quality at the end of the project.

Continue Reading >>

Industry Investing in Better Device Runtime Visibility During Testing

By Paul Henderson

Here’s the final installment in my series about our embedded device software industry testing survey conducted in April-May 2010 with almost 900 respondents (see previous blog postings).  If you’d like a copy of the full report in pdf, please drop me an email at paul.henderson@windriver.com and I will send it to you.

In this section of the survey we asked participants about what test tools they use today and where they are investing in test automation. Given the high cost of product failure, accelerating complexity and reduced schedules the industry is turning to more test automation in 2010 to help address these problems. The top investment are moving to new tools that can help test teams and their management better understand how well they are testing, better focus their efforts on the areas needing testing, and reduce cycle time through more automation.

Continue Reading >>

When it comes to multi-core, it takes a village

By Jessica Schieve

Telecom and Network equipment providers are facing huge challenges to build and deploy products that can meet the growing performance and capacity demands while also delivering the service levels customers have come to expect.  In the rapidly evolving wireless and wireline broadband markets, multi-core technologies have become a tremendous force that is impacting the entire value chain of industry suppliers (the village) and how it is responds to meet these challenges.

Wind River and LSI’s village just got bigger, stronger, and smarter.  Today, Wind River and LSI announced a long-term strategic collaboration to optimize and tightly integrate their multi-core hardware and software portfolios.  LSI’s Axxia Communication Processors will be integrated with Wind River’s industry leading Linux and VxWorks platforms and development tools. Now, equipment providers can leverage this collaboration effort as a powerful advantage to build faster, more intelligent, and highly competitive network products.

Continue Reading >>

The High Cost of Poor Quality – Brand, Market, Budget

By Paul Henderson

I’m continuing my series on our embedded device industry software testing survey conducted in April-May 2010 with almost 900 respondents (see previous blog posting).  If you’d like a copy of the full report in pdf, please drop me an email at paul.henderson@windriver.com and I will send it to you.

In this section of the survey we asked participants about how they measure the high cost of poor quality. Respondents told us that the true cost of poor quality is much higher than program budget. The majority of respondents showed that the true cost of poor quality is measure by damage to company brand and lost revenue due to missed market windows.

Continue Reading >>