Ptp faill

Please provide the following info (tick the boxes after creating this topic):
Software Version
[*] DRIVE OS 6.0.10.0
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
2.1.0
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

Issue Description
<Please provide details about your query/application pipeline/usecase/pictures here >

Error String
< Please provide just the error messages here >

Logs
Provide logs in text box instead of image

Please paste the complete application log here. If there are multiple logs, please use multiple text box

I plugged a laser radar into the mgbe1_0 port and it only supports gptp. When I tried to start PTP to synchronize time stamps, I got the following error. Could you please help me take a look?

zhangzs@tegra-ubuntu:~/adas_ws$ sudo ptp4l -v
1.92
zhangzs@tegra-ubuntu:~/adas_ws$ sudo ptp4l -S -E -2 -m -i mgbe1_0
ptp4l[1035.756]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[1035.756]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[1041.828]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
ptp4l[1041.828]: selected local clock 48b02d.fffe.fed196 as best master
ptp4l[1041.828]: assuming the grand master role
ptp4l[1042.829]: timed out while polling for tx timestamp
ptp4l[1042.829]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1042.830]: port 1: send sync failed
ptp4l[1042.830]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1058.920]: port 1: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1065.618]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
ptp4l[1065.618]: selected local clock 48b02d.fffe.fed196 as best master
ptp4l[1065.618]: assuming the grand master role
ptp4l[1066.619]: timed out while polling for tx timestamp
ptp4l[1066.619]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1066.619]: port 1: send sync failed
ptp4l[1066.619]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1082.696]: port 1: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1089.679]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
ptp4l[1089.679]: selected local clock 48b02d.fffe.fed196 as best master
ptp4l[1089.679]: assuming the grand master role
ptp4l[1090.680]: timed out while polling for tx timestamp
ptp4l[1090.680]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1090.680]: port 1: send sync failed
ptp4l[1090.680]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
^Czhangzs@tegra-ubuntu:~/adas_ws$ cat /etc/ne
netconfig netplan/ network/ networks newt/
zhangzs@tegra-ubuntu:~/adas_ws$ cat /etc/netplan/01-lidar-network.yaml
network:
version: 2
renderer: networkd
ethernets:
mgbe1_0:
dhcp4: no
addresses:
- 192.168.1.102/24
zhangzs@tegra-ubuntu:~/adas_ws$

@SivaRamaKrishnaNV Could you please take a look?

Dear @deng.shigang,
Is it like you want to sync the radar timestamp to PTP? May I know radar details to check internally on support.

is lidar。and we have solve it.by using -H instead of -S。and use the automotive-master.cfg。but we need to set tx_timestamp_timeout 1000

1 Like

Dear @deng.shigang,
Glad to hear you could fix it. Could you share details on what was your mistake and how you could fix it?

1 Like

We found that Orin only supports hardware-based time synchronization, and using software-based time synchronization would cause problems. Therefore, we changed to hardware-based time synchronization instead.

1 Like