This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DP83848-EP: PHY

Part Number: DP83848-EP

Hi,

Why are we seeing the RX_ER pin go active on us when initiating an FTP file transfer to our :

1. The DP83848 BIST external loopback test passed with flying colors, and,

2.Two identical products successfully perform the file transfer task, i.e, ethernet packets are the same

The MAC FPGA is on the 'other side' of the PHY and should not be a factor as to why the RX_ER pin of the PHY goes high

Thanks

  • Hi Don,

    The person who supports this is in Dallas and the question came through after 6pm CDT.   He will respond to your question on Monday morning.

  • Don,

    I am going to request our catalog team take a look at this and offer debugging  suggestions.

    When you indicate two identical products, what do you mean?  Different boards of same design?

    Do you have schematic that can be shared?

    Regards,

    Wade

  • Hi Wade,

    Yes - Identical products, same design and plugged in and tested the same test environment.

    We have successfully produced and tested more than 15 of these boards. This is first test failure we've had.

    We have measured strapping, power and clocks on these board several times already

    We are Boeing Aerospace here, data is somewhat restricted so I am not sure if I can advertise the schematics. I can probably provide the schematic page showing the PHY.

    We are starting to contemplate swapping parts on the board, which is a very expensive and delicate process

    We are wondering why we are getting the RX_ER when we attempt to transfer data thru the PHY given that it is passing the BIST External Loopback test and that the packets sent to it are the same as transferred with all other products that passed tests

    I will find out if I can attach some data for you guys to review. 

    Yours,

    Don J

    P.s, Additional info:

    We used Wireshark to analyze the comm between our ETH board (Clent) and the FTP File Server (21). It shows that Wireshark (sitting at the same PC that has the FTP Server) saw the valid REQ from our Client and then saw the SYN:ACK sent out from the FTP Server to the Client, but did not see the 3rd HS step, the ACK back from the Client to the server. We then enter a retry cycle for a few minutes before quitting.  

  • Don,

    I apologize for delay.  The mass market team has been out of the office for awhile.  I have been able to confirm that they can take a look at this shortly and provide input.  Likely they will want a schematic snippet of the PHY to accelerate.

    Regards,

    Wade

  • I can provide the schematics snippet for the PHY plus more info but i'd like to send it to a more limited distribution location rather than to the open forum website.

  • Don,

    I will contact you via email to get additional information.

    Thanks,

    Wade

  • Closing this post for now, as this is being addressed via email.

    Thanks,

    Wade