openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Troy Lee <troy_lee@aspeedtech.com>
To: Graeme Gregory <quic_ggregory@quicinc.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: RE: AST2600 EVB eth0 (MAC1) Issue
Date: Fri, 24 Sep 2021 03:32:10 +0000	[thread overview]
Message-ID: <HK0PR06MB21457F237946252F810F07098AA49@HK0PR06MB2145.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <296f8f59-c6a5-5a1a-2567-63c7845e53d3@quicinc.com>

Hi Graeme,

We'd like to ask you to dump SCU registers (0x1e6e2000 ~ 0x1e6e2fff) with your current image, then we could check the mac clock delay is correctly set. 
You could use UART debug controller (datasheet section 11) if devmem is not available.

Thanks,
Troy Lee

> -----Original Message-----
> From: Graeme Gregory <quic_ggregory@quicinc.com>
> Sent: Friday, September 24, 2021 5:23 AM
> To: Troy Lee <troy_lee@aspeedtech.com>; OpenBMC Maillist
> <openbmc@lists.ozlabs.org>
> Subject: Re: AST2600 EVB eth0 (MAC1) Issue
> 
> On 23/09/2021 10:09, Troy Lee wrote:
> > Hi Gaeme,
> >
> > Which soc revision and evb board revision are you using?
> > Can you try to use phy-mode = "rgmii-rxid" for eth0/1 in your dts?
> >
> > Thanks,
> > Troy Lee
> 
> Hi Troy,
> 
> Soc Rev:-
> 
> U-Boot 2019.04-00083-ge5902174d9-dirty (Sep 22 2021 - 15:10:03 +0000)
> 
> SOC: AST2600-A1
> 
> 
> EVB Rev:-
> 
> AST2600-DDR4 EVB V1.4
> 
> 
> phy-mode = "rgmii-rxid" instead of "rgmii" improves the issue and I now get
> DHCP on that interface, but packet loss is still hight compared to
> eth1 (MAC2).
> 
> eth0
> ping -f 192.168.222.119
> PING 192.168.222.119 (192.168.222.119) 56(84) bytes of data.
> ................................................................................................................
> ................................................................................................................
> .............................................................................................^C
> --- 192.168.222.119 ping statistics ---
> 597 packets transmitted, 330 received, 44.7236% packet loss, time 6775ms
> rtt min/avg/max/mdev = 0.078/809.845/3266.263/1099.208 ms, pipe 205,
> ipg/ewma 11.367/30.024 ms
> 
> eth1
> ping -f 192.168.222.30
> [sudo] password for ggregory:
> PING 192.168.222.30 (192.168.222.30) 56(84) bytes of data.
> .^C
> --- 192.168.222.30 ping statistics ---
> 50591 packets transmitted, 50590 received, 0.00197664% packet loss, time
> 5550ms rtt min/avg/max/mdev = 0.083/0.105/0.816/0.004 ms, ipg/ewma
> 0.109/0.104 ms
> 
> Thanks
> 
> Graeme
> 
> >> -----Original Message-----
> >> From: openbmc <openbmc-
> >> bounces+troy_lee=aspeedtech.com@lists.ozlabs.org> On Behalf Of
> Graeme
> >> Gregory
> >> Sent: Wednesday, September 22, 2021 11:49 PM
> >> To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
> >> Subject: AST2600 EVB eth0 (MAC1) Issue
> >>
> >> Hi,
> >>
> >> I know A0 versions of the AST2600 had an issue where eth0 was not
> >> working, but the errata indicates this is fixed in later revisions.
> >>
> >> I am seeing an issue on the EVB board though where eth0 (MAC1) is not
> >> functional. The other three ports all function as expected.
> >>
> >> On my DHCP host machine I can see DHCP requests from the AST2600,
> and
> >> replies are sent. Looking at /proc/interrupts it looks very much like
> >> no IRQs are ever generated for incoming packets.
> >>
> >> Thanks
> >>
> >> Graeme
> >>

  reply	other threads:[~2021-09-24  3:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22 15:49 AST2600 EVB eth0 (MAC1) Issue Graeme Gregory
2021-09-23  9:09 ` Troy Lee
2021-09-23 21:22   ` Graeme Gregory
2021-09-24  3:32     ` Troy Lee [this message]
2021-09-24 13:12       ` Graeme Gregory

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=HK0PR06MB21457F237946252F810F07098AA49@HK0PR06MB2145.apcprd06.prod.outlook.com \
    --to=troy_lee@aspeedtech.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=quic_ggregory@quicinc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).