• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 280 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.

NET wire

Frank Lee96
Intellectual 830 points

Hi TI,

1、There are two type net wire named A class(direct connect) and B class(crossover connect),I want to know how to select them,where I should use A type wire and where I should use B type wire?

2、And the net wire can be divided into different kinds of types like CAT4,CAT5 and so on,but how to select them when needed?

3、Recently I meet a problem with my circuit,my embeded MCU connect to a net chip and connect to interchanger by net wire and the interchanger connect to my PC.

At first,the MCU can communicate with PC,then I pull out the net wire between the net chip and the interchanger,next insert the net wire back,then I find the MCU CAN'T commnuicate with PC!!!! I have not find the reason,can you give me some advice?

Best regards,

Frank

  • 0
    TI__Mastermind 18425 points
    HI Frank,

    Which TI product is used in your system? The problem that you are describing is solved by a feature called Auto-MDIX. This is where the Ethernet PHY can sense which channel is being used as transmit and which is receive when communicating with a link partner. The Ethernet PHY then automatically adjusts its own transmit and receive channels so that there is not conflict during communication. Most of our products have this feature and its enabled by default. Customers can turn it off in their application. If this feature is supported on the PHY used in your system then you can use both Direct and Crossover cable.
    For 10/100/1000 Ethernet application it is recommended to use Cat5e cable.
    The problem that you described with your PC can happen due to higher layer protocols and maybe out of scope for this forum.

    -Regards,
    Aniruddha