HOME  |  NEWS  |  BLOGS  |  MESSAGES  |  FEATURES  |  VIDEOS  |  WEBINARS  |  INDUSTRIES  |  FOCUS ON FUNDAMENTALS
  |  REGISTER  |  LOGIN  |  HELP
<<  <  Page 2/2
garysxt
User Rank
Iron
HW vs SW
garysxt   9/6/2013 11:56:20 AM
NO RATINGS
In the projects I manage I have a rule that both software and hardware are guilty until proven innocent.  Both groups are expected to work together to solve the problem. The SW guys can dismiss the HW team or vice versa if they feel the ball is in their own court, but one group can't claim the problem is on the other side and walk away on their own.

In the first week on this job I overheard some software guys discussing a problem. I went over an offered to help (it sounded like possibly a couple of shorted address lines). It turned out to actually be a software problem, but I gained a lot of respect from that incident. They were used to both sides pointing fingers at each other.

Jim_E
User Rank
Platinum
Great find
Jim_E   9/6/2013 9:07:25 AM
NO RATINGS
That's a good story!  (and by a fellow Evans too...)  I like how just noticing that it took a slightly longer time to fail from a cold start gave you the idea of how to narrow down the problem.  I've never worked for a super-large company with all of those divisions, but I see how there could be communication issues.

At least all of your hardware came internally.  I recall dealing with a hardware problem (not as severe as yours) when writing firmware, but the hardware was from an outside supplier who refused to accept that they had a problem.  We eventually had to write a workaround in software.  The old "can't you guys fix that in the software" solution.

 

tekochip
User Rank
Platinum
Difficult to determine
tekochip   9/6/2013 8:57:40 AM
NO RATINGS
It's very often difficult to determine if a problem is caused by hardware or software.  I had a problem with an NXP processor that would crash whenever the I2C interface was turned on.  It sounds like software, but when all other tasks were halted and only the I2C ran, everything was fine.  OK, maybe I'm running out of execution time?  No, no problem there either.  NXP eventually sent out an errata that the Vdd bond wire in the chip had too large of a voltage drop and would crash when the processor was pulling a great deal of current.


laser_scientist
User Rank
Iron
Human nature
laser_scientist   9/6/2013 8:43:53 AM
NO RATINGS
Actually, I have seen this phenomenon in various other development situations, as well, except that you could replace "firmware team" and "hardware team" with "hardware module 1 team" and "hardware module 2 team". I think it's human nature (at least for the engineer/scientist humans) to make up your mind what the problem is, and then proceed as though your notion is the truth -- until proven otherwise. Which is exactly what the hardware engineers did in this case.

 

naperlou
User Rank
Blogger
Configuration Control
naperlou   9/5/2013 8:52:59 AM
NO RATINGS
Jason, configuration control and documentation are critical to ensuring that a design is correct and can pass from prototype to production.  When "patches" go undocumented, as you discovered with the evaluation board, then it becomes impossible to correctly configure the system.  Software has dealt with this situation for some time.  Frankly, I always thought hardware did as well.  Just goes to show...

<<  <  Page 2/2


Partner Zone
Latest Analysis
We take a look at 2015's top engineering schools by salary potential for undergraduate students.
If we are going to be creating a network that serves us, one of its most critical nodes will need to be ourselves. This is where wearable technology comes into play.
Researchers at the University of Maryland have achieved a first in lithium-ion battery science: the development of a successful lithium-based battery using one material for all three core components of a battery -- anode, cathode, and electrolyte.
The online Bar Steel Fatigue Database for automotive design engineers has been updated for the fifth time and now contains 134 iterations, or grade/process combinations. It provides better predictability for designing parts with long-term reliability and durability.
FPGAs use programmable fabric to create custom logic, but this flexibility comes at a cost -- usually around 10 times more silicon real estate and 10 times the power dissipation. Can we really claim any FPGA is low power?
More:Blogs|News
Design News Webinar Series
5/21/2015 11:00 a.m. California / 2:00 p.m. New York
5/7/2015 11:00 a.m. California / 2:00 p.m. New York
6/3/2015 8:00 a.m. California / 11:00 a.m. New York
6/11/2015 11:00 a.m. California / 2:00 p.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.
Jun 8 - 12, Everything You Ever Wanted to Know about Filters
SEMESTERS: 1  |  2  |  3  |  4  |  5  |  6 |  7


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 Course June 2nd-4th:
Sponsored by Proto Labs
Learn More   |   Login   |   Archived Classes
Twitter Feed
Design News Twitter Feed
Like Us on Facebook

Sponsored Content

Technology Marketplace

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