Hi @kenli
I found when running "ptp4l -i eno0 -f gptp.cfg -m" at the first time. It shows port link down and up.
But when I use switch port swp0, it would not cause the link down/up problem.
If we run an eth application before time sync(ptp4l -i eno0 -f gptp.cfg), it will cause the port link down which is not allowed.
So I have two questions down below:
1. Why it is different between eno0 and swp0 by using the same ptp4l command?
2. How do I avoid such link up/down problem on eno0 port?
Thanks
Please refer to section "8.8.1.3 Basic TSN configuration examples on ENETC" in LSDKUG_Rev21.08.pdf
Hi @yipingwang
Thank you for your reply.
I could not find solution from the file, but I think it is the ptp4l strategy.Maybe it is better to post my question on PTP forum.
Thank you