Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PTP- Why clock is updated after the Follow-up but not after Delay response packet. #8

Open
srivallik-eaton opened this issue Jun 20, 2024 · 0 comments

Comments

@srivallik-eaton
Copy link

Hi,

I am using nucleo STM32H743zi controller.
I am using linux machine as host and my controller as slave in E2E mode.
I have used DHCP mode.
I have below few questions for which I was unable to find answers for:
It will be really helpful if I can get answers to these questions.

  1. Why is the internal timing or the clock updated soon after the Follow-up message is received. Should not the clock be updated after delay response is received from master. (in protocol.c, function name: handleFollowUp( ))

  2. Since the sequence ID is int16_t it is storing negative sequence numbers. (in datatypes.h)

  3. Is there any work-around the internal time exceeding the integer limit after 2038. (in arith.c)

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant