OSD335x C-SiP Ethernet issue

[Sktz]

Have a custom board design using the OSD3358 C-SiP and TI DP83822 PHY, both are configured for MII.
Using u-boot and Linux, based on your RED platform with appropriate modifications.
The Ethernet interface has been working intermittently on several boards. Sometimes auto-neg works, sometimes not.
Sometimes a power cycle or reset results in a successful connection, sometimes not.
I have read thru a number of posts here but haven’t made any progress.
Can someone take a look at my log files, device tree, etc?
I’ll post whatever is requested.
I think this is a configuration problem.

[Neeraj Dantu]

Sktz,

The first thing to do here is to verify whether the design is correct. Please review your Ethernet design and/or post it here or contact us through the support channel for a review on it. See https://e2e.ti.com/support/interface/f/138/t/694453 for a design to compare against.

Please post the kernel logs of various fail cases so we can see where the fault occurs in initialization. For example, it could be that the pull-up/down configuration on the PHY address pins are not configured properly and the processor detects the PHY at a different address than what is set in the device tree.

Another possibility is that there could be EMI causing signal interference issues on your design. Take a look at this useful reference for layout guidelines on Ethernet: https://resources.pcb.cadence.com/blog/2019-mii-and-rmii-routing-guidelines-for-ethernet

Please let us know if you have any more questions.

Best,

Neeraj

[Sktz]

Neeraj,
Thanks for the response.
I had done all you suggested before posting.
Design and config are correct.

Since posting I have discovered that it is a power-on reset problem between the OSD3358 C-SIP and the TI DP83822 PHY.
It is the same situation as mentioned in this forum poast:

Ethernet does not work without active UART session

See Reply #9276.
For now I have a jumper and will hold the PHY in reset longer and add a GPIO for reset control.
I would like to understand this issue better though and will continue to investigate.

At the moment we are now debugging the USB interface, which also seems to be a config/driver issue.
I have attached the boot log after a successful DHCP session using the PHY reset jumper coming out of power-up.
Can you review to see if there are issues we are missing?

Thanks again.
Steve

• This reply was modified 4 years, 9 months ago by Sktz.

Attachments:

1. Boot_Log_Board4_DHCP_Good_with_Jumper_on_PHYreset.txt

[Sktz]

While this Ethernet/MII/PHY reset issue is not a priority at the moment and we have a fix, I would like to understand what the poblem is.
The USB port not working is a higher priority and I will create a dedicated post.
Steve

[Neeraj Dantu]

Steve,

Thanks for the update. The bootlogyou attached looks good. We will respond to the USB issue on the post.

Best,

Neeraj

[Sktz]

Thanks Neeraj.
I would like to understand the issue with the MII interface and the PHY reset but it is not a pressing issue at this time.

Thanks for reviewing the log file.

Steve

[Author]

Posts