EP4CGX110DF27I7N ISSUA

[Pablo4]

Customer reported: FRU1 Faulted. The unit booted up correctly, logs were retrieved The unit was vali Date Posted: November 27, 2023 Customer reported: FRU1 Faulted. The unit booted up correctly, logs were retrieved The unit was validated with Filler and TB0. FRU detection was validated, Slot 1 failed. Swap was done and the unit was validated again, failing same slot. FRU’s used during validation were M99441FD and M994C124, respectively before swap. Factory Reset was performed. Slot 1 remained failing. FRU0_SCL_SRC and FRU0_SDA were detected absent at Main Board. U91 was sent for replacement. Critical repair reported multiple damaged pads at removing BGA, and alerted the high risk of the repair process. This was escalated to Ciena, who authorized to continue with the repair. Pads of FRU0_SCL_SRC and FRU0_SDA signals were affected / damaged. This is a critical repair with its own risks. After repair, the unit was validated manually and still failed. The root cause of the field failure mode is damaged pads at U91 location. PN: EP4CGX110DF27I7N Qty: 2 Flex PN: N0230475

[Farabi]

Hello,

Could you please explain what is the problem with your FPGA?

is it power issue? config issue? what are the symptoms?

please explain in details so we can provide assistance.

regards,

Farabi

[Pablo4]

• Could you please explain what is the problem with your FPGA?
  Yes, FPGA was not sending signals to control one of the peripherals of the unit (there are two ones of this type, called P0 and P1). RMA unit could not communicate with P0 because of the absence of signals on AB8 and AF5 pins. Case was concluded as electrical damage.

• is it power issue? config issue?

No, it is not power issue, since all other functions related to FPGA were performed successfully. Only mentioned signals were not working properly. Do to this, I consider config issue unlikely, but component arrived programmed, there is no programming process in production floor to validate this part. Further analysis was required by Ciena due to the unit had failed in field, that is, it passed all test train in factory before shipping and failed with final customer.

• what are the symptoms?

Only symptom is the absence of mentioned signals, at pins AB8 and AF5, that should be working and they are not.

[Fakhrul]

Hi Pablo4,

From my understanding you're having issues on two Cyclone IV boards, right? Are these two boards having the same behavior as you've mentioned that there are no output signals at pins AB8 and AF5?

Regards,

Fakhrul

[Pablo4]

Answering your questions:

From my understanding you're having issues on two Cyclone IV boards, right?
Yes, that's right, two boards had issues with FPGA Cyclone IV components.

Are these two boards having the same behavior as you've mentioned that there are no output signals at pins AB8 and AF5?
Yes, both cases presented same behavior, no output signals from mentioned pins.

Pls let me Know if we can proceed by RMA, we need to know the root cause of this failure mode detected in Field. 

[Fakhrul]

Hi Pablo4,

May I get details of the boards to check the warranty:

1)Serial Number S/N:

2)Product Number P/N:

3)DVK Model Name:

and also your information

Name:

Email address:

Company:

Site:

Regards,

Fakhrul

[Pablo4]

Hi Intel team, pls find in the below in the atatched file the feedbacka about the informaiton requetsed by you.

Pls help me to check and confinr to me if we can proceeed wiht the RMA. 

1)Serial Number S/N: CAAAF2113E.

2)Product Number P/N: EP4CGX110DF27I7N.

1)Serial Number S/N: CAAAF2225E.

2)Product Number P/N: EP4CGX110DF27I7N.

Could you please clarify what  does DVK Model Name stand for?

Name: Pablo Perez Hernandez

Email address: pablo.perez@flex.com

Company: Flextronics

[Fakhrul]

Hi Pablo4,

Before we proceed to FA. Can you perform a signal tap on that particular pins? If the ball is damaged during the assembly process Intel would not accept it because it is due to mishandling.

Regards,

Fakhrul

[Pablo4]

Flex doesn't count with infrastructure to perform a Signal Tap. FPGA is bought to the broker Arrow and it arrives already programmed. Talking about mishandling, it is considered not likely due to test coverage: the unit passed all tests in factory, but failed in field. That's the why of 2nd level FA request.

RX evidence attached.

CAAAF2113E

CAAAF2225E

[Pablo4]

Hi Itel Team, Im waiting for the next step, in ordet to determinate the root cause. pls let me know how proceed. 

[Fakhrul]

Hi Pablo4,

Require confirmation from the customer regarding any mention of ball damage:

• Is it solely the ball, or does it include the pad?

• In the case of the pad, please verify the pin name. It's important to highlight that we cannot accept pad damage because our Test Program (TP) will fail to function if a critical test pin cannot be read. The resulting report will indicate 'undetermined' as no valid result can be obtained in such cases.

Regards,

Fakhrul

[Pablo4]

Hi Intel Team, Is it solely the ball, or does it include the pad?
Solely the ball.

These kind of failure is becoming epidemic, and in all cases investigations are taking us to FPGA. Do you need any further information to continue with FA?

Pls let me to check, we need you suport in expedite the FA for material reported. 

[Pablo4]

Hi Intel team, im attaching the device problem report, pls let me know the next step for have the RMA, we need your support por FA from Intel and determinate the root cause of the dailure reported. 

Waiting for your comments. 

[Pablo4]

Friendly reminder, 

 Hi Intel team, Im wating for the RMA , and continue with the analysis of the dailure reported by Flex. 

[Pablo4]

Friendly reminder, 

 Hi Intel team, Im wating for the RMA , and continue with the analysis of the dailure reported by Flex. 

[Pablo4]

Hi Intel Team, pls let me know the RMA status, and if the informtion shared by Flex is complete, we need t continue wiht the RMA for root cause anslisi. 

Wating for your comments.