[eevblog] Apple's MacBook Design FAIL – Who's To Blame? - Overclock.net - An Overclocking Community

Forum Jump: 

[eevblog] Apple's MacBook Design FAIL – Who's To Blame?

 
Thread Tools
post #1 of 1 (permalink) Old 06-20-2019, 04:11 PM - Thread Starter
Head Dwarf
 
iamjanco's Avatar
 
Join Date: Aug 2016
Location: In a circus tent
Posts: 1,918
Rep: 86 (Unique: 56)
[eevblog] Apple's MacBook Design FAIL – Who's To Blame?

Dave Jones--who runs eevblog--digs deeper into the examination/review Louis Rossmann did last December of problems with the engineering design associated with the latest MacBook Pros available at that time:


A...
made by Youtube user Rainiedays to Rossman's video actually sums up the root cause(s) fairly well:

Quote:
...as a former hw engineer of a large company, it's easy to see where this error arose. No single designer is responsible for the design from start to finish in a large corporation. The error started with the CAD librarian (responsible for drawing schematic symbols for new parts and maintaining them in a "library") who incorrectly labeled pins 1 and 43 to be far apart numerically when physically they are close together with the mindset that the physically larger rail (voltage and ground) pins (43 and 44) should be grouped together with the other rail pins (45+), without highlighting that pins 43 and 44 are actually physically super close to pins 1 and 2. The board/circuit designer (person responsible for designing the schematic) then imported the connector into the schematic and performed pin assignment with the assumption that pins 1 and 43 are far apart because they're numerically far apart (a completely different mindset than what the librarian had). When this is passed onto the layout engineer (person responsible for actually routing the design on a physical board), he routes the design blindly and does not catch the error because he does not know or really care about how the circuit functions. When the board goes thru testing, nothing is ever caught since nobody has the foresight to purposely try to short a design during testing. Ultimately this is a flaw due to a misunderstanding/mismanagement between multiple engineers with different functions. This would never happen in a smaller company where the design is owned by one person from start to fab, so Apple being rich and large actually works against them because all of the engineers that work on a board need to have the same exact design philosophy or at least adhere to the same standard. This flaw is still, of course, unacceptable and can be remedied with better communication or a set internal design philosophy standard.

...playin' the lead roll in a dwerg tossing contest.



Last edited by iamjanco; 06-20-2019 at 04:19 PM.
iamjanco is offline  
Sponsored Links
Advertisement
 
Reply

Quick Reply
Message:
Options

Register Now

In order to be able to post messages on the Overclock.net - An Overclocking Community forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.
User Name:
If you do not want to register, fill this field only and the name will be used as user name for your post.
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:

Log-in



Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Show Printable Version Show Printable Version
Email this Page Email this Page


Forum Jump: 

Posting Rules  
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off