S32G274A SGMII Interface

[gopalakrishna]

One of custom board design we are using S32G274A processor, a 1000BASE-T1 PHY interfacing over the SGMII interface details,

Broadcom Part No : BCM89885MA0BWMLG (

The Broadcom PHY chip auto-negation is enabled, configured in Advertise 1000BASE-T1 and 100BASE-T1 secondary.

As of now, processor able to detect the PHY but ping is not coming. 

Please let us reasons for ping is not coming.

Thanks.

Regards,

Gopala

[Daniel-Aguirre]

Hi,

Which BSP version are you using? Which interface are you using?

Can you share a full boot log about the behavior you are seeing? Under the log, help us adding the hwconfig you have configured.

Since this is a custom board, we can recommend either opening a ticket or contacting your local NXP representative/FAE/DFAE, given that we are unable to reproduce the specific behavior you are seeing. We do apologize.

Please, let us know.

[gopalakrishna]

Hi,

Currently we are able to read and write all the registers from SGMII and 1000/100Base-T1 register and able to load the Phy driver that support Clause 45.

The issue that we are facing currently is that the PHY is not able to detect the link up status on plugging in of the ethernet cable.

Currently we are using the Generic Linux phy driver as mentioned below

https://elixir.bootlin.com/linux/latest/source/drivers/net/phy/phy-c45.c

Can you suggest the Linux driver which is specific for BCM89885 phy (Linux version used is 5.10.41).

PHY Interface to Processor:

SERDES1_LANE1 (PFE1)

SERDES1_LANE0 (PFE0)

These are interfaces we are using. 

Based on Clause 45 and we are able to read the SGMII Register set after doing the register write as shown in attached image also attached the register value that we could able to read from PHY(SGMII_reg_read.txt).

[Daniel-Aguirre]

Hi,

Thanks for your feedback.

On regards of the following comment:

"Can you suggest the Linux driver which is specific for BCM89885 phy (Linux version used is 5.10.41)."

Under this specific channel, we understand that NXP does not provide any drivers from a different company (in this case, we understand it is a Broadcom PHY). We can recommend contacting your PHY supplier for them to provide further comments on this. We do apologize.

As for the overall description, we understand that the S32G interfaces "correctly" with the respective PHY. We also understand that the problem is related to the PHY itself, not the MAC, for which we can again recommend contacting your PHY supplier. We do apologize.

Please, let us know.