• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 34 subscribers
  • Views 786 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.

TLK110 PHY - parallel detection not happening

Prasanna Vengateshan
Prodigy 50 points
Other Parts Discussed in Thread: TLK110

Hi,

The TLK110 is not entering into parallel detection when link partner ANEG capability is disabled.

Experiment 1:

1. In link partner ANEG is diabled.

2. In TLK phy, Write 0x3300 in to basic control reg to restart aneg.

3. wait for some delay,

4. Read basic status register, got 0x7869. Where link is not up.

Here  i am expecting parallel detection should happen and it has to enter into Half duplex with link detected.

But after power on ,Just i read basic status register. The link was up.

Experiment 2:

1. Aneg is disabled at link partner.

2. Power ON TLK, wait for some secs

3. Read Basic status register, got 0x786d, here link is up.

Parallel detection would have happened above.

Can you help me to sort it out why parallel detection not happened with Experiment 1?

  • 0
    TI__Mastermind 31600 points

    I have a few questions to help clarify the functionality:

    1. What is the link partner on the other end of the cable?  When its auto-negotiation capability is disabled, can you confirm that it is configured for 100M half-duplex?
    2. When you read the Basic Mode Status Register (BMSR), address 0x0001, could you read it multiple times and reply with the results?  The link status bit latches low so it retains information if the link has been lost since the last read.
    3. Please also include register reads of:
      1. The Auto Negotiation Advertisement Register (ANAR), address 0x0004.
      2. The Auto-Negotiation Link Partner Ability Register (ANLPAR) (BASE Page), address 0x0005.
      3. The Auto-Negotiate Expansion Register (ANER), address 0x0006

    Thanks,

    Patrick

  • 0 in reply to Patrick OFarrell
    TI__Mastermind 31600 points

    I have been tracking back through open forum posts.  Were you able to resolve this and successfully parallel detect?  If so, could you post any learnings?  If not, could you let me know what additional support is required?

    Patrick