Really appreciate your response. I tried the steps that you clearly outlined above. But, still facing some issues.
Was able to set the correct time in Aurix. The target is Tegra-a and interface eth0 is not connected to any network. Interface enp3s0 gets connected to external network intermittently and during this step both interfaces was not connected. To do step 4, should any of the interface be connected to external network, I assume NO, because we are just sync’g with Aurix right?
In step-4 “sudo ./ptp4l -f ./gPTP.cfg -p /dev/ptp0 -i eth0 -s -m -D -l 7” was just displaying “port 1: delay timeout”.
As per my understanding, since it is suppose to sync with Aurix, I used interface eth0.200 for the next try. “sudo ./ptp4l -f ./gPTP.cfg -p /dev/ptp0 -i eth0.200 -s -m -D -l 7”. This sync’d the time and was able to see the correct time when I did “sudo ./phc_ctl /dev/ptp0 get” and using date.
$./phc_ctl /dev/ptp0 get
phc_ctl[5255.526]: clock time is 1520542668.412596911 or Thu Mar 8 20:57:48 2018
Thu Mar 8 20:57:54 GMT 2018
But, the time was was not persistent across reboots on the target. After reboot, it gets reset.The AURIX time still looks fine.
sudo ./phc_ctl /dev/ptp0 get
phc_ctl[45.385]: clock time is 0.000000000 or Thu Jan 1 00:00:00 1970
Thu Feb 8 19:12:26 GMT 2018
Do I have to re-sync everytime the target is rebooted?
Your comments will be very helpful