ADIN6310 Supports IEEE 802.1AS

Hi Thejas Kumar,

Thank you for reaching out to us.

Could you please let us know the end application where you intend to use the AS2020? Additionally, are you using the Evaluation Application or the Driver API to configure the time synchronization profile?

The ADIN6310/ADIN3310 devices support IEEE 802.1AS-2020 and IEEE 1588-2019 time synchronization profiles. However, please note that currently, the ADIN6310/ADIN3310 only support the 2-step synchronization process. As a result, you will not see any option related to step selection in the configuration.

If you are using the Evaluation Application, please refer to the "TIME SYNCHRONIZATION IEEE 802.1AS" section of the Evaluation User Guide. 
If you are using the Driver APIs, refer to the "TIME SYNCHRONIZATION" section in the Driver User Guide.

Please let us know if you need further assistance.

Regards,
Himanshu

I am using the ADIN6310 board along with an LRU that acts as the Grandmaster(802.1AS) clock. When i configured port 6 of the ADIN6310 as time receiver, the grandmaster was not detected. Currently, we are testing this feature through Web UI, and plan to use APIs for this purpose later. 

Hello Thejas,

What version of 802.1AS is the Grandmaster configured for?

Are you using the web GUI in default configuration or have you made any changes? 

The ADIN6310 PTP stack supports 802.1AS 2020, but the default GUI configuration currently configures the switch for Peer-to-peer delay mechanism, so that it will also be capable to synchronize with a device running older 802.1AS 2011 version. If your Grandmaster is running Common Mean Link Delay service (CMLDS), then you need to change the configuration for the ADIN6310 to also use CMLDS -> you can do this in the Candidate page. 

Do you have anything in the path between Port 6 and the Grandmaster device? e.g. Ethernet tap? By default, the GUI configures the Mean Link Delay Threshold to be 800ns [per the IEEE 802.1AS standard], some ethernet taps can add a very large delay. If the additional delay causes the measured mean link delay  > 800ns, then it wouldn't sync. The GUI Candidate page allows user to adjust the Threshold value. Also the GUI Status page will show you what the measured mean link delay is. Could you take a screenshot of what the Candidate/Status pages are showing? 

If you have an ethernet tap in between the two devices, can you please share a capture of the traffic? Thanks in advance. 

best regards,

Catherine. 

Hello Thejas,

What version of 802.1AS is the Grandmaster configured for?

Are you using the web GUI in default configuration or have you made any changes? 

The ADIN6310 PTP stack supports 802.1AS 2020, but the default GUI configuration currently configures the switch for Peer-to-peer delay mechanism, so that it will also be capable to synchronize with a device running older 802.1AS 2011 version. If your Grandmaster is running Common Mean Link Delay service (CMLDS), then you need to change the configuration for the ADIN6310 to also use CMLDS -> you can do this in the Candidate page. 

Do you have anything in the path between Port 6 and the Grandmaster device? e.g. Ethernet tap? By default, the GUI configures the Mean Link Delay Threshold to be 800ns [per the IEEE 802.1AS standard], some ethernet taps can add a very large delay. If the additional delay causes the measured mean link delay  > 800ns, then it wouldn't sync. The GUI Candidate page allows user to adjust the Threshold value. Also the GUI Status page will show you what the measured mean link delay is. Could you take a screenshot of what the Candidate/Status pages are showing? 

If you have an ethernet tap in between the two devices, can you please share a capture of the traffic? Thanks in advance. 

best regards,

Catherine.