All-
Our custom 6678 board is based on the EVM 6678 reference design but has two Marvell 88E1111 PHY devices (PHY1 connected to SGMII0 and PHY2 connected to SGMII1). Currently we need to boot Linux, and later SYSBIOS. We're using the most recent C66x Linux from GITHUB (git://linux-c6x.org/git/linux-c6x.git) and we're up to date on all C66x Linux documentation and e2e forum posts
We use TFTP boot, which works well. During Linux bring-up, we use DHCP and NFS as our root file system. However, for the new board, we are seeing response to DHCP packets sent from ETH0 received back on ETH1, which are thus discarded in ipconfig.c *.
My concern is there is low-level Linux kernel code we need to change to support boot on SGMII0, which is the default configuration for the EVM. If there an EVM project or other reference design or app note for SGMII0 boot? I think if we could compare EVM boot from SGMII0 then we could find the issue on our board.
Thanks.
-Jeff
Signalogic
* The discard occurs near line 966:
/* Is it a reply to our BOOTP request? */
if (b->op != BOOTP_REPLY || b->xid != d->xid) {
if (net_ratelimit()) printk(KERN_ERR "DHCP/BOOTP: Reply not for us, " "op[%x] xid[%x]\n", b->op, b->xid);
goto drop_unlock;
}