> For the complete documentation index, see [llms.txt](https://dev.solid-run.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.solid-run.com/nxp/imx6/sbc-platform/imx6-other-articles/imx6-rev-19-and-rev-20-adin1300-phy-qualification-process.md).

# i.MX6 Rev 1.9 and Rev 2.0 ADIN1300 PHY Qualification Process

| **Date**    | **Owner**    | **Revision** | **Notes** |
| ----------- | ------------ | ------------ | --------- |
| 21 Feb 2022 | Alvaro Karsz | 1.0          |           |

## **Background**

Following SolidRun’s PCN on i.MX6 SOM Rev 1.5 migrating to Rev 1.9 and Rev 2.0, this article explains the qualification procedure that SolidRun performed to make sure the performance of Analog Devices ADIN1300 PHY is adequate and no performance / quality / stability issues are affecting any customer.

## Auto negotiation (A/N) test

ethtool was used to select the speed with A/N on.

#### **1Gbps**

```
$ ethtool -s eth0 speed 1000 duplex full autoneg on
[ 8548.041399] fec 2188000.ethernet eth0: Link is Down
[ 8551.757596] fec 2188000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
```

#### **100Mbps**

```
$ ethtool -s eth0 speed 100 duplex full autoneg on
[ 8617.585894] fec 2188000.ethernet eth0: Link is Down
[ 8620.397596] fec 2188000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
```

#### **10Mbps**

```
$ ethtool -s eth0 speed 10 duplex full autoneg on
[ 8648.151779] fec 2188000.ethernet eth0: Link is Down
[ 8650.557544] fec 2188000.ethernet eth0: Link is Up - 10Mbps/Full - flow control rx/tx
```

## Stress test

Stress test using iperf for 30 minutes.

```
$ iperf3 -c <iperf server IP> -t 1800
```

|                       |                   |                       |
| --------------------- | ----------------- | --------------------- |
| **Cable length \[m]** | **Speed \[Mpbs]** | **Number of retries** |
| 3                     | 1000              | 0                     |
| 50                    | 1000              | 0                     |
| 100                   | 1000              | 49                    |

#### Retries for 100M cable iperf

```
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-1800.00 sec  80.6 GBytes   385 Mbits/sec   49             sender
[  5]   0.00-1800.11 sec  80.6 GBytes   384 Mbits/sec                  receiver
```

## Thermal

![](/files/1MK8LGXTJ0NbNGhVPPRl)

Max. temperature in PHY (Poly 1): \~71 °C.

Max. temperature in the SOM (Poly 3): \~75°C in SoC.

{% hint style="info" %}
Thermal snapshot was taken after a weekend long iperf, without a heat-sink.
{% endhint %}

## Conclusion

Based on SolidRun’s short and long term tests, we find that Analog Devices ADIN1300 ethernet PHY meets the requirements of the datasheet and SolidRun did not observe any stability, reliability or thermal problems.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dev.solid-run.com/nxp/imx6/sbc-platform/imx6-other-articles/imx6-rev-19-and-rev-20-adin1300-phy-qualification-process.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.