From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-wr1-f51.google.com ([209.85.221.51]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lMZ7q-0004rB-Fa for distrokit@pengutronix.de; Wed, 17 Mar 2021 17:34:28 +0100 Received: by mail-wr1-f51.google.com with SMTP id e9so2472972wrw.10 for ; Wed, 17 Mar 2021 09:34:26 -0700 (PDT) MIME-Version: 1.0 References: <1690512.roPDE2jfQB@ada> In-Reply-To: <1690512.roPDE2jfQB@ada> From: Jon Ringle Date: Wed, 17 Mar 2021 12:34:13 -0400 Message-ID: Subject: Re: [DistroKit] ethernet on SAMA5D2-SOM1-EK1 List-Id: DistroKit Mailinglist List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0279880906==" Errors-To: distrokit-bounces@pengutronix.de Sender: "DistroKit" To: Alexander Dahl Cc: distrokit@pengutronix.de --===============0279880906== Content-Type: multipart/alternative; boundary="0000000000004fb9ab05bdbe0eed" --0000000000004fb9ab05bdbe0eed Content-Type: text/plain; charset="UTF-8" On Wed, Mar 17, 2021 at 10:30 AM Alexander Dahl wrote: > Hello, > > for testing some new mikroBUS modules I got a dusty SAMA5D2-SOM1-EK1 from > our > shelf and build recent DistroKit master for it. Nice thing: SD card works > in > both ports. However ethernet does not work correctly out of the box. :-/ > > In barebox shell it uses a random mac address (the real one is in a small > eeprom on the SoM), dhcp and ping successful. > > In Linux (5.11.4) however it also uses a random mac address and > furthermore > either the micrel ethernet phy is not found at all or the link can not be > set > to up. Tried both nmtui and raw iproute2 command. > Hey Alexander, I don't know if this will apply to you with sama5d2-som1-ek1, but we have a board that is based on sama5d2-som1 that has ksz8081rna phy, which based on the strap on options configured via pull up/down is on phy 4. We are in the process of updating from linux-4.14 to linux-5.4. A problem that was noticed on update to linux-5.4 was that the Ethernet port stopped working after power on boot, but would work after a subsequent soft reboot. I noticed that the phy address used in arch/arm/boot/dts/at91-sama5d27_som1.dtsi didn't match the one for our board in either the linux-4.14 or linux-5.4 tree, but we never noticed a problem when we did initial bring up of our board with linux-4.14 a couple years ago. When I fixed the device tree to use the correct phy address 4 for our board. The problem went away and the Ethernet port now works properly on linux-5.4. -Jon --0000000000004fb9ab05bdbe0eed Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, Mar 17, 2021 at 10:30 AM Alex= ander Dahl <ada@thorsis.com> w= rote:
Hello,

for testing some new mikroBUS modules I got a dusty SAMA5D2-SOM1-EK1 from o= ur
shelf and build recent DistroKit master for it. Nice thing: SD card works i= n
both ports. However ethernet does not work correctly out of the box. :-/
In barebox shell it uses a random mac address (the real one is in a small <= br> eeprom on the SoM), dhcp and ping successful.

In Linux (5.11.4) however it also uses a random mac address and furthermore=
either the micrel ethernet phy is not found at all or the link can not be s= et
to up. Tried both nmtui and raw iproute2 command.

=
Hey Alexander,

I don't know if this= will apply to you with sama5d2-som1-ek1, but we have a board that is based= on sama5d2-som1 that has ksz8081rna phy, which based on the strap on optio= ns configured via pull up/down is on phy 4.
We are in the process= of updating from linux-4.14 to linux-5.4. A problem that was noticed on up= date to linux-5.4 was that the Ethernet port stopped working after power on= boot, but would work after a subsequent soft reboot.
I noticed t= hat the phy address used in arch/arm/boot/dts/at91-sama5d27_som1.dtsi didn&= #39;t match the one for our board in either the linux-4.14 or linux-5.4 tre= e, but we never noticed a problem when we did initial bring up of our board= with linux-4.14 a couple years ago. When I fixed the device tree to use th= e correct phy address 4 for our board. The problem went away and the Ethern= et port now works properly on linux-5.4.

-Jon
--0000000000004fb9ab05bdbe0eed-- --===============0279880906== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ DistroKit mailing list DistroKit@pengutronix.de --===============0279880906==--