HOME  |  NEWS  |  BLOGS  |  MESSAGES  |  FEATURES  |  VIDEOS  |  WEBINARS  |  INDUSTRIES  |  FOCUS ON FUNDAMENTALS
  |  REGISTER  |  LOGIN  |  HELP
Blogs
Electronic News & Comment

9 Things Engineers Need to Know About Embedded Development

NO RATINGS
1 saves
< Previous Page 2 / 5 Next >
View Comments: Threaded|Newest First|Oldest First
Beth Stackpole
User Rank
Blogger
Embedded development reality check
Beth Stackpole   7/24/2012 8:01:13 AM
NO RATINGS
Great job, Chuck, highlighting the common misperceptions and challenges associated with embedded development. The whole notion that the development effort is predicated more around software design, not hardware design, is a huge cultural barrier for many engineering organizations which may lack a deep pool of expertise in that area and for years, have priortized and emphasized non-software related development.

The tools are also a huge issue. You talk about the need to invest in development tools specifically around writing embedded code. There also needs to be an investment in tools that integrate the embedded development effort with the rest of the product design effort, both mechanical and electrical components. If all the work is done in silos, you can run into intercompatibility problems and design snafus late in the cycle when it is expensive to make changes.

williamlweaver
User Rank
Platinum
Re: Embedded development reality check
williamlweaver   7/24/2012 9:01:42 AM
NO RATINGS
Great article, Chuck. You have hit many of the major pinch points in embedded development. 
 
I like your first point "It's all about the software" and your second - "Software is a relatively new field... and we're really still figuring it out". The difficulty arises from Moore's law -- with every 18-months the capability of each component doubles as we continue to innovate.
 
Five years late with their product? That's more than three generations out of date before the team launched their first product.
 
If the development team decided to use traditional "requirements-based" project management, they need to freeze the requirements and build to the original specification. But as most teams find out quickly, even if they don't change requirements for new technology, the requirements change because of unanticipated difficulties and incorrect assumptions made by the original designers.
 
May I suggest an initial "Zeroth Point" on your list: "0. Use an Agile Software Development Method". Once the team develops using Agile methods, the subsequent components on your list are still important, but can be altered with less difficulty. The smart-phone industry is one of the best examples of successful Agile development. Pushing software updates to the devices, new models with new features arriving often, and using standard ports and interfaces so upgraded devices can be swapped out with relative ease are slowly becoming the norm.


gsmith120
User Rank
Platinum
Re: Embedded development reality check
gsmith120   7/24/2012 2:15:24 PM
Charles, really good article and lots of good points!!

I know and have been on those projects that seem to keep going and going and begging for someone to put them down.  Many good projects have over run budgets or just failed due to poorly written or no requirements or requirement creeping or engineer's free give aways.

If I had a .01 for every time I've heard an engineer say I can do this better and it would be nice to have this extra feature and just write it in without really understanding it is out of scope and most likely budget, I would be a millionaire. 

I remember having to fight management to purchase good lab equipment to test our designs.  It cost the company more money and the designers unnecessary time due to fighting with management to get what we needed to get the job done.

Charles Murray
User Rank
Blogger
Re: Embedded development reality check
Charles Murray   7/24/2012 5:17:32 PM
Very good point, Bill. The smartphone industry HAD to learn agile software development to survive, given their rate of progression of their products. Others need to learn to follow their lead.

Beth Stackpole
User Rank
Blogger
Re: Embedded development reality check
Beth Stackpole   7/25/2012 8:27:26 AM
Great point about agile development practices, William. I'm hearing more and more about those as I start to dive into cloud-based design tools and mobile apps. It's definitely a mind set change. Hopefully, it's a practice being woven into new curriculum to help engineers get their arms around how to do it adeptly.

Charles Murray
User Rank
Blogger
Re: Embedded development reality check
Charles Murray   7/24/2012 5:23:36 PM
NO RATINGS
Beth: As a former hardware guy, I feel comfortable saying this: Those of us who were educated in mechanical/electrical in the 1980s or earlier are have more trouble bridging that cultural barrier that you refer to. We've been trained to think in terms of hardware, and it's a tough habit to break. Maybe it's a bit of an ego thing, but it's tough to say, "Yes, software is the most important part of our product."

ttemple
User Rank
Platinum
Software
ttemple   7/24/2012 8:59:12 AM
NO RATINGS
"Software is a relatively new field -- only about 50 or 60 years old -- and we're really still figuring it out,"

I think this is one of the best points in the article.  This is a relatively unrecognized fact in the computer world.  There is a lot about software that we are still trying to figure out.

ChasChas
User Rank
Platinum
Why?
ChasChas   7/25/2012 10:52:57 AM
NO RATINGS
 

Okay, Charles, you told us that embedded programming is hard to do. Can you now tell us WHY?

I hear some programmers work better in the nude and all kinds of crazy stories. 

WHY?

Charles Murray
User Rank
Blogger
Re: Why?
Charles Murray   7/25/2012 7:20:10 PM
NO RATINGS
ChasChas: It can't really be boiled down any further than to say that writing and de-bugging code is a very slow, tedious, complex process and many products have hundreds of thousands, or even over a million, lines of code. As RogerD accurately points out here, the numbers cited here refer more to larger projects. Still, the stories I've heard seem to indicate that many, many teams don't have a full appreciation for the scale of the software portion, and that misunderstanding (or lack of understanding) gets them into trouble. As for your reference to eccentric behavior by programmers, we'll need some deeper insight from some of our readers on that one.   

ChasChas
User Rank
Platinum
Re: Why?
ChasChas   7/25/2012 8:59:33 PM
NO RATINGS
 

Thanks, Charles. I thought I could get you to use the word "convoluted".

RogerD
User Rank
Iron
Development time
RogerD   7/25/2012 12:39:36 PM
NO RATINGS
I went back to my last embedded project and tallied the hours and code, and the result was 50 lines of assembly-level code per 8 hour day, and this includes the algorithm development. This was a small medical device (2100 lines of code not including LUTs) where I did both the H/W and S/W. The S/W was real-time in nature due to a feedback controller.

So I think there are several caveats to the 200 lines per month number. It's no doubt accurate on large projects with a random assortment of programmers, and I find that just the problem of having multiple entities involved bogs the process down. In my example I had intimate knowledge of the H/W since I designed it as well, an advantage never afforded the typical project. But a factor critical to assess is the motivation and technical ability of the individuals involved rather than the use of a fixed line/day estimate; in fact I'd argue that using the smallest (carefully chosen) S/W staff possible has a significant benefit toward minimizing the development time.

ttemple
User Rank
Platinum
Re: Development time
ttemple   7/25/2012 2:36:04 PM
NO RATINGS
RogerD,

I couldn't have said it better.  I completely agree that the smallest possible software team will usually minimize development time.

I have seen a one man "team" design, debug, and program a very high performance FPGA/DSP/Microcontroller based motion control and data acquisition system in about a year (hardware and software).  I doubt if a whole team could have done it in five years.  A government funded team would probably never have finished it.  I'm not saying that anybody could have done what he did, but he was the right man for the job, and adding more people to the mix would have only slowed him down.

Unless a software project can be very distinctly divided and conquered, the fewer programmers the better.

JimT@Future-Product-Innovations
User Rank
Blogger
Post these bullets like Scripture Reference
JimT@Future-Product-Innovations   7/25/2012 1:27:00 PM
NO RATINGS
To point #1 (all about SW) truer words were never spoken. A recent contract assignment involved placement of a Standardized (COTS) transceiver on a motherboard.  One staff meeting discussion entertained the topic of eliminating the COTS transceiver in favor of a direct chipset embedded solution.  Easier for the EE's;  easier for the ME's.  But the SW guys hit the ceiling, citing months of recoding development.  All the points of your article are great checkpoints for whole teams and especially program managers to post on their walls for continuous awareness.

JimT@Future-Product-Innovations
User Rank
Blogger
One more bullet, #10: Agency Approvals take longer.
JimT@Future-Product-Innovations   7/25/2012 1:33:19 PM
NO RATINGS
One additional thought:  when a project takes any COTS module and places it onto a product host PCB, any Agency Approvals (FCC, UL, CE, etc.) are streamlined because the COTS module already "grand-fathers" the host product's approval process.  On the contrary, embedding the solution eliminates that short-cut and you must face the full scrutiny of any Agency.  Plan on adding at least another 8-12 weeks before approvals are granted.

bobjengr
User Rank
Platinum
Embedded development reality check
bobjengr   7/26/2012 6:22:13 PM
NO RATINGS
Great article Charles.  I am one of those mechanical types and have very limited experience with software, embedded or otherwise.  This field fascinates me and I am certainly appreciative of your article highlighting the difficulties with the technology.  Your comments about the time-consuming efforts and costs to produce the code were revelations.  Revelations.   My experience in programming is with C++, Pascal and Visual Basic, which are basically "learning-types" of software.  If I may, I write an educational blog published through WordPress; i.e. www.cielotech/wordpress.com.  Would you mind giving me permission to reference your article in an upcoming blog discussing embedded systems?  I think my readers would also be fascinated by the subject.  Many thanks, Bob J.

Charles Murray
User Rank
Blogger
Re: Embedded development reality check
Charles Murray   8/17/2012 6:31:54 PM
NO RATINGS
Sorry I didn't see your comment earlier, bobjengr. Please feel free to reference the article. I appreciate your comments.  

bobjengr
User Rank
Platinum
Re: Embedded development reality check
bobjengr   8/18/2012 1:38:40 PM
NO RATINGS
Many thanks Charles.  I will send you the write-up as soon as I finish.  Again, great article.  Bob

ErrantMule
User Rank
Iron
Masses of asses
ErrantMule   7/30/2012 6:08:55 PM
NO RATINGS
"The average programmer writes about 200 lines of code per month. At that rate, a staff of 50 would need 100 months -- more than eight years -- to write a million lines of code."

Knowing the author is simplifying for the sake of brevity, it may not be obvious to some that total lines of 'good' project code per time unit is never linear in the number of people devoted to the task.  There is definitely a point of diminishing returns, and a point at which adding more people does the project a disservice by making the overall task unwieldy, if not outright unmanageable.  Microsoft used to blame IBM for ruining OS2 because non-technical managers relied on the 'masses of asses' principle as a means of (erroneously) getting it done faster, then ran roughshod over the coders when the simple arithmetic did not prove axiomatic.  The people who were a party to the overall 'vision' at the outset can become disconnected from what is actually emerging, as new people are added at the back end to expedite certain tasks or address new requirements.  Moreover, the newcomers may have a completely different view of what the goal posts look like.  If you start out with a few people who all know 'C' well then, for example, marketing decides the thing needs Android, bringing in Java experts who've never seen a pointer in their life may cause the team to split into two camps, and they may end up competing more often than working together.

Regarding operating systems, I agree they should be avoided wherever prudent and possible.  For some projects however, there's no getting away from it.  For example, if you're targeting a high end MPU like a Cortex A8 or above, you NEED an OS else you'll get bogged down in the minutiae of writing drivers etc.  The first rule of thumb is you should abandon all rules of thumb.  The second might be if you're using a MCU like a MSP430 or a Cortex-M0 to M3, you can probably get away without an OS.  As stated in the article, concurrency beyond all but the simplest of requirements dictates you need an OS to manage access to inter-process, shared objects.

Thanks to the author for making a software guy feel important for an afternoon.  It's time to go home so my teenager can ruthlessly burst that delicate bubble.

 

Partner Zone
More Blogs from Electronic News & Comment
A Design News course on field programmable gate arrays (FPGAs) should help engineers who are considering the technology for their upcoming designs.
Conventional wisdom holds that MIT, Cal Tech, and Stanford are three of the country’s best undergraduate engineering schools. Unfortunately, when conventional wisdom visits the topic of best engineering schools, it too often leaves out some of the most distinguished programs that don’t happen to offer PhD-level degrees.
If you're planning to develop a product that uses a microcontroller, you'll want to take note of next week's Design News Continuing Education course, "MCU Software Development – A Step-by-Step Guide."
The diesel engine, long popular on European roads, is now piquing the interest of American automakers.
As more electric cars and plug-in hybrids hit the highways, the need for battery chargers is growing.
Design News Webinar Series
9/25/2014 11:00 a.m. California / 2:00 p.m. New York
9/10/2014 11:00 a.m. California / 2:00 p.m. New York
7/23/2014 11:00 a.m. California / 2:00 p.m. New York
10/7/2014 8:00 a.m. California / 11:00 a.m. New York
Quick Poll
The Continuing Education Center offers engineers an entirely new way to get the education they need to formulate next-generation solutions.
Oct 20 - 24, How to Design & Build an Embedded Web Server: An Embedded TCP/IP Tutorial
SEMESTERS: 1  |  2  |  3  |  4  |  5  |  6


Focus on Fundamentals consists of 45-minute on-line classes that cover a host of technologies. You learn without leaving the comfort of your desk. All classes are taught by subject-matter experts and all are archived. So if you can't attend live, attend at your convenience.
Next Class: October 2
Sponsored by Altera
Learn More   |   Login   |   Archived Classes
Twitter Feed
Design News Twitter Feed
Like Us on Facebook

Sponsored Content

Technology Marketplace

Copyright © 2014 UBM Canon, A UBM company, All rights reserved. Privacy Policy | Terms of Service