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.

Sign up for GitHub

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

Jump to bottom

gPTP: MDSyncReceiveSM doesn't block PortSyncSyncReceive #36

Open
ahogen opened this issue Apr 19, 2018 · 0 comments
Open

gPTP: MDSyncReceiveSM doesn't block PortSyncSyncReceive #36

ahogen opened this issue Apr 19, 2018 · 0 comments

Comments

@ahogen
Copy link

ahogen commented Apr 19, 2018 •
edited
Loading

In MDSyncReceiveSM, a DISCARD due to folllowUpReceiptTimeoutTime means PortSyncSyncReceive should not get a rcvdMDSync event.

However in XMOS code, even if a folllowUpReceiptTimeout event occurs, syncReceiptTimeoutTimeInterval is updated, which is incorrect and breaks the correct operation of the AGED event in PortAnnounceInformation.

  • IEEE Std. 802.1AS-2011 Figure 10-2
  • IEEE Std. 802.1AS-2011 Figure 10-4
  • IEEE Std. 802.1AS-2011 Figure 11-6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ahogen