-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Medium
-
Linux Core SDK
-
LCPD-44680
-
-
11.02
-
AM62x EVM set up as PTP4l follower connected to another device setup as grandmaster results in seeing many "received PDELAY_REQ without timestamp" messages if in P2P mode (TI was able to replicate) and "DELAY_REQ without timestamp messages" if in E2E mode (customer reported). This shows up for SDK 11.0 and SDK 11.1
Could be related to and issue on errata i2401 workaround where NOT every ptp4l message is being timestamped?
AM62x Log using P2P mode and gPTP.cfg: https://gist.github.com/dao-qiu/f5be5c06e42f0e1cef4e0ff92d217fbf
AM64x Log using P2P mode with gPTP.cfg: https://gist.github.com/dao-qiu/4c820b70ec648ca741e05328bc7f61ae
--> able to see "received PDELAY_REQ without timestamp" and "SYNC without timestamp" on AM62x
AM62x Log using SDK example: https://gist.github.com/dao-qiu/e3235f0dccbb3196a0f885aca229b77d
AM64x Log using SDK example: https://gist.github.com/dao-qiu/303f4d2b13b72380701b4ccfac9844ec
--> able to see "received PDELAY_REQ without timestamp" on AM64x and "received SYNC without timestamp" on AM62x
AM62x Log using E2E mode with -4 option (CUSTOMER'S CONFIGURATION): https://gist.github.com/dao-qiu/c9d12951dadb4c979199c9087969c795
AM64x Log using E2E mode with -4 option (customer used a different non-TI device): https://gist.github.com/dao-qiu/c7c51d5122a775fea225af140cef3b92
---> Need to make sure IP address is configured
--> Took some time but the "received SYNC without timestamp" does show up on AM62x
AM62Px Log using E2E mode with -4 option (CUSTOMER'S CONFIGURATION): https://gist.github.com/dao-qiu/ad6a25587b82f47ac4129124114e03c1
AM62x Log using E2E mode with -4 option: https://gist.github.com/dao-qiu/f74a4985c0775112864204d99c3dc4f7
--> AM62Px doesn't show the "without timestamp" messages at least for the length of time that I ran for in the logs
--> AM62x shows "PDELAY_REQ without timestamp" message