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.

DP83620 - Link Detection Problems with short cables

Other Parts Discussed in Thread: DP83620

Hello

 

I am using the DP83620 in an application with Ethercat Slaves. On every Ethercat Slave there are two DP83620 used. Now we have some serious problems which only seem to occur when we are using short cables (< 0.5m) to connect our Ethercat Slaves. Often the DP83620 needs a very long time until it detects a link (up to 30s or more after reset was released). When we use long cables the link is established after 1-2 seconds.

Has anyone had similar problems? My error suggestion is that the DP83620 has troubles with the Auto-Negotiation and or the AUTO-MDIX function. As suggested by Ethercat the DP83620 is configured as follows:

- PHY address 16

- Auto-Negotiation enabled, advertised -> 100BASE-TX, FullDuplex

- CLK_OUT disabled

- FX disabled

- LED Config, Mod3 1

- MII Mode selected

- Phy Control Frame disabled

 

I used a scope to measure the LED_LINK signal.


- CH1: LED_LINK signal of DP83620, Ethercat Slave 5, Port 0 (Input)

- CH2: /RESET signal of DP83620, Ethercat Slave 5, Port 0 (Input)

- CH3: LED_LINK signal of DP83620, Etherct Slave 4, Port 1 (Output)

 

Once the link is established the connection works fine.

 

Thomas