PTP sync mgbe3_0

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.8.1
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
1.9.3.10904
other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

We would like to ptp sync a device connected to the mgbe3_0 interface via ptpd.

Access to the device from the Orin is working as expected and data traffic is also observable.

After starting the ptp sync, the loggings look quite good as they are indicating a successful start of the syncing process using the mgbe3_0 interface.

Unfortunately the clock on the target device is not updated.

Running an almost exact same setup but connecting the target device to the mgbe1_0 interface works flawlessly though. The only difference is, that we are using a media converter to be able to connect the target device to the ethernet interface of the Orin.

We tested two different Orins (Drive OS 6.0.6 & 6.0.8.1) and experienced the same behaviour.

Are there any special settings or hardware configurations needed to be taken into account when switching from mgbe3_0 to mgbe1_0 regarding ptp sync?

Thank you very much in advance for your help and support.

Dear @sebbe,
Could you share the used steps?

Dear @SivaRamaKrishnaNV ,

The steps are basically as follows:

Setup interface by assigning an appropriate IP address and adjusting some special settings (device already connected):

ip link set dev mgbeX_0 down
ip link set dev mgbeX_0 mtu 9999 up
ip addr add 0.0.0.0/24 dev mgbeX_0
sysctl net.core.rmem_max=9999
sysctl net.core.rmem_default=9999

Please note that mgbeX_0, 0.0.0.0/24 and 9999 are just some placeholder values.

After the device has been activated and messages are observable in Wireshark, the ptp sync is started by:

/usr/sbin/ptpd -C -d -L -c /path/to/ptp2.conf

As mentioned this works for the mgbe1_0 interface although there are also malformed follow up messages observable.

Observing the mgbe3_0 interface in Wireshark, those malformed messages also pop up as soon as the described ptp process is running.

Delay request and response messages are completely missing though when comparing to using the mgbe1_0 interface.

Dear @sebbe,
Does this issue need support?

Dear @SivaRamaKrishnaNV ,

I was able to identify the problem in the ptpd configuration file:

Does NOT WORK for ‘mgbe3_0’ (but for ‘eqos_0’ and ‘mgbe1_0’):

ptpengine:dot2as = Y
ptpengine:transport = ethernet

DOES WORK for ‘mgbe3_0’ (and for ‘eqos_0’ and ‘mgbe1_0’):

ptpengine:dot2as = N
ptpengine:transport = ethernet

It may be related to the information outlined in Other PTP Profiles in Orin:

DRIVE OS Linux supports IEEE 802.1AS profile. Support for this profile is limited to the software stack running in Tegra/Orin i.e., no support in switches. This means this profile can not be enabled on Ethernet MACs, which are directly connected to the switches on the DRIVE Orin Development Platforms. For custom boards all the Tegra MACs can support this profile.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.