S32G274 PFE MDIO clock is not observed

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

S32G274 PFE MDIO clock is not observed

Jump to solution
1,899 Views
yellapu_anishkh
Contributor IV

Hi,

I am using a custom hardware based on NXP S32G274 SoC.

Using PFE0 and PFE1 to connect to PHY and Ethernet Switch.

PFE0 --> RGMII --> SJA1105 Ethernet Switch  

                            one port from switch for data  --> PHY (88EA1512)

                            MDIO connection from PFE0 for config   --> PHY (88EA1512)

PFE1 --> SGMII --> Ethernet Switch

                          PFE1 MDIO --> PHY

I have done necessary changes in dts to support the same.

Please find the kernel log below.

root@s32g274acustom:~# dmesg | grep -i pfe0
[ 5.909358] 000: pfeng 46000000.pfe: pfe0 linked to EMAC 0
[ 5.909389] 000: pfeng 46000000.pfe: TX clock tx_rgmii for pfe0 installed
[ 6.178686] 000: pfeng 46000000.pfe pfe0: registered
[ 6.186098] 000: pfeng 46000000.pfe pfe0: setting MAC addr: 00:01:be:be:ef:11
[ 6.186350] 000: pfeng 46000000.pfe pfe0: Register HIF client pfe0 on logif 0
[ 6.186359] 000: pfeng 46000000.pfe pfe0: PTP HW addend 0x80000000, max_adj configured to 46566128 ppb
[ 6.186898] 000: pfeng 46000000.pfe pfe0: Registered PTP HW clock successfully on emac0
[ 6.207787] 001: mdio_bus PFEng Ethernet MDIO.pfe0: MDIO device at address 2 is missing.
[ 6.208057] 001: mdio_bus PFEng Ethernet MDIO.pfe0: MDIO device at address 3 is missing.
[ 6.208324] 001: mdio_bus PFEng Ethernet MDIO.pfe0: MDIO device at address 4 is missing.
[ 6.208592] 001: mdio_bus PFEng Ethernet MDIO.pfe0: MDIO device at address 5 is missing.
[ 6.212186] 001: mdio_bus PFEng Ethernet MDIO.pfe0: MDIO device at address 8 is missing.
[ 6.212455] 001: mdio_bus PFEng Ethernet MDIO.pfe0: MDIO device at address 9 is missing.
[ 6.212728] 001: mdio_bus PFEng Ethernet MDIO.pfe0: MDIO device at address 10 is missing.
[ 6.212997] 001: mdio_bus PFEng Ethernet MDIO.pfe0: MDIO device at address 11 is missing.
[ 6.213265] 001: mdio_bus PFEng Ethernet MDIO.pfe0: MDIO device at address 12 is missing.
[ 6.213532] 001: mdio_bus PFEng Ethernet MDIO.pfe0: MDIO device at address 13 is missing.
[ 6.213800] 001: mdio_bus PFEng Ethernet MDIO.pfe0: MDIO device at address 14 is missing.
[ 6.214066] 001: mdio_bus PFEng Ethernet MDIO.pfe0: MDIO device at address 15 is missing.
[ 6.732261] 000: pfeng 46000000.pfe pfe0: configuring for fixed/rgmii link mode
[ 6.732275] 000: pfeng 46000000.pfe pfe0: Set TX clock to 125M
[ 6.732554] 000: pfeng 46000000.pfe pfe0: Link is Up - 1Gbps/Full - flow control off
[ 7.180752] 000: IPv6: ADDRCONF(NETDEV_CHANGE): pfe0: link becomes ready

From kernel log there is no error, but when trying to configure phy, ID itself is not detecting.

Upon probing MDIO clock, it is observed no clock on the line, what can cause MDIO clock not to observe on this bus. As the parent will be pfe_mac0.

Any support here will be highly appreciated.

Thank You

#S32G

#PFE

 

I am having S32G-VNP-EVB, where able to see MDIO clock on PFE1, when i try to configure PFE0 as RGMII and observe clock, there is an issue with phy access.

root@s32g274aevb:~# dmesg | grep -i pfe10
[ 6.137873] 003: pfeng 46000000.pfe: pfe0 linked to EMAC 0
[ 6.137914] 003: pfeng 46000000.pfe: TX clock tx_rgmii for pfe0 installed
[ 6.424818] 003: pfeng 46000000.pfe pfe0: registered
[ 6.432232] 003: pfeng 46000000.pfe pfe0: setting MAC addr: 00:01:be:be:ef:11
[ 6.432484] 003: pfeng 46000000.pfe pfe0: Register HIF client pfe0 on logif 0
[ 6.432492] 003: pfeng 46000000.pfe pfe0: PTP HW addend 0x80000000, max_adj configured to 46566128 ppb
[ 6.433025] 003: pfeng 46000000.pfe pfe0: Registered PTP HW clock successfully on emac0
[ 7.050751] 002: pfeng 46000000.pfe pfe0: could not attach PHY: -22
[ 7.050761] 002: pfeng 46000000.pfe pfe0: Error connecting to the phy: -22

 

 

0 Kudos
Reply
1 Solution
1,828 Views
yellapu_anishkh
Contributor IV

Hi,

I have done the pinmux changes and serdes config from u-boot.

One strange observation once i upgrade to BSP33, this issue got resolved, without much changes.

Checking what exactly resolved in BSP33.

View solution in original post

0 Kudos
Reply
3 Replies
1,823 Views
MayanksPatel
NXP Employee
NXP Employee

Hi Anish,

Thank you for sharing the results here.

In BSP33, PFE Drivers were changed and upgraded.

You can create a new case in case of any queries in the future.

Can you please close this case if your issue has been resolved?

 

Thanks,

Mayank s Patel

 

0 Kudos
Reply
1,841 Views
MayanksPatel
NXP Employee
NXP Employee

Hi Anish,

Hope you are doing well.

Can you please share the changes you did in dts or in BSP for this?

 

Thanks,

Mayank s Patel

0 Kudos
Reply
1,829 Views
yellapu_anishkh
Contributor IV

Hi,

I have done the pinmux changes and serdes config from u-boot.

One strange observation once i upgrade to BSP33, this issue got resolved, without much changes.

Checking what exactly resolved in BSP33.

0 Kudos
Reply