From: Ron Eggler <ron.eggler@mistywest.com>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: netdev@vger.kernel.org
Subject: Re: Unable to TX data on VSC8531
Date: Mon, 1 May 2023 13:34:11 -0700 [thread overview]
Message-ID: <2c2bade5-01d5-7065-13e6-56fcdbf92b5a@mistywest.com> (raw)
In-Reply-To: <20230501064655.2ovbo3yhkym3zu57@soft-dev3-1>
Hi Horatiu,
[snip greetings]
> I've posted here previously about the bring up of two network interfaces
> on an embedded platform that is using two the Microsemi VSC8531 PHYs.
> (previous thread: issues to bring up two VSC8531 PHYs, Thanks to Heiner
> Kallweit & Andrew Lunn).
> I'm able to seemingly fully access & operate the network interfaces
> through ifconfig (and the ip commands) and I set the ip address to match
> my /24 network. However, while it looks like I can receive & see traffic
> on the line with tcpdump, it appears like none of my frames can go out
> in TX direction and hence entries in my arp table mostly remain
> incomplete (and if there actually happens to be a complete entry,
> sending anything to it doesn't seem to work and the TX counters in
> ifconfig stay at 0. How can I further troubleshoot this? I have set the
> phy-mode to rgmii-id in the device tree and have experimented with all
> the TX_CLK delay register settings in the PHY but have failed to make
> any progress.
> Some of the VSC phys have this COMA mode, and then you need to pull
> down a GPIO to take it out of this mode. I looked a little bit but I
> didn't find anything like this for VSC8531 but maybe you can double
> check this. But in that case both the RX and TX will not work.
> Are there any errors seen in the registers 16 (0x10) or register 17
> (0x11)?
Good point rewgarding the COMA mode, I have not found anything like it.
The RGMII connectivity should be pretty straight forward per the
datasheet, TX0-TX4, TX_CLK, TX_CTL, RXD0-RXD4, RX_CLK & RX_CTL.
Not sure if you've seen this in the subthread that is ongoing with
Andrew Lunn but as part of it, I did invoke the mii-tool and got a
pretty printout of the PHY registers, see below:
# mii-tool -vv eth0
Using SIOCGMIIPHY=0x8947
eth0: negotiated 100baseTx-FD, link ok
registers for MII PHY 0:
1040 796d 0007 0572 01e1 45e1 0005 2801
0000 0300 4000 0000 0000 0000 0000 3000
9000 0000 0008 0000 0000 0000 3201 1000
0000 a020 0000 0000 802d 0021 0400 0000
product info: vendor 00:01:c1, model 23 rev 2
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD
10baseT-FD 10baseT-HD
advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
link partner: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD
10baseT-FD 10baseT-HD flow-control
Alternartively, the registers can be read with phytool also:
# phytool read eth0/0/0x10
0x9000
# phytool read eth0/0/0x11
0000
--
Ron
next prev parent reply other threads:[~2023-05-01 20:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-30 14:08 Unable to TX data on VSC8531 Ron Eggler
2023-04-30 14:23 ` Andrew Lunn
2023-05-01 19:57 ` Ron Eggler
2023-05-01 20:12 ` Andrew Lunn
2023-05-01 20:23 ` Ron Eggler
2023-05-01 6:46 ` Horatiu Vultur
2023-05-01 20:34 ` Ron Eggler [this message]
2023-05-02 7:11 ` Horatiu Vultur
2023-05-02 20:16 ` Ron Eggler
2023-05-02 20:50 ` Horatiu Vultur
2023-05-04 19:25 ` Ron Eggler
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=2c2bade5-01d5-7065-13e6-56fcdbf92b5a@mistywest.com \
--to=ron.eggler@mistywest.com \
--cc=horatiu.vultur@microchip.com \
--cc=netdev@vger.kernel.org \
/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