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
gPTP: frdm_k64f : can not converge time #29599
Comments
I see this issue in release 2.3 as well. |
@mmahadevan108 , you can assign to me, as I have better SDK team support. |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
I find this is not dirver issue, as from wireshark, I can see the ptpv2 package, the problem now is that:
so I guess there are some state machine confliction while connection with different accuracy timer instance. |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
Describe the bug
we set up one pc and run https://github.com/Avnu/gptp.git I attached the windows package
Debug.zip
then we set up frdm_k64f board connect with PC though direct connect ethernet cable.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
the time calculation complete and converged
Impact
PTP usage.
Logs and console output
pc side application output
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: