ADIN6310 custom hardware verification

Hi BW, 

Clarifying my last message,

Since this is an unmanaged PHY in relation to the switch, we recommend that you trigger the host to read the PHY, allowing the switch to speed match as necessary. 

Based on your PHY's datasheet, there does not look to be a link pin that we can connect to Px_LINK. Therefore, we can't use the switch's Px_LINK pin to trigger the host.

However, there is an MDINT pin that we can use. By connecting this interrupt pin to the host, the host can be triggered on a link-up, signalling the host to read the PHY over the switch's MDIO. The switch's Driver API, SES_ReadPhyReg(), can be used to read the PHY, which can be found in the header file, SES_switch.h, in the Driver Library.

Let me know if you'd like support with triggering the host or reading the PHY. 


Thanks, 

Ciara

Hi Ciara, 

Thanks for the clarification. I think I understand your proposal there. 

For my application, The host is going to be somewhat limited on what we will be able to with that configuration. 

So, let me ask a follow up question. If I were to swap my phys with the ADIN1300 phys, would the be able to handle the MAC speed change without another interaction from the host? The host would still do the initial configuration, of course. 

Thanks,

BW

Hi BW, 

Correct. If the ADIN1300 PHY is being used, the switch's Px_LINK can be connected to the ADIN1300's LINK_ST pin, triggering the switch on link-up to read the PHY and speed match automatically. Exactly, the host will need to load the firmware onto the switch, and then the switch will take care of managing the ADIN1300 PHY. 

Thanks, 

Ciara

Hi Ciara, 

Perfect! Thanks for all your help with this, and thank you to Catherine and Karl for your help as well! 

Thanks,

BW

Hi BW, 

You're welcome. Let us know how you get on, or if you need support. 

Thanks, 

Ciara

Hi BW, 

You're welcome. Let us know how you get on, or if you need support. 

Thanks, 

Ciara