Breaking News
Design How-To

That Was Tricky: How much decoupling should we use?

2/23/2012 02:58 PM EST
4 comments
NO RATINGS
More Related Links
View Comments: Newest First | Oldest First | Threaded View
ReneCardenas
User Rank
Rookie
re: That Was Tricky: How much decoupling should we use?
ReneCardenas   3/30/2012 10:05:41 PM
NO RATINGS
May be you should tell your vendor that you had a fix for their board that you would share provided he paid for your knowledge gain from this effort. Or at the very least a discount in the next batch, if you were EVER willing to spend any additional money in products from a source that failed to acknowledge such problems. ;-)

ialexo
User Rank
Rookie
re: That Was Tricky: How much decoupling should we use?
ialexo   2/26/2012 7:25:12 PM
NO RATINGS
Although in general I agree with you and this is what i usually do, at the particular time the whole team was so frustrated by such a primitive problem, while at the same time we have paid much money to get these boards from an expert (they were not custom boards just for us). If decoupling design was more sensible, we would probably told him.

cdhmanning
User Rank
Rookie
re: That Was Tricky: How much decoupling should we use?
cdhmanning   2/25/2012 8:07:26 PM
NO RATINGS
"Needless to say, we never told the designer of the development board our findings…" Why not? If I had designed a board that had a problem I would want to be told so that (1) I could fix it. and (2) improve my ability to design better in the future.

David Ashton
User Rank
Blogger
re: That Was Tricky: How much decoupling should we use?
David Ashton   2/23/2012 7:07:13 PM
NO RATINGS
@ "Needless to say, we never told the designer of the development board our findings…" I wonder what would have happened if you had done so??

Most Recent Comments
_hm
 
David Ashton
 
Olaf Barheine
 
BobSnyder
 
elizabethsimon
 
seaEE
 
BobSnyder
 
NoviceMan
 
David Ashton
August Cartoon Caption Winner!
August Cartoon Caption Winner!
"All the King's horses and all the KIng's men gave up on Humpty, so they handed the problem off to Engineering."
5 comments
Top Comments of the Week
Like Us on Facebook

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)
EE Times on Twitter
EE Times Twitter Feed
Flash Poll
Radio
LATEST ARCHIVED BROADCAST
David Patterson, known for his pioneering research that led to RAID, clusters and more, is part of a team at UC Berkeley that recently made its RISC-V processor architecture an open source hardware offering. We talk with Patterson and one of his colleagues behind the effort about the opportunities they see, what new kinds of designs they hope to enable and what it means for today’s commercial processor giants such as Intel, ARM and Imagination Technologies.