• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 32 subscribers
  • Views 264 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

DP83822I: Errors and Forward Errors

Brian Wang0928
Genius 12070 points
Part Number: DP83822I
Other Parts Discussed in Thread: TLK111, TLK105, DP83826E

Here are some of questions with DP83822I need to be clarify about the error package during communication according to 14.2 description as diagram below. 

Q1. I would like to know that how to deal with the packets in DP83822I to be sent/received with extra nibble?

 

Q2. In EtherCAT an_phy_selection_guidev2.7.pdf,

TLK105~TLK111 have setting restrictions on Forwarded RX Error (0x308) (Disable Odd nibble detection via MII management, otherwise Forwarded RX errors cannot be detected.), I would like to know that is this setting relevant to our problem? And how to set it through the MII management?

 

Q3. As Question 2 says, TLK105~TLK111 have setting restrictions on Forwarded RX Error (0x308), but DP83822 has no additional setting description for 0x308 register, please help to confirm this point.

 

application: Comm. module for AC inverter.

  • +1
    TI__Expert 8640 points

    Hi Brian,

    TLK PHYs and DP83822 are different architectures.

    Can you please explain the issue being noticed ? Are RX_errors being triggered on the DP83822 PHY ?

    Regards,
    Rahul

  • 0 in reply to Rahul
    TI__Genius 12070 points

    Thanks. 

    We connect EK1110 and 2 customer Cards like below.

    When noise is happened, Card 1 and EK1110 should add 0x308 counter.

    However, the observed phenomenon is that the port 1 of Card 1 and EK1110 both increase 0x302 and 0x308 unchanged.

    I would like to ask how the DP83822 will handle the Forwarded RX Error packet (with nibble) when sending and receiving, and whether it will cause this phenomenal possibility, thanks.

  • 0 in reply to Brian Wang0928
    TI__Expert 8640 points

    Hi Brian,

    Thank you for the clarification.

    This Forwarded RX errors cannot be detected phenomenal is only for the TLK devices as mentioned, DP83822 shouldn't cause this.

    The error packets will be detected and forwarded.

    Using Register 0x0015 of PD83822, we can check the RX errors counter.

    Regards,
    Rahul

  • 0 in reply to Rahul
    TI__Genius 12070 points

    Thanks Rahul.

    1. Does DP83822 do any extra processing when there are additional 4-bits nibble packets to send out? Or it just sends this packet directly?

    2. In “How and Why to Use the DP83826E for EtherCAT Application”, the page 7 suggestes Disable Odd-nibble detection.

    The DP83822 default is Enable Odd-nibble detection.

    Please explain the difference in between in the case of EtherCAT Forwarded Error frame (with nibble), and whether the different settings could cause the error situation that we tell?

    Regards

    Brian

  • 0 in reply to Brian Wang0928
    TI__Expert 8640 points

    Hi Brian,

    Please let me review this and update you early next week.

    Regards,
    Rahul

  • 0 in reply to Rahul
    TI__Expert 8640 points

    Hi Brian,

    Brian Wang0928 said:
    However, the observed phenomenon is that the port 1 of Card 1 and EK1110 both increase 0x302 and 0x308 unchanged.

    In both EK1100 and card 1, they detected invalid packet format because of noise and that got triggered.

    I would request customer to Disable the odd nibble as mentioned in 826 EtherCAT application note and provide their feedback.

    Regards,
    Rahul

  • 0 in reply to Rahul
    TI__Expert 8640 points

    Hi Brian,

    Can you also please tell me how you are injecting noise between the cards to reproduce the packet errors ?

    Thanks,
    Rahul