• State Resolved
  • Locked Locked
  • Replies 13 replies
  • Subscribers 33 subscribers
  • Views 463 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DP83867IR: PING does not work

Hisao Uchikoshi
Genius 14900 points
Part Number: DP83867IR

Hi Experts,

My customer is facing an issue that the communication over ethernet does not work. PING cannot reach to peer device. Below is the detail.

- Once this failure occurs, user needs to plug out and re-plug in to restart it..

- The failure rate is once per 100 times of the cable plug-in. The failure rate seems to depends on the ethernet cable. This occurs when using CAT5 w/o shield. When using CAT5 WITH shield, the failure rate becomes lower. 

- Auto negotiation ON, Auto MDIX

- The peer device is the switching hub and LINK LED is on even when this failure occurs.

- They dumps resisters and below are only differences.

Address

NG

OK

ANER (0x0006)

0x006F

0x006D

ADDAR (0x000E) 

0x00AA

0x0000

ISR (0x0013)

0x1C40

0x0000

Can you please suggest anything how to find the root cause?

Regards,

Uchikoshi

  • 0
    TI__Mastermind 39855 points

    Hello Uchikoshi,

    Are you able to get link and no ping? Or can not link at all?

    Also, can we get your register settings for registers 0-1F, 6E, 6F?

    Sincerely,

    Gerome

  • 0 in reply to Gerome Cacho
    TI__Genius 14900 points

    Hi Gerome,

    Link seems to be established. Please see below registers settings.

    Address

    OK

    NG

    0x00

    0x1000

    0x1000

    0x01

    0x796D

    0x796D

    0x02

    0x2000

    0x2000

    0x03

    0xA231

    0xA231

    0x04

    0x01E1

    0x01E1

    0x05

    0xC1E1

    0xC1E1

    0x06

    0x006D

    0x006F

    0x07

    0x2001

    0x2001

    0x08

    0x4806

    0x4806

    0x09

    0x0300

    0x0300

    0x0A

    0x3800

    0x3800

    0x0B

    0x0000

    0x0000

    0x0C

    0x0000

    0x0000

    0x0D

    0x401F

    0x401F

    0x0E

    0x0000

    0x00AA

    0x0F

    0x3000

    0x3000

    0x10

    0x5048

    0x5048

    0x11

    0xAC02

    0xAC02

    0x12

    0x0000

    0x0000

    0x13

    0x0000

    0x1C40

    0x14

    0x29C7

    0x29C7

    0x15

    0x0000

    0x0000

    0x16

    0x0000

    0x0000

    0x17

    0x0040

    0x0040

    0x18

    0x6B56

    0x6B56

    0x19

    0x4444

    0x4444

    0x1A

    0x0002

    0x0002

    0x1B

    0x0000

    0x0000

    0x1C

    0x0000

    0x0000

    0x1D

    0x0000

    0x0000

    0x1E

    0x0002

    0x0002

    0x1F

    0x0000

    0x0000

    0x6E

    0x0001

    0x0001

    0x6F

    0x0100

    0x0100

    Regards,

    Uchikoshi

  • 0 in reply to Hisao Uchikoshi
    TI__Mastermind 39855 points

    Hi Uchikoshi,

    Please give us 1-2 days to do some research regarding this issue.

    Sincerely,

    Gerome

  • 0 in reply to Gerome Cacho
    TI__Mastermind 39855 points

    Hello Uchikoshi,

    My apologies, but I will need additional time to gather up the information. I should be expecting to get back to you early next week. Again, apologies for the delay.

    Sincerely,

    Gerome

  • 0 in reply to Gerome Cacho
    TI__Genius 14900 points

    Hi Geromo,

    I understood. Customer is going to start the mass production soon so I really appreciate your investigation.

    Regards,

    Uchikoshi

  • 0 in reply to Hisao Uchikoshi
    TI__Mastermind 39855 points

    Hello,

    Can you please send the schematic?

    Sincerely,

    Gerome

  • 0 in reply to Gerome Cacho
    TI__Genius 14900 points

    Hi Gerome,

    So do you mean that you did not find any issue on register settings? Could you please confirm if you can find any hint from register settings at first?

    Regards,

    Uchikoshi 

  • 0 in reply to Hisao Uchikoshi
    TI__Mastermind 39855 points

    Hello Uchikoshi,

    I could not find anything explicitly problematic within the register settings. Looking at your comments on the issues, specifically, the CAT5 observation, I would like to move the focus to the schematic to see if there is anything of interest there.

    Sincerely,

    Gerome

  • 0 in reply to Gerome Cacho
    TI__Genius 14900 points

    Hi Gerome,

    Sorry for the late reply. We would like to confirm below.

    1. It looks that LINK is established since BMSR register bit 2 indicates 1 = Valid link established. Do you have any idea what causes the connection cannot start even though LINK is established?

    2. For one of recovery process, there is a way that user issues the software reset or retry the negotiation. For that purpose, are there any registers for user to detect if this error condition is occurring?

    Regards,

    Uchikoshi

  • 0 in reply to Hisao Uchikoshi
    TI__Mastermind 39855 points

    Hey Uchikoshi,

    I had some follow up questions regarding the issue:

    1) Is the issue both created and resolved through connecting and disconnecting the cable? Or is the PHY under normal operation and then this issue comes up?

    2) Can you verify if there is data communication on TX and RX during both NG and OK case?

    3) What is the length of the cable you are using?

    4) Have you tried using a CAT-5E cable? Does this change the occurrence rate of this issue?

    5) Have you tried using a different DP83867IR board? Does this change the occurrence rate?

    6) Have you tried using a different switch or overall link partner? Does this change the occurrence rate?

    I would like to take a look at your schematic to see if there is anything that might cause an issue there. Can you please send it to me?

    Sincerely,

    Gerome

  • 0 in reply to Gerome Cacho
    TI__Genius 14900 points

    Hi Gerome,

    Please see my comments in below.

    1) Is the issue both created and resolved through connecting and disconnecting the cable? Or is the PHY under normal operation and then this issue comes up?

    The issue occurs only when connecting the cable.

    2) Can you verify if there is data communication on TX and RX during both NG and OK case?

    This is difficult for customer to monitor it since they do not have any equipment and not enough time.

    3) What is the length of the cable you are using?

    I need to ask.

    4) Have you tried using a CAT-5E cable? Does this change the occurrence rate of this issue?

    I need to ask but I am expecting the issue will disappear.

    5) Have you tried using a different DP83867IR board? Does this change the occurrence rate?

    No, they have not tried..

    6) Have you tried using a different switch or overall link partner? Does this change the occurrence rate?

    No, they have not tried.

    Customer wants to close this inquiry with the answer to below questions.

    1. It looks that LINK is established since BMSR register bit 2 indicates 1 = Valid link established. Do you have any idea what causes the connection cannot start even though LINK is established?

    2. For one of recovery process, there is a way that user issues the software reset or retry the negotiation. For that purpose, are there any registers for user to detect if this error condition is occurring?

    Regards,

    Uchikoshi

  • 0 in reply to Hisao Uchikoshi
    TI__Mastermind 39855 points

    Hi Uchikoshi,

    Without being able to review the schematic, I suggest the following to see if they are able to resolve your issue:

    1) Software Reset: Register 0x0, Bit 15 = '1'

    2) Auto-negotiation Restart: Register 0x0, Bit 9 = '1'

    3) Hardware Restart: Pin RESET_N (either 59 or 43 depending on the package), send low for atleast 1µs.

    Please try all these steps and let me know which ones would resolve the issue.

    Sincerely,
    Gerome

  • 0 in reply to Gerome Cacho
    TI__Genius 14900 points

    Hi Gerome,

    The issue occurrence depends on the cable and customer confirmed there were so noise on the cable. Now we want to close this inquiry.

    Thank you so much for your kind support.

    Regards,

    Uchikoshi