New ContributorHi Intel Folks, @Farabi
Jabil manufacturing line found 9pcs MPN: 10M16SAU169C8G FPGA component with failure symptom :"unable to program" , 3.3V short to ground.
Please kindly advise how are we going to perform the reject parts return.
Its urgent case. Need response ASAP.
New ContributorI would like to continue this discussion privately. Please enable the private message capability.
Regular ContributorHello,
Do you have distributor to file IPS for FACR case?
regards,
Farabi
Regular ContributorHello Jun Yi,
We have filed IPS case for your FACR. Now CQE want the DPR (Device Problem Report).
I attached the DPR and please fill in and send back to us to process the FACR.
regards,
Farabi
Super ContributorHi,
Any update? Have you fill in the DPR form?
1- What is the failure symptom? Please elaborate the failure symptom in detail.
2.- When did the failure happen?
3.- How did you discover the failure?
4.- In which part of your process did you found the issue (Lab, production, quality, etc.)?
4.1- Was the device already in Field? For how long?
5.- How many units failed and how many units were used/tested by you?
6.- How did you determine the failure? Please elaborate the procedures.
7.- Does the failure unit was ever working before failure? If yes, how long had it been in use?
8.- How did you rule out that the failures were not caused by an electrical over stress (EOS) or an Electrostatic discharge (ESD)?
9.- What are your expectations of this failure analysis?
10.- Have you Re-ball your device? If yes, Is it lead-free reballing?
11.- Please add pictures of the device from the top and the bottom.
Regards,
Aiman
New ContributorJabil？
Super ContributorHi,
Can you also answer below?
1- What is the failure symptom? Please elaborate the failure symptom in detail.
2.- When did the failure happen?
3.- How did you discover the failure?
4.- In which part of your process did you found the issue (Lab, production, quality, etc.)?
4.1- Was the device already in Field? For how long?
5.- How many units failed and how many units were used/tested by you?
6.- How did you determine the failure? Please elaborate the procedures.
7.- Does the failure unit was ever working before failure? If yes, how long had it been in use?
8.- How did you rule out that the failures were not caused by an electrical over stress (EOS) or an Electrostatic discharge (ESD)?
9.- What are your expectations of this failure analysis?
10.- Have you Re-ball your device? If yes, Is it lead-free reballing?
11.- Please add pictures of the device from the top and the bottom.
Regards,
Aiman
New ContributorHi @NurAiman_M_Intel ,Hi,
Can you also answer below?
1- What is the failure symptom? Please elaborate the failure symptom in detail.
The only failure symptom is FPGA fail to program during our manufacturing test.
2.- When did the failure happen?
During our manufacturing functional test.
3.- How did you discover the failure?
When we program the FPGA.
4.- In which part of your process did you found the issue (Lab, production, quality, etc.)?
Production
4.1- Was the device already in Field? For how long?
Nope, the FPGA is brand new part.
5.- How many units failed and how many units were used/tested by you?
9 pcs fail out of total 300pcs tested.
6.- How did you determine the failure? Please elaborate the procedures.
The only failure symptom is FPGA fail to program during our manufacturing test.
7.- Does the failure unit was ever working before failure? If yes, how long had it been in use?
Nope, the reject part is constantly fail.
8.- How did you rule out that the failures were not caused by an electrical over stress (EOS) or an Electrostatic discharge (ESD)?
Our production line go through similar process and handle with same method.
9.- What are your expectations of this failure analysis?
Get the Root cause and FA to confirm why the FPGA fail to program.
10.- Have you Re-ball your device? If yes, Is it lead-free reballing?
Nope. There is not needed for re-ball.
11.- Please add pictures of the device from the top and the bottom.
Sorry to said that we already quarantine the reject part and its not possible to pull the part out from quarantine area.
Super ContributorThank you. I have forwarded all the information for FACR. Will keep you updated.
Regards,
Aiman
New ContributorHi @NurAiman_M_Intel ,
Any update or good news for the FACR? We are request this since 20th Jan. Its almost one month for this case.
Super ContributorHi,
I have respons to you through private message. However we are required to investigate the failure symptom as you mention:
The only failure symptom is FPGA fail to program during our manufacturing test.
What is the failure message/error message? Can you please send us the screenshot of the error message.?
Regards,
Aiman
Super ContributorHi,
Any update for this case?
Regards,
Aiman
New ContributorHi @NurAiman_M_Intel ,
Very sorry to say we dont have any screen shot provided. Its fail during our customer manufacturing functional test . We only know the content of FPGA not able to program, then our debug team replace new FPGA and those boards able to pass test.
Please kindly help for return the parts for FA. This case is dragging for too long time.
Super ContributorHi,
I did email you through forum email as it require some private information. Can you kindly response to the email?
Regards,
Aiman
New ContributorHi @NurAiman_M_Intel ,
Please refer to below reply and attachment of photo.
Customer Name: Advantest
Development Board: <please fill in>DCN and DCL
Project Name: <please fill in> Native DCDC
Project Status: (Design in / Design Commit / Prototype ?) <please fill in>Mass Production
Target Production Date: <please fill in>NA
Project Value / Revenue ($/Year): <please fill in>NA
Quartus Version being used: <please fill in> 21.1
Software patches (if any): <please fill in> NA
