Archive for the ‘embedded’ Category

Hearing no

Monday, October 4th, 2010

You’ve been working with a group of stakeholders to forge consensus on a project issue. Some want exactly what others don’t want, some refuse to reveal their private agendas, and some seem to change their goals almost at random. At times, you’ve felt that the group was close to agreement, only to be disrupted when someone on high changed the external constraints.

It’s been a little frustrating.

Work life sometimes delivers disappointments, often in the form of No. Some of us have difficulty hearing No or dealing with it once we do hear it. And, sometimes, No arrives so frequently that we exhaust our ability to cope with it.

Click here to continue reading this article at Sticky Minds.

Smart grid: What’s here, what’s needed, and what you should know now

Monday, September 27th, 2010

Let’s define the smart grid as the infrastructure and technologies that enable integration of the consumer and distributed resources (generation, renewables, storage, demand response, load control) with the operation of the entire grid and electricity markets, while also improving the reliability and Security of the overall electric service. The biggest gap is the lack of inexpensive, standardized, and ubiquitous communications that deliver bandwidth, extreme reliability, and security for both control and management applications as well as basic information management and sharing applications. This broadband communications infrastructure does not need to be one technology, but it needs to extend all the way from central control systems to end-user devices.

Click here to read this whole article at Embedded Computing Design.

Embedding an IPMI platform management subsystem to monitor server system health

Thursday, September 16th, 2010

Primarily utilized in enterprise systems, platform management provides the ability to monitor and report on the health of the system hardware via isolated  hardware/software that does not rely on the operational state of the system’s hardware or software.
The platform management hardware typically resides on the same board as the system hardware; however, because it is isolated it can remain functional even if the system hardware is non-operational. The platform management hardware is usually powered by a separate power supply.
Servers make up the vast majority of these enterprise systems and they are the backbone of the Internet. There are thousands upon thousands of these servers in server farms all over the world. When a server fails or is about to fail, it is important for the technical caretakers to find, fix, or replace the system quickly.

Click here to continue reading this article at EE Times

The Impact of Automation on Development

Thursday, September 2nd, 2010

It seems obvious that automation will affect the test organization. Less obvious—but no less real—is that it will also affect the development organization. In fact, when you choose to automate the testing for an application, your relationship with development changes completely.

Think about it. Manual testers only have to be able to interact with the application using the screen, keyboard, and mouse or other device. Automated test tools, on the other hand, have to interact with the software at a deeper level, thus exposing the inner workings of the code and perhaps uncovering problems that prevent or complicate automation. If you’re not careful, developers might think you have suddenly transformed into an interfering busybody who is sticking your nose into their business.

This shift in your relationship with development can be handled in a bad way or a good way.

Click here to read this article at Sticky Minds.

Protect and control software stored in flash memory

Tuesday, August 31st, 2010

It’s been said for every measure, there’s a countermeasure, and that’s also true for securing code in embedded systems. Sometimes a small device can be just the countermeasure needed to thwart cloning of flash contents.

Many systems use external standard flash memory chip(s) to store the operating program for processors that do not include embedded nonvolatile program storage. This is great because it allows easy flash memory expansion and software modification, perhaps in the manufacturing line as a customer download or during a maintenance operation. The downside is that the OEM loses control over the contents of the flash, potentially allowing unauthorized copies or modification.

Click here to continue reading this article at Embedded Computing Design.

The 8 commandments for choosing a unit testing solution

Thursday, August 26th, 2010

Teams who perform unit testing on a regular basis are perceived to be more reliable, professional and advanced. But what do you need to consider before choosing a unit testing solution?

We have developed the ‘8 commandments’ below as a guide for ensuring you select a unit testing solution that is right for your development.

1. Thou shalt not waste time on the learning curve

When choosing a unit testing solution, you will want one that will require minimal time for implementation. It may be worthwhile to time a new developer within your team with the framework to get an accurate idea of how long it takes to get started. For example – how long will it take them to write the first three tests for some class in your system? Is the API clear and simple? Is there a single point of entry in the API? Is there clear guidance on what to do at each step of the way? How often, if at all, do you need to check the docs and tutorials? How easy is it to look for the next step when you’re not sure what to do? Some tools offer guidance within the IDE, while some provide extensive help. Some don’t do either.

Click here to continue reading this article at EE Times Embedded.

Building Embedded Linux Systems Using System Builder

Thursday, July 29th, 2010

Linux has been deployed as the defacto standard for a wide variety of embedded applications across virtually every market segment. Developers today are facing huge development challenges brought on by insanely short development cycles and ever-increasing hardware and software complexity driven by customer demand and competitive pressures.

One of the distinguishing characteristics of embedded systems is that each is a unique combination of hardware and software components.

Click here to read this article at Embedded Computing Design.

Good Idea! Now What?

Wednesday, July 14th, 2010

idea.jpgA good idea is a valuable asset, and a lot of good ideas can be like a treasure trove. But what do you do with those ideas?  Many ideas wither, not because they are bad ideas, but because of clumsy presentation. Most nascent ideas stand a better chance if you remember these four things:

1. It’s not about you.
Most of the time, people pursue a new idea because they can see how it will help them. Don’t just tell them why you think your idea is a good one. See the world from their point of view, and frame the idea in terms of what matters to them. If your manager cares only about cost, then talking about quality, speed, reuse, or elegance won’t convince him to try your idea. Connect your idea with what’s important to the people you are hoping to influence.

2. It is about who you know.
Bringing your ideas to fruition is a social process. You will need the aid and interest of others to make your idea reality.

Click here to continue reading this article at Sticky Minds.

Embedded software-driven hardware verification

Thursday, July 1st, 2010

chip.jpgBy best estimates, the software development effort behind 90 nm chip designs has already surpassed the hardware development effort. The projection for 2011 is that less than 40 percent of the overall chip development cost will be spent on hardware. Software now dominates project cycles and determines when a chip can get into volume production. As a result, the importance of software verification has increased, and software has taken on an integral role in the hardware verification process.

Click here to continue reading this article at Embedded Computing Design.

Debug will get your attention, sooner or later

Tuesday, June 29th, 2010

idea.jpgAsk an engineer what he is doing and there is a good chance his answer will be, “I am debugging.” Day in and day out, project after project, engineers debug — it’s part of being an engineer. Sometimes, it’s quick and easy, but sometimes it’s hard, not obvious, time consuming, and unpredictable. Everyone knows that debugging is a dreaded but necessary part of the design and verification process.
One alarming trend that is not necessary is the increasing proportion that debugging consumes in the design cycle. Within functional verification, it is the single largest component at approximately 60 percent and is projected to grow even larger. Broadly speaking, the reason for this trend is that traditional debug practices are not adequate for today’s problems.
Sooner or later, debug will get your attention.

Click here to continue reading this article at Embedded.com

Live Chat

Join the Live Chat