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.

DP83TC811R-Q1: FCS & Jabber Errors and Compatibility with other devices.

Part Number: DP83TC811R-Q1
Other Parts Discussed in Thread: DP83TC811

Hi team,

My customer use PHY DP83TC811R-Q1, connect with Marvell 88q2112 revA2. After power on, it will report “FCS & Jabber Errors“ as below:

They tried three methods could solve it:

1.Replug the PHY cable interface。

2.Activate the Marvel's system interface loopback can solve it, the information after activating loopback is as follows:

  

3.Switch PHY speed from 100Mbps to 1000Mbps, and then switch back, the problem can also eliminated.

Their question is:

1. Have other users of DP83TC811 had the same problem?

2.Does it match marvell 88q2112? Is there any related match test report?

Thanks!

Colin

  • Hello Colin,

     I suspect if customer can force Marvel device to be in 100BT1 mode (as 811 is 100BT1 only device) and then start the link-up, he may not see any error. Can we try this?

    --

    Regards,

    Vikram

  • Hello Vikram and Colin,

    I'm from a sensor company who uses TI PHY DP83TC811R-Q1.

    I will describe the issue in detail. We use TI PHY DP83TC811R-Q1(100BT1 only)  and our link partner is Marvell 88q2112 revA2 (100/1000 BT1).

    1) If TI PHY connects to Marvel PHY 1000BT1 at first, no link. Then switch the speed from 1000 to 100, link is OK but FCS & jabber erros occur and no data transfer. After that, Swith again to 100M or Replug ethernet cable, or reset Marvel PHY, any of this method can make the link OK again. 

    2) If TI PHY connects to Marvel PHY 100BT1 at first, nothing wrong happens (No matter whether you switch from 100 to 1000 to 100, reset, or replug, after that) 

    Forcing Marvel to be in 100BT1 mode can exactly solve the problem but it needs to change the resister of Marvel device. Our customer who uses Marvel refused to change HW board. So we want to know the root cause of the link-up but no data transfer issue. Also we hope to find why we need to configure to 100BT1 at least twice.

    The test results are shown as below:
    Step\status Link Data Transfer  register<0x0001> register<0x018B> register<0x0133>  register<0x0198>
    Step 0  Power up LiDAR (TI Phy) /
    Step 1 Connected to 1000M Marvel PHY NOK NOK 0x61 0x1000 0x4200 0x1810
    Step 2 Connected to 100M Marvel PHY OK NOK 0x65 0x1000 0x4100 0x0810
    Step 3 Option 1: PHY software reset OK OK 0x65 0x1000 0x4100 0x1010
    Option 2: replug the ethernet cable between TI & Marvel OK OK 0x65 0x1000 0x4300 0x1810
    Option 3: Power off and on Marvel OK OK 0x65 0x1000 0x4300 0x1810
    In each test case, step0~step2 are the same. In step3, we conducted 3 different tests and all the data transfer results are OK.
    Because the key bits that are changed in register<0x0133> and register<0x0198> are reservedaccording to the user Manual of TI DP83TC811R-Q1, 
    Could you please explain the cause of why Data Transfer in Step 2 is NOK based on the register we read ?

    Thank you for your support!

  • Hello,

    We have been in touch on emails and gave clarification there. I will keep on replying to your further queries on email and update here later.

    --

    Regards,

    Vikram