AM437x SDK 2 : Ethernet not working : PHY working; No MII Tx

pathfinder

Team,

My customer is using AM437x SDK 2.0 and having Ethernet issues. They are using DP83848JSQ PHY.

"..now have the PHY "working" in that it blinks the 100M LED and can be configured from linux. Though it seem that all MII Tx comms are non-existent (though the tx interrupts in the CPSW driver seem to fire on a regular interval). Also, using the logic analyzer I can see Rx data on the MII Rx lines."

I'm using the DP83848 driver found in the 4.3 kernel source tree. Though it should be noted that I cherry picked that driver back into the 4.1.6 kernel. Commit for that is here: https://github.com/torvalds/linux/commit/34e45ad9378c31ef2b59e8bd63d62f0ca8e719a3

dmesg bootlog info is attached.

8078.dmesg.out.txt

over 9 years ago

0 Yordan Kovachev over 9 years ago

TI__Guru**** 161600 points

Hi Marc,

As I see from the dmesg log, everything regarding mdio/mii/net looks fine, the phy is detected & initialized by the kernel and mac address is assigned.

Not sure why they don't see data on the mii tx.

What is the result of ifconfig, ifdown & ifup commands?

Also I see that they have a kernel panic, because of an L3_custom error, which you can try to overcome by following the suggestion here:

Also there is a problem with the i2c0 & the parsing of some power supplies definition.

Can you also share the full DTS file (and the included dtsi files) that is used?

Best Regards,
Yordan

0 pathfinder over 9 years ago in reply to Yordan Kovachev

TI__Genius 12790 points

Yordan,

I received response from customer, can you take a look at it? Thanks.

===========================================

Thanks for getting back to me. I've attached a few files, I'll give a explanation of each to avoid confusion.

cmdline_output*.txt: Ran ifconfig and ifup straight from boot to show the state post failed auto-negotiations with the PHY, I then call mii-diag to config eth0 to be a fixed speed (100baseTx-FD) which results in the ethernet link to come up (100Mbps Eth light starts blinking). Lastly ifconfig, ifup and ifdown were run post mii-diag config, as requested.

dts_files.zip: The full dts file and all included dtsi files

etc_network_interfaces.txt: Is the /etc/network/interfaces file in use.

Thanks for the help,

Bill

1263.dts_files.zip 1325.cmdline_output_IFUP_IFDOWN_IFCONFIG_MIIDIAG.txt 3683.etc_network_interfaces.txt

AM437x SDK 2 : Ethernet not working : PHY working; No MII Tx

0 Yordan Kovachev over 9 years ago in reply to pathfinder

TI__Guru**** 161600 points

Hi Marc,

1. Have you added the DP83848 PHY support in the defconfig file?
2. Have you tried changing the phy-mode?

Best Regards,
Yordan

0 pathfinder over 9 years ago in reply to Yordan Kovachev

TI__Genius 12790 points

Yordan,

*** I clicked by mistake 'flag this post as spam' - what do i do now?7282.dts_files.zip

I am getting their defconfig to verify PHY support.

Meantime, can you look at their dts/dtsi files ? I attached them to earlier post?

Thanks.

0 Yordan Kovachev over 9 years ago in reply to pathfinder

TI__Guru**** 161600 points

Hi Marc,

Marc DAmato said:
*** I clicked by mistake 'flag this post as spam' - what do i do now?

I see the posts in this thread, so I think it is ok, you shouldn't take any actions.

I'll have a look at the device tree files & come back to you if I find anything wrong with the settings.

Best Regards,

Yordan

0 Dhruvil Patel over 8 years ago in reply to Yordan Kovachev

Prodigy 110 points

Hi,

I am facing the similar issue, can you please post here is there is any update?

Processors

Processors forum

AM437x SDK 2 : Ethernet not working : PHY working; No MII Tx