Hi Daniel,
Since you're using MAC mode, the TSE IP ignores the value in the dev_ability register and automatically sets the value to 16’h4001. Once auto-negotiation completes, TSE IP speed will be resolved based on the value in the partner_ability. The partner_ability register is received from the link partner during the auto-negotiation process.
There are few options to check on auto negotiation:
- Make sure that both sides of the link are configured the same way.
- If one side of the link is set to auto-negotiation, make sure the other side is also set to auto-negotiation.
- If one side is set to 100/full, make sure the other side is also set to 100/full.
- Failure may happened if one side of the link has been set to 100/full, and the other side has been set to auto-negotiation
This may results in one side being 100/full, and the other side being 100/half.
- Auto negotiation must be configure in one PHY mode and one MAC mode
- Auto Negotiation completed but 2 devices run at different speed. It was due to 2 SGMII PCS are configured with Auto Negotiation in MAC mode. In SGMII AN, one PCS must be in MAC mode and the other in PHY mode
- Auto Negotiation succeeded with mismatch ability advertised.
- It happened that "SGMII bridge" option was enabled in parameter setting but SGMII ENA bit of IF_MODE register was set to '0'.
- The SGMII mode does not disabled if SGMII bridge is enabled in the parameter setting. Hence, Auto Negotiation was done in SGMII mode instead of 1000BASE-X mode. dev_ability and partner_ability registers do not take effect in SGMII mode.
Regards,
Pavee
New Contributor
