DP83867IS: Link up problem

Atsushi Takahashi

Expert 1415 points

Part Number: DP83867IR
Other Parts Discussed in Thread: DP83867IS

Tool/software:

Hi Team,

I have link up problem in customer application using the DP83867IRPAP.

The link partner is DP83867CRRGZR.

I have the schematic, artwork and register information.

Could you check these and give me some advice?

As these are customer information, it cannot be posted in this thread.

I would prefer to send it via private message.

Best Regards,

9 months ago

0 Atsushi Takahashi 9 months ago

Expert 1415 points

Hi Team,

This is a different case from the following thread I posted previously.

DP83867IS: About Gigabit Master Scramble Mode
https://e2e.ti.com/support/interface-group/interface/f/interface-forum/1467528/dp83867is-about-gigabit-master-scramble-mode

DP83867IS: Communication problems
https://e2e.ti.com/support/interface-group/interface/f/interface-forum/1447700/dp83867is-communication-problems

The part number DP83867IS in the title of this thread is incorrect. Sorry.

As stated in the description, the local device is DP83867IRPAP and the link partner is DP83867CRRGZR.

0 Evan Mayhew 9 months ago in reply to Atsushi Takahashi

TI__Mastermind 25148 points

Hi Takahashi-san,

Do you have an FAE contact? If so, please have them create an internal thread to share the information for this issue.

Otherwise, please email me the details at e-mayhew@ti.com .

Thank you,

Evan

0 Atsushi Takahashi 9 months ago in reply to Evan Mayhew

Expert 1415 points

Hi Evan-san,

Thank you for your reply.

I don't have FAE contact.

I'll send you e-mail later.

0 Evan Mayhew 9 months ago in reply to Atsushi Takahashi

TI__Mastermind 25148 points

Sounds good, please reach out as needed.

Thank you,

Evan

0 Atsushi Takahashi 9 months ago in reply to Evan Mayhew

Expert 1415 points

Hi Evan-san,

I sent you an email the other day.

How is the progress in this case?

Thank you,

0 Evan Mayhew 9 months ago in reply to Atsushi Takahashi

TI__Mastermind 25148 points

Hi Takahashi-san,

Apologies for the delay here, I will share feedback by EOD 3/13.

Thank you,

Evan

0 Atsushi Takahashi 9 months ago in reply to Evan Mayhew

Expert 1415 points

Hi Evan-san,

Thank you for your reply.

I look forward to hearting from you.

If customer design information is included, please respond by email.

0 Evan Mayhew 9 months ago in reply to Atsushi Takahashi

TI__Mastermind 25148 points

Hi Takahashi-san,

Could you please share the PHY register dump for both the passing and failing link cases?

Are all customer application units identical?

Here are the possible causes of link failure:

MDI signal quality (please see email for schematic concern)
Auto-negotiation configuration issue (caused by incorrect straps or register init in software)
Link partner does not support 1G auto-negotiation (can read 867 register 0x5 to confirm advertisements from link partner)

Thank you,

Evan

0 Atsushi Takahashi 9 months ago in reply to Evan Mayhew

Expert 1415 points

Hi Evan-san,

Thank you for your reply.

I sent you e-mail about MDI signal and register info.

You said;

Are all customer application units identical?

What does this question mean? I'm sorry for my lack of understanding.

0 Evan Mayhew 9 months ago in reply to Atsushi Takahashi

TI__Mastermind 25148 points

Hi Takahashi-san,

Atsushi Takahashi said:
I sent you e-mail about MDI signal and register info.

I will review and share feedback over email.

Atsushi Takahashi said:
Are all customer application units identical?

Sorry for the confusion here.

I assume the test case is Customer Application Unit (DP83867) connected to Link Partner (PHY/MPU?)

I would like to know if all Customer Units are initialized with the same PHY/MPU config, and if the Link Partners are identical (no difference in PHY, MPU, and SW config for each test case).

Thank you,
Evan

Interface

Interface forum

DP83867IS: Link up problem