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

Atxmega core devices are not synchronized to harp synchronization specification #62

Open
bruno-f-cruz opened this issue Nov 29, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@bruno-f-cruz
Copy link
Member

This issue is following the discussion start in #53
In summary, it appears that atmega subordinate devices are not synchronizing to the clock generator device and instead add a offset in the order of 200 microseconds.

This bug can be demonstrated by measuring the clock serial output from a clock generator (example 1 a atmega generator, TimestampGeneratorGen3 and example 2 a rp2040 generator, WhiteRabbit) and the corresponding heartbeat LED toggle of a subordinate device (in this case a atmega behavior board)

Example 1)

image

Example 2)

image

Under a perfect scenario, if the two board were to be perfectly synchronized (and the led heartbeat routine is instantaneous), one would expect the led toggle to take place exactly 672 after the start of the last byte, as per harp standard (https://github.com/harp-tech/protocol/blob/main/SynchronizationClock.md#serial-configuration)

@bruno-f-cruz bruno-f-cruz added proposal Request for a new feature bug Something isn't working and removed proposal Request for a new feature labels Nov 29, 2024
@glopesdev glopesdev changed the title Atmega core devices are not synchronized to harp synchronization specification Atxmega core devices are not synchronized to harp synchronization specification Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant