Hello K606
This is Rolando and will help you with this issue. Can you provide more details of the Ethernet setup that you have? Are you using an HPS emac? Are you working on a custom board or a dev kit? Signal Tap is used mainly when your have a component in the fabric design (maybe a MAC in the fabric), but if you are using the HPS emac, then it may not be very useful.
I think you can increase the verbosity of your kernel to see if there is any idea about what is going on?. You can doit from the kernel command line by adding the loglevel=7 parameter.
When using HPS emac, the issue that are observed normally are addressed by configs in .config or device tree parameters.
You need to identify which emac is the one that you are using and then identify the node in the device tree that corresponds to this emac.
Then, ensure that the node is enabled and that the correct interrupts are associated with this emac.
The emac that you are using, need to be connected to a PHY. Check that a sub-node in the device tree also exist for the PHY. This needs node must be referenced in the emac node. In the emac node you need to indicate the interface that will be used with the PHY (rgmii, sgmii). The PHY is controlled by the HPS through a mdio interface (kind of i2c interface) which has an address, this address needs to be indicated in the PHY node.
For the emac and the PHY, the build of the corresponding drivers need to be enabled through the corresponding CONFIG in the .config.
Thanks
Rolando