The clocks on my custom design are as follows:
- SYSCLK is 153.6 MHz
- ARMCLK is 122.88 MHz
- DDR3A and DDR3B are 100 MHz
- SRIOSGMIICLK is 156.25 MHz
Right now I am debugging the ethernet interface, in the Uboot environment. We are using the same Marvell 88E1111 PHY and SRIOSGMIICLK values in our design as the EVM. As such, I left the CONFIGs the same:
/* Network Configuration */
#define CONFIG_ETH_PHY_MARVEL_88E1111
#define CONFIG_DRIVER_TI_KEYSTONE_NET
#define CONFIG_MII
#define CONFIG_BOOTP_DEFAULT
#define CONFIG_BOOTP_DNS
#define CONFIG_BOOTP_DNS2
#define CONFIG_BOOTP_SEND_HOSTNAME
#define CONFIG_NET_RETRY_COUNT 32
#define CONFIG_NET_MULTI
#define CONFIG_GET_LINK_STATUS_ATTEMPTS 5
#define CONFIG_SYS_SGMII_REFCLK_MHZ 312
#define CONFIG_SYS_SGMII_LINERATE_MHZ 1250
#define CONFIG_SYS_SGMII_RATESCALE 2
One difference is I am using the SGMII2 interface instead of 0 or 1 like the EVM. What changes might I have to make for this difference? I noticed the addition of eth2 and eth3 in eth_priv_t eth_priv_cfg[] which is in board.c and one difference is .sgmii_link_type =SGMII_LINK_MAC_MAC_FORCED versus .sgmii_link_type = SGMII_LINK_MAC_PHY. But I'm not sure what the differences between those two are in relation to my issue. Uboot seems to initialize all 4 interfaces just fine and gets to the command prompt, but if I try to do something like "ping", there is no response.
Any thoughts on how to attack this?