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.

DP83869EVM: DP83869EVM reproducible interoperability issue with Starlink Ethernet adapter (Idle Errors and RX Errors)

Part Number: DP83869EVM
Other Parts Discussed in Thread: DP83869,

Hi,

I am investigating a Gigabit Ethernet interoperability issue between a Starlink Ethernet interface and the DP83869.

Initially this was observed on a custom media converter design using two DP83869 PHYs. To eliminate hardware-specific causes, I have now reproduced the same behaviour on a DP83869EVM.

Configuration

Topology:

 

Starlink Ethernet Adapter
|
DP83869EVM
|
1000BASE-X Fiber
|
COTS Media Converter
|
PC

 

The EVM is configured such that:

 

OP_MODE_DECODE (0x01DF) = 0x0004

WhatsApp Image 2026-08-14 at 15.30.25.jpeg

With this configuration the Starlink link comes up successfully.

Relevant registers after link establishment:

 

0x0001 = 0x796D
0x000A = 0x3800
0x0011 = 0xBC02
0x01DF = 0x0004

 

The PHY negotiates:

 

1000BASE-T
Full Duplex
Auto-negotiation complete

 

Problem Description

When connected directly to Starlink:

 

Starlink
|
DP83869EVM

 

Download performance is significantly degraded.

Upload performance is much less affected.

While running a download speed test, the PHY accumulates large numbers of receive errors.

Idle Error Counter

Before speed test:

 

0x000A = 0x3800

 

After speed test:

 

0x000A = 0x38FF

 

The idle error counter saturates at 255.

RX Error Counter

Before speed test:

 

0x0015 = 0x0003

 

After speed test:

 

0x0015 = 0x1D23

 

RX errors increase substantially during download traffic.

Switch Insertion Test

When an unmanaged Gigabit switch is inserted:

 

Starlink
|
Switch
|
DP83869EVM

 

The issue disappears completely.

Before Speed Test

 

0x000A = 0x3800
0x0015 = 0x0000

 

After Speed Test

 

0x000A = 0x3800
0x0015 = 0x0000

 

Results:

 

No idle errors
No RX errors
Full throughput restored

 

Additional Information

The same behaviour was originally observed on custom hardware using DP83869 PHYs.

The issue is therefore reproducible on:

 

1. Custom DP83869 media converter
2. DP83869EVM

 

and disappears when the immediate link partner is changed from:

 

Starlink Ethernet Interface

 

to

 

Standard Gigabit Ethernet Switch

 

Question

Have there been any known DP83869 interoperability issues involving:

 

1000BASE-T receive path
DSP adaptation/equalization
Idle error accumulation
Starlink Ethernet interfaces

 

or are there any recommended debug registers, DSP diagnostics, or workaround settings that could help identify why the PHY accumulates large RX and idle error counts only when directly connected to the Starlink Ethernet interface?

Thanks.

  • Hello,

    From the diagnostic information provided, it appears that idle errors are being triggered. This is indicated via Reg 0xA. It appears that the Starlink adapter may be sending packets with lower IPG than expected to the PHY. We do have a configuration which can help with this. Can you please program Reg 0x53[3:0] to 0x3 and rerun your testing?

    Sincerely,

    Gerome