Hi there,
I am currently evaluating a design that utilizes the NXP platform #i.MX8Mini processor. However, I have encountered a problem with the Gigabit Ethernet after a few months of usage with prototype boards. Please refer to the following pictures for a better understanding of the connection.
The issue is that although Gigabit communication appears to be established between my board and the Ethernet switch, it refuses to function. In contrast, 10/100-T base communication appears to be working fine. Upon measuring the net_rgmii_txc signal, it is evident that the signal has a 64% duty cycle, which falls outside the acceptable range specified in other specifications. I would like to clarify that the measurement was taken on the pad (AG24), and the trace is entirely cut off from the PHY.
Currently, we suspect that the problem may be related to a broken pad/CPU peripheral block/clock source, or an unoptimized firmware setting. I would appreciate any support you can provide regarding this issue.
Thank you.
Hi @Invent_Piano,
I hope you are doing well.
Please help me to answer a few queries as listed below:
1. Are you observing the same behavior on all custom boards?
2. If I understood correctly, the RGMII was working fine before and the issue is being faced now. Please correct me if I am wrong.
3. The clock waveform doesn't look to be in a good shape. Do you have the clock waveform captured when the RGMII was working fine previously?
Since the 10/100-T base communication is working fine, I suspect the issue is related to the clock.
Thanks & Regards,
Ritesh M Patel
Hi Ritesh, @riteshmpatel
Thank you very much for the quick reply.
the boards worked well for periods of more than a month before they became problems. and we have clock signals measured in the picture below on the boards working well.
Hi @Invent_Piano,
I assume that Hardware and Firmware configurations are the same for all 40 boards.
I suspect, this issue could be due to the following mentioned couple of factors:
1. There might be a possibility that the processor might have been operated outside the operating range.
2. Improper handling or mechanical stress.
Thanks & Regards,
Ritesh M Patel